starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

Toogleable Whisper/Shout #2969

New issue

Open

opened 2026-02-20 22:15:54 -05:00 by deekerman · 16 comments

deekerman commented

2026-02-20 22:15:54 -05:00

Owner

Originally created by @BenjaminApprill on GitHub (Mar 17, 2025).

Context

No response

Description

I need to utilize high AMP with mouse and keyboard, while being able to verbally communicate using Mumble...

Right now however, any verbal communication requires using a continuous hotkey press, which depletes potential APM.

It would be useful to "toggle" my whisper state on and off; not have to hold it down the entire time. There are situations where I need to communicate over Mumble, AND retain my ability to enter keyboard commands.

This feature is available for continuous transmission, voice activation, and push-to-talk... However, all of these only allow for toggling of a shout that goes beyond the current channel.

Mumble component

Client

OS-specific?

Additional information

No response

Originally created by @BenjaminApprill on GitHub (Mar 17, 2025). ### Context _No response_ ### Description I need to utilize high AMP with mouse and keyboard, while being able to verbally communicate using Mumble... Right now however, any verbal communication requires using a continuous hotkey press, which depletes potential APM. It would be useful to "toggle" my whisper state on and off; not have to hold it down the entire time. There are situations where I need to communicate over Mumble, AND retain my ability to enter keyboard commands. This feature is available for continuous transmission, voice activation, and push-to-talk... However, all of these only allow for toggling of a shout that goes beyond the current channel. ### Mumble component Client ### OS-specific? No ### Additional information _No response_

deekerman added the

client

feature-request

good first issue

labels

2026-02-20 22:15:54 -05:00

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 18, 2025):

You can almost get what you want already by setting keyboard shortcuts for switching to continuous transmission and back.

Or, effectively exactly what you want: set your transmission mode to continuous (or voice activated) and then use a shortcut to toggle your mute state.

@Krzmbrzl commented on GitHub (Mar 18, 2025): You can almost get what you want already by setting keyboard shortcuts for switching to continuous transmission and back. Or, effectively exactly what you want: set your transmission mode to continuous (or voice activated) and then use a shortcut to toggle your mute state.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 18, 2025):

Ah hold on. I just realized you are taking about whispering/shouting, not PTT in general...

Why do you need to continuously use these modes instead of regular communication?

@Krzmbrzl commented on GitHub (Mar 18, 2025): Ah hold on. I just realized you are taking about whispering/shouting, not PTT in general... Why do you need to continuously use these modes instead of regular communication?

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 18, 2025):

For a game. There are times where I need to control the game with the keyboard, while also communicating to team members. This becomes a pain in the ass when I have to hold a hotkey to use comms.

In other words; there are times where I am simultaneously in need of communicating with team members, while also needing to retain maximum control over my "ship" in the game, which requires the hand usually controlling the ship to be relegated to holding a hotkey during the transmission.

@BenjaminApprill commented on GitHub (Mar 18, 2025): For a game. There are times where I need to control the game with the keyboard, while also communicating to team members. This becomes a pain in the ass when I have to hold a hotkey to use comms. In other words; there are times where I am simultaneously in need of communicating with team members, while also needing to retain maximum control over my "ship" in the game, which requires the hand usually controlling the ship to be relegated to holding a hotkey during the transmission.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 18, 2025):

So I am assuming the situation is that you have a shortcuts for whispering to any given team member (or shout to a group of predefined members), which you use to selectively talk to different people at different times?

@Krzmbrzl commented on GitHub (Mar 18, 2025): So I am assuming the situation is that you have a shortcuts for whispering to any given team member (or shout to a group of predefined members), which you use to selectively talk to different people at different times?

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 18, 2025):

No. It is just the standard Whisper/Shout hotkey to the Current channel.

Any other configuration of options shouts to other channels.

The closest thing I can find to this is setting the "Hold Time" setting for a few seconds, but this is still a step removed from ideal.

For all of the configurability Mumble possesses (including the ability to toggle all the other speech options) it has been a long-time source of frustration that something like this isn't in the app.

@BenjaminApprill commented on GitHub (Mar 18, 2025): No. It is just the standard Whisper/Shout hotkey to the Current channel. Any other configuration of options shouts to other channels. The closest thing I can find to this is setting the "Hold Time" setting for a few seconds, but this is still a step removed from ideal. For all of the configurability Mumble possesses (including the ability to toggle all the other speech options) it has been a long-time source of frustration that something like this isn't in the app.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 18, 2025):

Why would you shout to the current channel? You don't need shouting for that

@Krzmbrzl commented on GitHub (Mar 18, 2025): Why would you shout to the current channel? You don't need shouting for that

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 18, 2025):

