mumble-voip/mumble

Description When switching the Audio Output System from PulseAudio to PipeWire, there's a leftover output called Mumble. We can clearly see it under the following command, but it's also observable in hyprpwcenter: gpu-screen-recorder --list-application-audio mpd.MPD PipeWire Output Zen Mumble Playback As you can see, both Mumble and Playback are present, and Playback is the name Mumble uses when set to PipeWire, read more about that under #7292 Steps to reproduce Switch from Audio Output System from PulseAudio to PipeWire. Observe the leftover Mumble output application in hyprpwcenter, GPU Screen Recorder etc. Restart Mumble to confirm the Mumble output is gone and only Playback persists. Mumble version 1.5.915 Mumble component Client OS Linux Reproducible? Yes Additional information No response Relevant log output Screenshots No response

Description When Audio Output System is set to PipeWire, Mumble appears as Playback instead of Mumble. This can be verified with applications such as: hyprpwcenter GPU Screen Recorder gpu-screen-recorder --list-application-audio mpd.MPD PipeWire Output Zen Playback Steps to reproduce Set Audio Output System to PipeWire Use on of the apps listed in examples to observe audio output applications Mumble version 1.5.915 Mumble component Client OS Linux Reproducible? Yes Additional information Oddly enough, it appears as Mumble Playback under pavucontrol: I am not familiar with the codebase, but this could be the cause: mumble/src/mumble/PipeWire.cpp Line 377 in 532706b m_engine = std::make_unique< PipeWireEngine >("Playback", this, processCallback); I would open a PR changing this to Mumble, but I am genuinely not sure whether it was intentionally set to Playback. Re

Description When an external ICE application (like gameserver or web backend) shuts down gracefully, it should unregister the ServerAuthenticatorPrx so mumble server doesn't try to route authentications and rely on own configuration. however because there is no removeAuthenticator() i tried to use nullptr and MumbleServer::ServerAuthenticatorPrx() . which unfortunately both throw InvalidCallbackException. and this leaves the the old dead authenticator inside the map which lead to the next user attempting to sign in a 5 seconds freeze in the mumble server before dropping the authenticator . Steps to reproduce 1- connect to mumble using ice and use setAuthenticator(); 2- disconnect from mumble ice . 3- reconnect or don't reconnect either way . 4- the next user trying to log in will cause the mumble server to freeze for about 5 seconds before returning to it original authentication method Mumble version 1.5.857 Mumble component Server OS Windows Reproducible? Yes Additional information No

Context I'm creating a plugin to provide positional audio for a game. And I want to add a radio/walkie-talkie system on top of that. The player will craft a radio in game, turn it on and select a channel. Then the player press a PTT on the radio to talk to everybody with the same channel selected. I was planning to use whisper/shout capability to do that. Description To be able to create my radio/walkie-talkie system my plugin must have access to the whisper/shout state using the plugin API. With a way to set targets and enable/disable the whispering status. For the question "How the plugin will know who must be in the target list ?" I was planning to use user's positional audio identity to store the user channel. And then having another addition in the API to retrieve users identity ? (I'm not sure about that part ..) My other idea to implement this, is more server centralized using a ICE to handle whispering states. But same as above the current ICE API doesn't provide a way to mani

Context I have a private server that I am only using with a specific group of friends. As all of us are registered in the server, I'd prefer if I could disable connections to the server to unregistered users. For now I'm stuck with setting a very long random password. Description I'd like for a configuration option to be introduced that denied all unregistered users from connecting, even with the password, to improve the security of the server from brute force attacks. Mumble component Server OS-specific? No Additional information It would also be great if this could be toggled while the server is running, for example to allow a new member to connect/register without having to restart the server, but I understand if this would be difficult to implement. This could also be introduced with one time passwords (issue #6061 talks about them).