starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Volume Mixer Sound Setting not saved for Windows Terminal #22102

New Issue
Open
opened 2026-01-31 08:03:32 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 08:03:32 +00:00
Owner
Copy Link

Originally created by @mobeigi on GitHub (Aug 17, 2024).

Windows Terminal version

1.20.11781.0

Windows build number

10.0.19045.4780

Other Software

No response

Problem

My issue is I like to have my system sounds (including the bell) set to 10% of System Volume.
I have already customised the bell wav for my terminal profiles and this works well, its just the bell sound is too loud and I can't set it to 10% volume because Windows doesn't remember the volume mixer setting for Windows Terminal after it restarts (unlike other apps).

Some undesirable workarounds:

  • I know I can disable the bell via bellStyle but this is not what I want to do.
  • I know I can modify the bell sound wav audio itself to be much quieter but it seems like a hack.

Steps to reproduce

Current volume mixer:
image

These settings work perfectly for Command Prompt shell (my system sounds is at 10% and my bell sound is quiet).

However, for other WT profiles it does not work the same:

  1. Open wt up with a non Command Prompt profile (for example, I am using Git Bash)
  2. Trigger bell sound (i.e. via failed autocompletion etc). Windows Terminal now appears in volume mixer
  3. Set Windows Terminal volume to desired volume (i.e. 10%)
  4. Quit Windows Terminal
  5. Start Windows Terminal
  6. Trigger bell sound again (Volume is back to 100% in Volume Mixer)

Post volume mixer:
SndVol_PtOoxEF9oK

Expected Behavior

Volume remains the same as previously set value in Volume Mixer.

Actual Behavior

Volume is reset (back to 100%) in Volume Mixer.

Originally created by @mobeigi on GitHub (Aug 17, 2024). ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.19045.4780 ### Other Software _No response_ ### Problem My issue is I like to have my system sounds (including the bell) set to 10% of System Volume. I have already customised the bell wav for my terminal profiles and this works well, its just the bell sound is too loud and I can't set it to 10% volume because Windows doesn't remember the volume mixer setting for Windows Terminal after it restarts (unlike other apps). Some undesirable workarounds: - I know I can disable the bell via `bellStyle` but this is not what I want to do. - I know I can modify the bell sound wav audio itself to be much quieter but it seems like a hack. ### Steps to reproduce Current volume mixer: ![image](https://github.com/user-attachments/assets/7c4b54be-e3b5-4a32-806a-f0e83cb2a812) These settings work perfectly for Command Prompt shell (my system sounds is at 10% and my bell sound is quiet). However, for other WT profiles it does not work the same: 1. Open wt up with a non Command Prompt profile (for example, I am using Git Bash) 2. Trigger bell sound (i.e. via failed autocompletion etc). Windows Terminal now appears in volume mixer 3. Set Windows Terminal volume to desired volume (i.e. 10%) 4. Quit Windows Terminal 5. Start Windows Terminal 6. Trigger bell sound again (Volume is back to 100% in Volume Mixer) Post volume mixer: ![SndVol_PtOoxEF9oK](https://github.com/user-attachments/assets/343e77fc-c2e6-42c2-8def-461625f23816) ### Expected Behavior Volume remains the same as previously set value in Volume Mixer. ### Actual Behavior Volume is reset (back to 100%) in Volume Mixer.
claunia added the Help WantedIssue-BugProduct-TerminalArea-UserInterface labels 2026-01-31 08:03:32 +00:00
claunia commented 2026-01-31 08:03:33 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Aug 21, 2024):

Thanks for filing! We're thinking this may be an app platform bug as it's fixed in Win11.

We're thinking this may also be fixed by using a different media player from the WinRT one. We've seen that doing that has fixed other issues (i.e. file picker issues).

@carlos-zamora commented on GitHub (Aug 21, 2024): Thanks for filing! We're thinking this may be an app platform bug as it's fixed in Win11. We're thinking this may also be fixed by using a different media player from the WinRT one. We've seen that doing that has fixed other issues (i.e. file picker issues).
claunia commented 2026-01-31 08:03:33 +00:00
Author
Owner
Copy Link

@mobeigi commented on GitHub (Aug 22, 2024):

We're thinking this may also be fixed by using a different media player from the WinRT one. We've seen that doing that has fixed other issues (i.e. file picker issues).

Thanks for the reply mate. Can you elaborate on the 'different media player' part? What does that mean exactly?
Do you have a link to other similar issues?

@mobeigi commented on GitHub (Aug 22, 2024): > We're thinking this may also be fixed by using a different media player from the WinRT one. We've seen that doing that has fixed other issues (i.e. file picker issues). Thanks for the reply mate. Can you elaborate on the 'different media player' part? What does that mean exactly? Do you have a link to other similar issues?
claunia commented 2026-01-31 08:03:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 22, 2024):

Sure thing. We're using the "modern" WinRT MediaPlayer APIs to play bell sounds currently:

56cfb77c6d/src/cascadia/TerminalApp/TerminalPaneContent.cpp (L314-L317)

But we've got a theory that the older, win32-style APIs for playing media probably don't have the same OS bug applicable to them. That's where we'd start investigating.

@zadjii-msft commented on GitHub (Aug 22, 2024): Sure thing. We're using the "modern" WinRT [MediaPlayer](https://learn.microsoft.com/en-us/uwp/api/windows.media.playback.mediaplayer?view=winrt-26100) APIs to play bell sounds currently: https://github.com/microsoft/terminal/blob/56cfb77c6d2aeaa408310756ed711531a037c021/src/cascadia/TerminalApp/TerminalPaneContent.cpp#L314-L317 But we've got a theory that the older, win32-style APIs for playing media probably don't have the same OS bug applicable to them. That's where we'd start investigating.
claunia commented 2026-01-31 08:03:33 +00:00
Author
Owner
Copy Link

@SamusAranX commented on GitHub (Dec 27, 2024):

as it's fixed in Win11.

I'm on Windows 11 (OS build 26100.2605, Terminal version 1.21.3231.0) and it's very much not fixed there.
Every time something in the terminal goes ding, the alert sound is played at a deafening volume.

@SamusAranX commented on GitHub (Dec 27, 2024): > as it's fixed in Win11. I'm on Windows 11 (OS build 26100.2605, Terminal version 1.21.3231.0) and it's very much not fixed there. Every time something in the terminal goes ding, the alert sound is played at a deafening volume.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Help Wanted Issue-Bug Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22102
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?