v1.4.2 - Teams notifications no longer trigger muting

Chat messages and other Teams notifications no longer mute your other apps.

What was wrong: new Teams plays its notification pings through the same
WebView2 child process as its ringtone, and Chromium keeps that audio session
open and looking "active" for several seconds after a sound has finished. Ring
detection watched exactly that, so a chat ping looked the same as an incoming
call and everything went quiet for a few seconds.

The fix: ring detection now measures how loud Teams actually is, rather
than whether its audio session is open. It reads the peak level of Teams' own
playback (the number behind the moving bar in the Volume Mixer) five times a
second while a Teams session is active, and counts it as ringing after roughly
2.5 seconds of real sound within an eight-second window. Teams' notification
chime is audible for about a third of a second, so it takes six pings inside
eight seconds to reach the bar, while a ringtone passes it easily.

Nothing else changed: still no microphone, no audio contents, no internet.

Upgrading: run the installer over the top, it keeps your settings.

Download	Use it if
TeamsAudioDucking-Setup-1.4.2.exe	normal install (per user, no admin)
TeamsAudioDucking-1.4.2-portable.zip	no install, just run the exe

v1.4.1: call volume actually works

Bug-fix release. If you turned on Raise the system volume during calls in 1.4.0 and nothing happened, this is the fix.

Fixed

• The call-volume option never actually ran. The audio device objects are created on the app's UI thread at startup, but a call is handled on a background thread, and Windows will not let the system volume be reached through a device object across that boundary. The log recorded Could not raise the system volume: Specified cast is not valid on every call. The device is now looked up on whichever thread is handling the call, so the volume is raised and restored as intended.

Muting was never affected by this, only the optional volume raise.

Behaviour, unchanged

The volume is only ever raised, never lowered, and it targets the output device Teams is actually playing through (not necessarily your default device). Your previous level is put back when the call ends, unless you adjusted the volume yourself mid-call, in which case your level is kept.

Install

Run TeamsAudioDucking-Setup-1.4.1.exe over your existing install; settings are kept. SmartScreen will warn that the publisher is unknown because the installer is not code-signed: More info then Run anyway. Portable users: unzip and replace the exe.

v1.4.0

Changed

• The call-volume option now raises the system volume, not Teams'' app volume. Raising Teams'' own app volume was the wrong target: it is already at 100% on a normal machine, so the option did nothing noticeable. What is actually turned down when a call sounds quiet is the Windows volume of the output device, so that is what gets raised now.

Details:

• The device is taken from Teams'' own audio sessions, not from the default device: the Communications-role default can be a different endpoint from the one Teams actually plays through.
• Only ever raises, never lowers. The previous level is put back when the call ends.
• Adjust the volume by hand during a call and your level is kept (the restore leaves it alone).
• Raised devices are persisted, so a crash mid-call still restores the level on the next start.
• Enabling the option or changing the level applies mid-call; switching it off puts the volume back straight away.

Existing settings carry over untouched, and Teams app-volume levels raised by 1.2.0-1.3.0 are still restored.

Install

Download and run TeamsAudioDucking-Setup-1.4.0.exe (over the top of any previous version; settings are kept). The SmartScreen warning on first run is expected: the installer is unsigned. More info > Run anyway.

v1.3.0

Fixed

• Incoming calls now mute while still ringing. New Teams plays the incoming ringtone through its embedded WebView2 process (msedgewebview2.exe), not through ms-teams.exe, so ring detection only fired for outbound calls. Audio sessions are now attributed to Teams by walking the parent-process chain, and Teams' WebView2 is no longer muted as a bystander app during calls.

Added

• AVD / Windows 365 media-optimised Teams (MsTeamsVdi.exe) is now recognised as Teams: its calls are detected and it is never muted.
• The call-volume boost logs when Teams is already at or above the target level, so a no-op is visible in the log (the boost only ever raises Teams, never lowers it).

Install

Download and run TeamsAudioDucking-Setup-1.3.0.exe (over the top of any previous version; settings are kept). SmartScreen warning on first run is expected: the installer is unsigned. More info > Run anyway.

v1.2.1

First packaged release.

Setup exe (recommended): per-user install, no admin, Start-menu shortcut, optional start-at-sign-in, proper uninstaller.
Portable zip: unzip anywhere and run; manage startup from the app's Settings.

Includes everything up to v1.2.1: exact-state mute/restore during Teams calls, ring detection, optional Teams call-volume boost, settings window layout fix. See the README changelog for details.