Closed ranomier closed 10 years ago
Running multiple instances of mumble at the same time is not officially supported at this point as it might lead to unwanted interactions in features like the overlay or volume attenuation. As such we really do not want to expose this directly in the GUI. The real solution is multi-server support though I'm not sure what timeframe we are talking about for implementing that.
Mumble could disable the overlay and attenuation feature for the 2nd instance. That way they wouldn't be an issue, anymore. The thing is, that the multi-server support probably won't support different input devices for different clients/servers. And different certificates as well.
This would result in highly unexpected behavior. Having different configuration profiles for different servers in multi-server mode on the other hand doesn't sound to far fetched to me.
Upon startup, mumble shouldn't just refuse to start entirely when a client is already running. Instead it should prompt the user if it's okay to start twice. A message box could do the trick.