Difference between revisions of "1.2.1"

From Mumble Wiki
Jump to: navigation, search
m (Status)
Line 5: Line 5:
 
Mumble 1.2.1 is currently in development. Since we just released version [[1.2.0]] a few days ago we are not yet sure which features we want to add for this release.
 
Mumble 1.2.1 is currently in development. Since we just released version [[1.2.0]] a few days ago we are not yet sure which features we want to add for this release.
  
= New features =
+
== New features ==
 
As development of 1.2.1 just started we did not yet implement any new features.
 
As development of 1.2.1 just started we did not yet implement any new features.
  
= Planned features =
+
== Planned features ==
 
This list contains some of the features we plan to implement for this release. This is not a fixed list and might change anytime. Once a feature got implemented we will move it to the  
 
This list contains some of the features we plan to implement for this release. This is not a fixed list and might change anytime. Once a feature got implemented we will move it to the  
  
== Extended Audio wizard ==
+
=== Extended Audio wizard ===
 
The audio wizard will receive a new page which contains most of the options users tend to change the first time they run Mumble. This includes codec quality and latency settings, Text-To-Speech to Sound pack switching and maybe some other things.
 
The audio wizard will receive a new page which contains most of the options users tend to change the first time they run Mumble. This includes codec quality and latency settings, Text-To-Speech to Sound pack switching and maybe some other things.
  
Line 17: Line 17:
 
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.
 
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.
  
== Video ==
+
=== Video ===
 
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.
 
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.
 
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.

Revision as of 13:59, 12 December 2009

1.2.1

Status

http://mumble.sourceforge.net/static/my_mumble_full_snap.png

Mumble 1.2.1 is currently in development. Since we just released version 1.2.0 a few days ago we are not yet sure which features we want to add for this release.

New features

As development of 1.2.1 just started we did not yet implement any new features.

Planned features

This list contains some of the features we plan to implement for this release. This is not a fixed list and might change anytime. Once a feature got implemented we will move it to the

Extended Audio wizard

The audio wizard will receive a new page which contains most of the options users tend to change the first time they run Mumble. This includes codec quality and latency settings, Text-To-Speech to Sound pack switching and maybe some other things.

Future

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.

Video

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.