Difference between revisions of "1.2.2"

From Mumble Wiki
Jump to: navigation, search
m (Improvements / Bug fixes)
m (Improvements / Bug fixes)
Line 21: Line 21:
* Fixed:
* Fixed:
G15 activation problems
# G15 activation problems
clientside chat URL handling
# clientside chat URL handling
error when upgrading database from 1.1.8 to 1.2.x
# error when upgrading database from 1.1.8 to 1.2.x
memory leak on certain configurations
# memory leak on certain configurations
many other bugs not listed
# many other bugs not listed
= Future =
= Future =

Revision as of 23:53, 16 January 2010




Mumble 1.2.2 is currently in development. Since we just released version 1.2.1 we are not yet sure which features we want to add for 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.

New features

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

User Information dialog

http://mumble.sourceforge.net/static/user_information_s.png We added a new dialog displaying useful information about other users on the server (e.g. packet loss). Depending on your authorization you can also inspect the users certificate and see his IP.

Improvements / Bug fixes

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

  • Made friend and server window icons skinnable (emblem-favorite.svg, etc).
  • Fixed:
  1. G15 activation problems
  1. clientside chat URL handling
  1. error when upgrading database from 1.1.8 to 1.2.x
  1. memory leak on certain configurations
  1. many other bugs not listed


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.