Hotkey no longer mutes both Speaker and Headset/Monitor after OBS audio mixer changes

A

Andore

New Member
Before the recent OBS audio mixer changes, I used Ctrl + Alt as my microphone mute/unmute hotkey and it worked perfectly for my setup.

Now, with the new Speaker and Headset/Monitor icons being separate, pressing my mute hotkey only mutes the Speaker icon, while the Headset/Monitor icon stays active.

My setup is basically:
  • Microphone source in OBS
  • Audio monitoring enabled
  • Ctrl + Alt assigned to Mute and Unmute
  • I want one shortcut to completely turn the microphone off/on
What I would like is:

Press Ctrl + Alt
  • Speaker/output muted
  • Headset/monitoring muted
Press Ctrl + Alt again
  • Speaker/output unmuted
  • Headset/monitoring unmuted
At the moment, I can't find a built-in hotkey for the new Headset/Monitor button, so I have to manually click it.

Is there currently a way to assign a hotkey to the Monitor/Headset toggle?

If not, could this be added as a hotkey option in OBS? Ideally, it would also be useful to have an option where Mute Source can optionally mute both the normal output and monitoring, similar to how it behaved before.

Thanks!
 
I have the same issue. There is a Hotkey option you can set for Audio Monitor Mute/Unmute. But it does not work when you try to bind the same Hotkey as the Audio Toggle button. OBS seems to lag a lot and want to crash when you do this. Waiting for a fix because honestly before it was perfect for my use case and now it's utterly broken.
 
+1
I completely understand the reasoning behind this change and the evolution of the audio monitoring system.

However, I really think it would be useful to have an option allowing users to choose whether muting a source should also mute its monitoring.

In my workflow, I used to rely on the previous behavior: when I muted an audio source, it was muted both from the stream output and from my monitoring. With the new behavior, the source remains audible in my headphones even though it is muted from the stream.

Unfortunately, this completely changes the way I manage my audio chain, and I can no longer use my audio sources the way I did in previous versions of OBS.

I think giving users the choice would be the best solution. Some users may prefer the new behavior, while others may need the previous one depending on their setup and workflow.

So rather than reverting the change, I would really appreciate an option such as “Mute also disables monitoring” (or similar), allowing each user to choose the behavior that works best for them.

Thanks for considering this!
 
The current workaround I have found is to use Adanced Scene Switcher to Mute/Unmute both Audio Output and Audio Monitoring on Macro Hotkey press.. It was a hassle to set up and it's not as "smooth" as it used to be before. Waiting for the official fix in OBS 33 as mentioned above.
 
+1

I need to be able to toggle audio source monitoring on/off with a hotkey because that's my main way to control the volume of my games (console). Since that's being added back to the next version, can we also please stop getting the pop-up notification at launch about OBS not having been closed properly last time? I don't care about that and no, I don't want to submit a bug report literally every other time I launch OBS about it.
 
Uzuki said:
+1

I need to be able to toggle audio source monitoring on/off with a hotkey because that's my main way to control the volume of my games (console). Since that's being added back to the next version, can we also please stop getting the pop-up notification at launch about OBS not having been closed properly last time? I don't care about that and no, I don't want to submit a bug report literally every other time I launch OBS about it.
Click to expand...

We will not be removing that dialog or allowing it to be suppressed. It's indicative that OBS is crashing on shutdown, or is otherwise not being allowed to cleanly exit. It's likely the same issue happens every time (and almost certainly it's a plugin that needs to be updated/replaced), so you would not need to submit a new bug report for every crash. I recommend making a new post about this issue, with a log file (and a crash log if OBS is crashing on exit) so someone can take a closer look. If you are not willing to take the time to troubleshoot and understand the issue, then you will just have to live with the annoyance :)
 
You must log in or register to reply here.
Back
Top