From Mumble Wiki
Revision as of 16:14, 19 January 2010 by Slicer (talk | contribs)
Jump to: navigation, search




Release timeline
Mumble 1.2.0
Mumble 1.2.1
Mumble 1.2.2
in development

Mumble 1.2.2, the successor of 1.2.1, is currently in development. To hit the last upload date for the next Ubuntu version we plan to release 1.2.2 somewhere near the end of this month. Everything on the list below already has been completed and will be in the release. It is not yet certain which additional features will be ready to be in a release by the end of this month.

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.

New features

As development of 1.2.2 just started we did not yet implement a lot of new features.

User Information dialog

We added a new dialog displaying useful information about other users on the server (e.g. packet loss). Depending on your privileges, you can also inspect the users' certificates and see their IP addresses. Note that the server has to be version 1.2.2 or greater for the client to be able to display this dialog.



  • Made friend and server window icons skinnable (emblem-favorite.svg, etc, see Skinning)
  • Improved connect speed to big servers with lots of users and comments
  • CELT version bump
  • Other small changes here and there

Bug fixes

This list contains notable bugs we fixed since the last release.

  • server side database upgrade bug (only occured when updating from 1.1.8 directly to 1.2.1)
  • G15 activation problems
  • memory leak on certain configurations
  • many other minor fixes


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. I really mean this; what filtering did for the audio quality in Mumble it also does for video quality.