从去年开始,Firefox, Chrome等主流浏览器和FFmpeg等视频播放器已经支持了VP9编码,如今YouTube官方博客宣布开始推广VP9编码视频。YouTube软件工程师Steven Robertson称,越来越多的人开始观看高分辨率的视频,我们需要一种视频格式能提供更高的分辨率但不增加带宽使用,VP9就是这样一种编解码器。


上图是以600Kbps网速观看VP9和H264编码视频的效果。如果你的带宽只能不缓冲观看480p清晰度的视频,那么你现在能在YouTube上流畅观看720p VP9编码视频。


VP9是一个由Google开发的开放格式、无使用授权费的视频压缩标准。VP9在开发初期曾被命名为Next Gen Open Video (NGOV,下一代开放视频)与VP-Next。VP9将是VP8的后继者。




VP9标准支持两种编码格式设定(Profiles):profile 0 和 profile 1。Profile 0支持4:2:0的色度抽样,Profile 1支持4:2:0、4:2:2和4:4:4色度抽样,并支持alpha通道和depth通道,另外Google也在考虑新增一个支援10位色彩深度的编码格式设定。



相关资源:VP9编码器 v1.3.0
已标记关键词 清除标记
世界上最快的VP9视频解码器 As before , I was very excited when Google released VP9 – for one, because I was one of the people involved in creating it back when I worked for Google (I no longer do). How good is it, and how much better can it be? To evaluate that question, Clément Bœsch and I set out to write a VP9 decoder from scratch for FFmpeg. The goals never changed from the original ffvp8 situation (community-developed, fast, free from the beginning). We also wanted to answer new questions: how does a well-written decoder compare, speed-wise, with a well-written decoder for other codecs? TLDR (see rest of post for details): as a codec, VP9 is quite impressive – it beats x264 in many cases. However, the encoder is slow, very slow. At higher speed settings, the quality gain melts away. This seems to be similar to what people report about HEVC (using e.g. x265 as an encoder). single-threaded decoding speed of libvpx isn’t great. FFvp9 beats it by 25-50% on a variety of machines. FFvp9 is somewhat slower than ffvp8, and somewhat faster than ffh264 decoding speed (for files encoded to matching SSIM scores). Multi-threading performance in libvpx is deplorable, it gains virtually nothing from its loopfilter-mt algorithm. FFvp9 multi-threading gains nearly as much as ffh264/ffvp8 multithreading, but there’s a cap (material-, settings- and resolution-dependent, we found it to be around 3 threads in one of our clips although it’s typically higher) after which further threads don’t cause any more gain. The codec itself To start, we did some tests on the encoder itself. The direct goal here was to identify bitrates at which encodings would give matching SSIM-scores so we could do same-quality decoder performance measurements. However, as such, it also allows us to compare encoder performance in itself. We used settings very close to recommended settings forVP8,VP9andx264, optimized for SSIM as a metric. As source clips, we chose Sintel (1920×1080 CGI content, source ), a 2-minute c
©️2020 CSDN 皮肤主题: 大白 设计师:CSDN官方博客 返回首页