Whisper/Shout is the same hotkey. It is the only way to get the "yellow" light-up that can only be heard in the current channel. The blue "shout" always bleeds over into other channels.

Continuous transmission only happens as the "blue" option, which means it shouts to other channels. Push-to-Talk proper does the same thing; it lights up as the blue "shout" and bleeds into other channels. The only configuration that doesn't do that is to set the Whisper/Shout hotkey Data setting to the Current channel. However, this is also the only setting that doesn't have a proper "toggle" option.

Any other configuration bleeds the vocals into other channels.

@BenjaminApprill commented on GitHub (Mar 18, 2025): Whisper/Shout is the same hotkey. It is the only way to get the "yellow" light-up that can only be heard in the current channel. The blue "shout" always bleeds over into other channels. Continuous transmission only happens as the "blue" option, which means it shouts to other channels. Push-to-Talk proper does the same thing; it lights up as the blue "shout" and bleeds into other channels. The only configuration that doesn't do that is to set the Whisper/Shout hotkey Data setting to the Current channel. However, this is also the only setting that doesn't have a proper "toggle" option. Any other configuration bleeds the vocals into other channels.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 19, 2025):

It is the only way to get the "yellow" light-up that can only be heard in the current channel. The blue "shout" always bleeds over into other channels.

Then you have misconfigured your channels.

Continuous transmission only happens as the "blue" option, which means it shouts to other channels. Push-to-Talk proper does the same thing; it lights up as the blue "shout" and bleeds into other channels.

No. Only if you have channels linked explicitly.

@Krzmbrzl commented on GitHub (Mar 19, 2025): > It is the only way to get the "yellow" light-up that can only be heard in the current channel. The blue "shout" always bleeds over into other channels. Then you have misconfigured your channels. > Continuous transmission only happens as the "blue" option, which means it shouts to other channels. Push-to-Talk proper does the same thing; it lights up as the blue "shout" and bleeds into other channels. No. Only if you have channels linked explicitly.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 19, 2025):

So what.

Just make Whisper/Shout toggleable.

Most of us don't have control over channel configuration. Channels need to be linked for when shouting is appropriate. Your argument is not convincing enough to talk-down the simplicity of this feature.

@BenjaminApprill commented on GitHub (Mar 19, 2025): So what. Just make Whisper/Shout toggleable. Most of us don't have control over channel configuration. Channels need to be linked for when shouting is appropriate. Your argument is not convincing enough to talk-down the simplicity of this feature.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 20, 2025):

You know what? With this attitude, you are welcome to implement this simple feature by yourself.

@Krzmbrzl commented on GitHub (Mar 20, 2025): You know what? With this attitude, you are welcome to implement this simple feature by yourself.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 21, 2025):

If you admit it is simple. It should have already been implemented. You are the one making excuses.

You never provided any rationale for why it isn't. You just provided inefficient alternatives for me to "tolerate".

Do you have any real rationale for why this feature isn't implemented already? Or why it can't be implemented?

@BenjaminApprill commented on GitHub (Mar 21, 2025): If you admit it is simple. It should have already been implemented. You are the one making excuses. You never provided any rationale for why it isn't. You just provided inefficient alternatives for me to "tolerate". Do you have any real rationale for why this feature isn't implemented already? Or why it can't be implemented?

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 21, 2025):

Do you have any real rationale for why this feature isn't implemented already?

No one has needed it yet and/or nobody was motivated enough to do it.

And to be very clear about it: I don't have to make any excuses. You are using a product for free that other people have created in their free time. It is you who wants something from me or any other dev and thus it is up to you to provide reasoning for why someone else should do this for you. Unless you are willing to pay a developer to work on this, your only chance of this happening is providing good reasons for why this needs to be implemented. And that includes a good reason why you are not using the software as it is intended to be used.

You never provided any rationale for why it isn't.

Never said, it would be complicated. But the set of things that are not complicated to do but are not implemented in Mumble is more or less infinitely large so that alone is not a reason for why it should be implemented.

@Krzmbrzl commented on GitHub (Mar 21, 2025): > Do you have any real rationale for why this feature isn't implemented already? No one has needed it yet and/or nobody was motivated enough to do it. And to be very clear about it: I don't have to make any excuses. You are using a product for free that other people have created in their free time. It is _you_ who wants something from _me_ or any other dev and thus it is up to _you_ to provide reasoning for why someone else should do this for you. Unless you are willing to pay a developer to work on this, your only chance of this happening is providing good reasons for why this needs to be implemented. And that includes a good reason why you are not using the software as it is intended to be used. > You never provided any rationale for why it isn't. Never said, it would be complicated. But the set of things that are not complicated to do but are not implemented in Mumble is more or less infinitely large so that alone is not a reason for why it should be implemented.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 21, 2025):

