Difference between revisions of "Future"
(Created page with 'This page 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…') |
|||
| Line 1: | Line 1: | ||
| + | {{ReleaseTimeline}} | ||
| + | |||
This page 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 page 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. | ||
Revision as of 10:52, 4 February 2011
NOTE: This release and version documentation is no longer being updated. Please see our announcements on our blog or our GitHub releases.
This page 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. We really mean this; what filtering does for the audio quality in Mumble, it will also do for the video quality of the overlay.
