VP8 Codec SDK "Cayuga" Released
Thursday, August 4, 2011 | 4:08 PM
Today we're making available "Cayuga," the third named release of the VP8 Codec SDK (libvpx). Note that the VP8 format definition has not changed, only the SDK. You can download the Cayuga libvpx snapshot (version 0.9.7) from the WebM Project Downloads page or clone it from our Git repository.
As promised, for Cayuga we targeted more areas for encoder speed improvements. Using our previous release ("Bali") as a benchmark, we’ve seen the following VP8 encoder improvements on x86 processors.
- +11.5% "Best" mode (at speed 0)
- +21.5% "Good" mode (at speed 0)
- +22.5% "Real-time" mode (at speed 6, a typical speed for videoconferencing applications)
- +35% "Best" mode (at speed 0)
- +75% "Good" mode (at speed 0)
- +52% "Real-time" mode (at speed 6)
We saw the following improvements on ARM processors:
- On ARM Cortex A9 with Neon extensions, real-time encoding of video telephony content is 35% faster than Bali on single core and 48% faster on multi-core.
- On the NVIDIA Tegra2 platform, real time encoding is 40% faster than Bali.
- Improved the datarate control in one-pass realtime compression.
- Improved one-pass variable bitrate (VBR) visual quality by average ~7% across a large collection of videos.
- Improved video conferencing user experience through error concealment, a feature that produces high visual quality frames even under conditions of substantial packet loss.
- Improved the ARM v6 and v7 encoders and decoders through greater use of SIMD features and strong use of cache prefetching.
- Alok Ahuja
- Alexis Ballier
- Ronald Bultje
- Rafael Ávila de Espíndola
- Ralph Giles
- Stefan Holmer
- Mike Hommey
- Taekhyun Kim
- Aron Rosenberg
- Joshua Bleecher Snyder
- Thijs Vermeir


6 comments:
Sergey said...
Make please --end-usage=3 (const quantizer = no adjust quantizer) from VP7 is the most favourable mode detailed elaboration/bitrate the Internet of conferences.
August 5, 2011 7:03 AM
Prescience500 said...
No news on SSIM quality gains?
August 9, 2011 6:26 PM
Sergey said...
August 17, 2011 8:15 AM
Sergey said...
The glitch with a mode -p 1 --end-usage=2 --cq-level= in 0.9.7-p1 and isn't corrected - at different CQ grow only intermediate frames, golden frames with what were at --cq-level=60 same and remain at --cq-level=20. The Same and at 0.9.6.1.
Besides -p 1 golden frames are exposed too often - they should is put in 1,5 times less often than in VP7.
Google, expel coders for a pizza and employ professionals.
August 17, 2011 9:08 AM
Lou Quillio said...
@Sergey Feature requests and bug reports should be raised here: http://code.google.com/p/webm/issues/list
Be sure to explain your issue clearly, and without snark. Thanks.
LQ
August 17, 2011 12:41 PM
Sergey said...
I don't write bugreports because I know English only through the translator.
Has tried to write bugreport, I hope there will understand.
August 17, 2011 4:36 PM
Post a Comment