Mumble 1.2.3, the successor of 1.2.2, is currently in development. It is not yet certain which features will be in this release.
We rely on your testing and feedback to improve Mumble, if you find any bugs in the current stable or in a recent snapshot please report them using our bugtracker. If you think we lack an important feature take a look at the corresponding feature tracker.
List of new features, improvements and bug fixes already in place for the upcoming release.
The overlay is now highly customizable. Instead of only being able to control position and size as in previous released you can now freely reorder, scall, show/hide its components giving you the freedom to make it look just the way you want it.
It can also display additional useful information like your Framerate (FPS).
As of popular request Mumble now has the ability to prioritize certain speakers. Meaning that once a priority speaker starts talking all other players in the channel are attenuated.
- Display of the full blown client user interface inside the overlay. On the Windows platform it is fully interactive just like the desktop client.
- Optional auto reconnect to last used server
- The client is now able to operate in WASAPI exclusive mode. This drops the latency overhead of the audio output considerably but has the disadvantage that no other application can input/output sound from that device.
Notable changes to Murmur, the server component of Mumble.
- There are now separate Ice secrets for read and write operations
- Support for priority speakers
- Logs in Database can be switched off (murmur.ini: "logdays=-1")
This section takes a peek into the future of Mumble's development. These features are what we would like to implement in future releases. There is no guarantee that we will ever get around implementing them however.
The current overlay texture system is designed for high speed texture transfers in a format that happens to be 60 pixels high. This is no coincidence.
Using H.264 encoding, 80x60 pixels is small enough that we can encode a 15fps video stream with minimal CPU impact. The bitrate will also be low (lower than existing audio streams), and with a bit of filtering the quality is near perfect. We really mean this; what filtering does for the audio quality in Mumble, it will also do for the video quality of the overlay.