EarTrumpet is a lightweight, open-source volume control that replaces the default Windows 11 volume flyout and gives you per-app audio, quick device switching, and a Fluent-style user interface that fills gaps left by the native mixer.
Install it and you get individual sliders, persistent app settings, and immediate access to output devices without opening Settings > Sound.
Clear value props: why choose EarTrumpet over the native mixer
EarTrumpet exposes per-app volume so you can balance music, browser audio, and chat on the fly without juggling multiple windows.
It offers faster device switching from the taskbar for system-wide or app-specific outputs in two clicks, which speeds up meetings and gaming setups.
The UI integrates with Windows 11 visuals and reduces clicks compared with Volume Mixer, cutting routine audio tasks from several steps to one or two.
Per-app audio control that changes how you manage sound
Individual sliders appear in a compact list; slide an app down a few percent to lower background music while keeping chat loud.
App-specific mute and volume persistence mean your settings survive app restarts and reboots unless the app recreates a new audio session.
Use EarTrumpet as an app volume mixer to treat each application as its own audio source instead of adjusting system master volume.
Faster output switching from the taskbar
Click the EarTrumpet icon, choose an app or system-wide output, then pick headphones, speakers, or a Bluetooth device — two clicks for most changes.
That contrasts with the longer Settings path: Settings > System > Sound > Choose output device, which takes more time and attention.
For Bluetooth users, quick switching avoids repeated trips to the Settings app and reduces audio dropouts during device changes.
Compatibility and system requirements for Windows 11
EarTrumpet targets modern Windows 11 builds; it works on stable releases and most Insider builds but can conflict with experimental audio changes in some Insider channels.
Recommended minimum: a current Windows 11 update build released within the last 12 months; check the EarTrumpet GitHub or Store listing for explicit build notes.
The Microsoft Store package supports x86/x64 and generally works on Intel/AMD devices; ARM device support depends on the Store build and system architecture compatibility.
Permissions and Windows services EarTrumpet needs
EarTrumpet requires no invasive permissions; it interacts with Windows audio services using standard user-level APIs and runtime permissions.
Ensure the Windows Audio and AudioEndpointBuilder services are running: open Services.msc, find both services, and set Startup Type to Automatic if disabled.
Microphone settings and privacy options do not need changes for EarTrumpet to control playback devices, but input-related routing may require permissions for apps that capture audio.
How EarTrumpet interacts with the Windows sound subsystem and drivers
EarTrumpet is a user interface layer built on the Windows Core Audio APIs; it queries audio sessions and exposes controls without installing kernel drivers.
Virtual drivers like Voicemeeter, virtual audio cables, or OBS virtual devices appear as normal endpoints and can be selected per app; that can create complex routing scenarios.
Conflicts arise when multiple audio routers claim exclusive control or when apps use exclusive audio mode; disable exclusive mode in app settings or the device properties to restore standard behavior.
Two fast installation paths: Microsoft Store vs GitHub releases
Microsoft Store: easiest route, automatic updates, verified publisher, and safe uninstall through Settings.
GitHub releases: best for bleeding-edge features, portable builds, and power-user installs; you must handle manual updates and verify release integrity.
Always prefer the official Microsoft Store entry or the verified EarTrumpet GitHub repo; avoid third-party sites and unsigned installers.
Installing from the Microsoft Store (recommended)
Open Microsoft Store, search for “EarTrumpet”, click Install, and let the Store handle updates and permissions.
After installation, confirm auto-update is enabled in the Store and pin EarTrumpet to the taskbar for one-click access.
Store installs are signed and verified, which eases enterprise deployment and reduces the need to manually check signatures.
Installing from GitHub or sideloading (power-user option)
Download the latest release from the official EarTrumpet GitHub releases page and check the release notes before running any installer or unpacking an MSIX/APPX package.
If sideloading is required, enable “Sideload apps” in Settings > Privacy & security > For developers, then install the package and trust the publisher.
Verify checksums or signatures when provided, keep a manual update schedule, and avoid unknown forks or unofficial builds that may include unwanted modifications.
First-time setup and taskbar integration
Pin EarTrumpet to the taskbar, test per-app sliders by playing audio in two apps, and confirm changes persist after closing and reopening each app.
Set EarTrumpet to run on login: add it to Startup via Task Manager > Startup or enable autorun if the Store version exposes that option.
Test quick device switching and per-app output routing during setup to catch driver or Bluetooth pairing issues early.
Pinning, replacing, and customizing the taskbar volume behavior
Right-click the EarTrumpet icon and choose options to pin it; hide the native volume icon via Settings > Personalization > Taskbar > Other system tray icons if you prefer EarTrumpet exclusively.
Use Windows 11 taskbar flyout behaviors to control how much appears on hover or click, keeping the flyout compact for fast access.
Configuring startup, autorun, and quick access
Enable EarTrumpet at boot by toggling its Startup entry in Task Manager so the icon appears immediately after login.
Keep the flyout compact by closing unnecessary system tray items and testing the click vs hover behavior for your workflow.
Mastering core features: per-app sliders and routing
The main UI lists running audio sessions with individual sliders and a global master control at the top; move sliders to adjust levels live.
Volume persistence stores per-app settings; to reset preferences, close the app, reset device output, or clear audio sessions by restarting Windows Audio service.
Adjusting per-application volume and muting from the flyout
Lower a game’s slider to reduce music without touching voice chat; mute background music apps with a single click to eliminate distractions.
If a slider disappears, force-close the affected app or switch its output once to recreate the audio session and restore control.
Routing individual apps to different output devices
Select an app in the EarTrumpet flyout and pick a different output to send that app to headphones while the system audio stays on speakers.
With virtual devices, send browser audio to a virtual cable for OBS capture while sending voice chat to a headset; test capture paths to avoid double-capture.
Advanced tips for gamers, streamers, and audio pros
Use EarTrumpet to separate audio sources before they hit OBS: route game, music, and chat to distinct devices and add each device as a separate capture source in OBS.
Keep communication apps like Discord on a dedicated output and adjust their sliders quickly during streams to manage guest volume without disrupting game audio.
Combining EarTrumpet with OBS, Discord, and audio routers
Route game audio to one device and voice chat to another, then configure OBS to capture the two outputs separately to maintain independent levels in the stream mix.
Avoid feedback loops by disabling desktop audio capture for devices already routed into OBS via virtual cables or by using exclusive capture only where needed.
Reducing latency and avoiding device conflicts while gaming
Turn off exclusive mode in device properties, match sample rates across devices in Sound Control Panel, and prefer manufacturer drivers for lower latency.
If you hear stutter or pops, restart Windows Audio services, check for driver updates, and ensure no two apps claim exclusive access to the same endpoint.
Troubleshooting: quick fixes and diagnostics
Missing icon, sliders not showing, or wrong device selected are common symptoms; first steps: restart EarTrumpet, restart Windows Audio, and reboot.
Check Windows Updates and audio driver versions; many issues resolve after updating manufacturers’ drivers or installing a stable Windows cumulative update.
EarTrumpet missing from taskbar or refusing to launch
Confirm EarTrumpet is installed, open Task Manager to end any hung instances, and re-pin the icon via Start or the installed app list.
Use Event Viewer to inspect application error logs if the app crashes, and consider reinstalling from the Microsoft Store to get a verified build.
Per-app sliders absent or stuck at a value
Force-close the affected app, restart the Windows Audio Endpoint Builder service, and toggle the app’s output to force new audio session creation.
If an app uses exclusive audio mode, disable that mode in the app or in the device’s Advanced properties to restore adjustable sliders.
Security, privacy, and open-source considerations
EarTrumpet is open-source and typically has a low data footprint; the Store build is signed and the GitHub repo shows source code for audit.
Review the repository, check commit history and contributors, and build from source if corporate policy requires binary verification.
Verifying releases, signatures, and trusting the GitHub repo
Prefer Microsoft Store builds for enterprise environments; for GitHub releases, verify tags, read release notes, and check published checksums or signatures where provided.
Look for official maintainer accounts and cross-check release artifacts with the repository’s signed tags if security is a concern.
Comparing EarTrumpet with Windows 11 Volume Mixer and alternatives
EarTrumpet adds per-app sliders, device switching, and a modern UI over the native mixer, which lacks quick device routing and persistent app settings.
Alternatives like Voicemeeter handle advanced routing and mixing, SoundSwitch offers hotkey device toggling, and Volume2 provides customizable hotkeys and behavior.
Choosing the right tool for casual users vs audio pros
Casual users get the most benefit from EarTrumpet via the Store install for automatic updates and minimal setup.
Advanced routing and mixing still require tools like Voicemeeter or virtual audio cables layered on top of EarTrumpet for UI control.
Maintenance, updates, and clean uninstall
Keep the Store app updated automatically; if using GitHub builds, check releases periodically and apply manual updates after verifying integrity.
Back up a short checklist of your per-app routing and device preferences so you can restore the setup quickly after a reinstall.
Proper uninstall and cleaning leftover settings
Uninstall via Settings > Apps > Installed apps or using the Microsoft Store uninstall option; then remove leftover registry keys only if comfortable editing the registry.
To restore the default Windows volume icon, re-enable it under Taskbar settings and reboot if the icon does not reappear immediately.
Quick checklist and pro shortcuts
1) Pick install method: Store for most users, GitHub for power users.
2) Install and pin EarTrumpet to the taskbar for one-click access.
3) Enable startup via Task Manager so EarTrumpet runs on login.
4) Test per-app sliders by running two audio sources and adjusting sliders live.
5) Route at least one app to a separate device to verify per-app output switching.
6) Integrate with OBS or your streaming tool and test capture paths to prevent double-capture.
7) Keep a note of device mappings and update schedule for fast recovery after updates or reinstalls.
Final practical shortcuts
Right-click app sliders for fast mute or device selection where supported, and use Task Manager to enable/disable EarTrumpet startup entries quickly.
For recurring workflows, save a short checklist of actions and test after major Windows updates to catch driver or permission changes early.
