EarTrumpet

Solving Common EarTrumpet Audio Issues

Beyond outright failures to open or make sound, EarTrumpet users occasionally run into smaller audio issues: a device-switching option that doesn't stick, a delay before sliders update, or a device listed that's no longer connected. These are generally quick to resolve with routine Windows checks.

Device list shows a disconnected device

If EarTrumpet's playback device menu lists a device you've unplugged, open Settings > System > Sound and check for the same stale entry there; Windows sometimes keeps disconnected devices listed until you restart or run a hardware scan in Device Manager.

Moving an app to a new output device doesn't stick

Some apps reset their own default output when they restart. After moving an app's audio with EarTrumpet, keep the app running rather than closing it immediately, and confirm the change again in Settings if it reverts.

Delayed or laggy slider updates

A brief lag when opening the flyout is normal on some systems as EarTrumpet enumerates active audio sessions. If the delay is long or sliders freeze, restart EarTrumpet from the tray icon and, if needed, restart the Windows Audio service via services.msc.

Theme or display quirks

EarTrumpet follows the Windows light/dark theme setting. If the flyout looks visually broken, check Settings > Personalization > Colors and confirm your chosen theme applies consistently system-wide.

Hotkey doesn't open the flyout

If EarTrumpet's keyboard shortcut stops working, check its settings for the current hotkey assignment and make sure no other app has claimed the same key combination.

When to reinstall or check GitHub

For issues that persist after the steps above, reinstall via the Microsoft Store or Chocolatey, and check the GitHub issue tracker for similar reports.

Why smaller audio quirks are usually harmless

Unlike a complete failure to open or produce sound, the issues on this page — stale device entries, brief lag, or a hotkey conflict — are cosmetic or timing-related rather than signs of a deeper fault. They tend to appear after Windows updates, driver changes, or simply having many audio devices connected and disconnected over time. None of them require a reinstall as a first response, which is why this page lists lighter checks before pointing toward a clean reinstall.

If you want to understand how these smaller controls map onto the full Windows Sound settings panel, that comparison can help confirm whether a quirk is unique to EarTrumpet or shared with Windows itself.

When multiple small issues appear together

If you notice several of these symptoms at once — for example laggy sliders and a stale device — rather than treating them individually, restart the Windows Audio service via services.msc first, since a single stressed service can produce a cluster of minor symptoms that all clear up together.

Distinguishing an EarTrumpet quirk from a driver issue

Audio driver updates from your PC manufacturer or sound card vendor can introduce small behavioral changes — such as a device briefly appearing twice — that show up in EarTrumpet's list simply because EarTrumpet reflects whatever Windows currently reports. Checking Device Manager's Sound, video and game controllers section for a recent driver update timestamp can confirm whether a driver change, not EarTrumpet, introduced the quirk.

For a comparison of how the same devices are listed in Windows' own settings, see Windows sound settings.

Reporting a reproducible minor issue

Minor issues that reliably reproduce — for example, a specific device always appearing twice after reconnecting a USB headset — are worth searching for on the GitHub issue tracker, since they're the kind of detail that's easy for maintainers to fix once clearly reported with steps to reproduce.

Keeping device drivers current

Since EarTrumpet relies on the same drivers Windows uses, checking Device Manager periodically for available audio driver updates is a simple way to avoid several of the smaller quirks described on this page before they start.

Frequently asked questions

Why does EarTrumpet still show a device I unplugged?

Windows can retain disconnected audio devices in its list until a restart or device rescan; check Settings > System > Sound for the same entry to confirm it's a Windows-level listing, not an EarTrumpet bug.

Can EarTrumpet cause audio crackling?

EarTrumpet does not process audio itself, so crackling is more likely tied to drivers, sample-rate mismatches, or hardware; the built-in Windows mixer will show the same crackling if that's the cause.

Why does my hotkey stop opening EarTrumpet?

Another application may have claimed the same shortcut; check EarTrumpet's hotkey setting and change it if there's a conflict.

Is a short delay when opening the flyout normal?

A brief delay while EarTrumpet reads active audio sessions is normal; a long freeze usually means the app or the Windows Audio service needs a restart.

Keep EarTrumpet current from the download page to avoid stale-build issues.