Doesn't sound like you have had to hassle with people setting up Mumble personally. Or you would understand how much of a headache it is for new users to configure around this particular issue. It has been that way for years now.

How could the admins. of my group configure this differently then, if it is just a matter of "not using the software as intended?"

@BenjaminApprill commented on GitHub (Mar 21, 2025): Doesn't sound like you have had to hassle with people setting up Mumble personally. Or you would understand how much of a headache it is for new users to configure around this particular issue. It has been that way for years now. How could the admins. of my group configure this differently then, if it is just a matter of "not using the software as intended?"

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Mar 21, 2025):

If you don't want audio to bleed into other channels, those channels must not be linked. Which is the default, so at some time someone must have explicitly linked channels. This should be undone by unlinking them.

By the way: I never said nor meant to say that the feature request itself is invalid. I mostly wanted to figure out whether there might be alternatives.

@Krzmbrzl commented on GitHub (Mar 21, 2025): If you don't want audio to bleed into other channels, those channels must not be linked. Which is the default, so at some time someone must have explicitly linked channels. This should be undone by unlinking them. By the way: I never said nor meant to say that the feature request itself is invalid. I mostly wanted to figure out whether there might be alternatives.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@BenjaminApprill commented on GitHub (Mar 21, 2025):

The channels need to be linked so Fleet Commanders can Shout down to everyone else, without everyone else being configured to Shout to other linked channels. The only way around this is to assign a hotkey to the Whisper/Shout option to differentiate between the two options. There isn't an option to just toggle this tho; the only option is continuous transmission of the Whisper/Shout option by holding down the assigned key.

The only reason this is so frustrating is because Continuous transmission and Push-to-Talk, both have a toggleable feature for their voice transmission. It is not like I'm asking for an arm and a leg here... It is just the toggling of a boolean on key down, followed by a shift in the behavior using an if statement or a delegate re-assignment. You would literally just put the current code in an if statement, shift it with the state of the boolean that toggles on key down... The final behavior doesn't even need to change or be re-worked, it is just changing the activation of the code to be based upon a boolean state, not a key down state.

I have ten years of C# experience, but I doubt Mumble is written in C#. So my first inclination was not to try and add such a simple feature personally... Mumble is excellent otherwise for a free software. One of the best softwares I've ever used, free or not. I wouldn't even give Team Speak a second thought if some of this stuff was in the application; I wouldn't have to. Mumble is that good.

@BenjaminApprill commented on GitHub (Mar 21, 2025): The channels need to be linked so Fleet Commanders can Shout down to everyone else, without everyone else being configured to Shout to other linked channels. The only way around this is to assign a hotkey to the Whisper/Shout option to differentiate between the two options. There isn't an option to just toggle this tho; the only option is continuous transmission of the Whisper/Shout option by holding down the assigned key. The only reason this is so frustrating is because Continuous transmission and Push-to-Talk, both have a toggleable feature for their voice transmission. It is not like I'm asking for an arm and a leg here... It is just the toggling of a boolean on key down, followed by a shift in the behavior using an if statement or a delegate re-assignment. You would literally just put the current code in an if statement, shift it with the state of the boolean that toggles on key down... The final behavior doesn't even need to change or be re-worked, it is just changing the activation of the code to be based upon a boolean state, not a key down state. I have ten years of C# experience, but I doubt Mumble is written in C#. So my first inclination was not to try and add such a simple feature personally... Mumble is excellent otherwise for a free software. One of the best softwares I've ever used, free or not. I wouldn't even give Team Speak a second thought if some of this stuff was in the application; I wouldn't have to. Mumble is that good.

deekerman commented

2026-02-20 22:15:56 -05:00

Author

Owner

@AvatarTheOld commented on GitHub (Mar 30, 2025):

Hello, I'd like to join this request for toggleable Whisper/Shout functionality, it would be very useful for our server. We hold some Team versus Team events, where team members, normally, can only communicate with each other, within their groups\teams, and we use "Whisper/Shout" function to allow all participants to communicate with each other, globally, during votes, technical pauses, etc. And using "hold key" for Whisper/Shout proved to be uncomfortable for us. Adding an option to use Whisper/Shout in toggle (on\off) mode would be great.

@AvatarTheOld commented on GitHub (Mar 30, 2025): Hello, I'd like to join this request for toggleable Whisper/Shout functionality, it would be very useful for our server. We hold some Team versus Team events, where team members, normally, can only communicate with each other, within their groups\teams, and we use "Whisper/Shout" function to allow all participants to communicate with each other, globally, during votes, technical pauses, etc. And using "hold key" for Whisper/Shout proved to be uncomfortable for us. Adding an option to use Whisper/Shout in toggle (on\off) mode would be great.