https://blogs.gnome.org/rbultje/2015/09/28/vp9-encodingdecod...
You get the same image quality at a lower bitrate and faster decoding.
VP9 encoding is much slower, but Intel's SVT-VP9 encoder is getting over 300 frames per second on the right hardware:
https://www.phoronix.com/scan.php?page=news_item&px=SVT-VP9-...
The VP9 encoder also tends to smooth ( clean ) the video rather than working with the noise ( Not a problem for most short internet video ), which even as of today x264 is very very good and possibly the best at.
The point is that you can select the VP9 encoder that makes the most sense for your use case. You can choose from EVE, libvpx, Intel SVT-VP9, Intel Quick Sync, NGCodec, mobile device encoders, etc.
* I'm not sure what the "ffh264" decoder they're talking about is. My understanding is that pretty much everyone is using libx264 for both encoding and decoding. Maybe the latter is more performant?
* Using SSIM to pick "equal quality" files will probably not give very accurate results.
* SVT-VP9 is, if I'm not mistaken, a hardware encoder. One of the issues with these is that they require some significant tradeoffs to get better speed, so they'll have worse quality than a software encoder at the same bitrate. If you go with software you really pay the price when it comes to encoding time.
ffh264 is FFmpeg's decoder. libx264 only does encoding, not decoding.
SVT-VP9 is a software encoder, specially optimized for Intel Xeon Scalable and Intel Xeon D processors.
http://www.compression.ru/video/codec_comparison/hevc_2018/
http://www.compression.ru/video/codec_comparison/hevc_2018/#...
Their subjective testing methodology:
http://www.compression.ru/video/codec_comparison/hevc_2018/p...
15 years ago there were people who said exactly the same thing about MPEG4-ASP (eg. divx/xvid). It all comes down to Moore's law and hardware acceleration.
Another thing about hardware acceleration is that on many platforms you really did not want to push 622Mbit/s worth of raw chroma-subsampled YUV FullHD video across whatever interconnect to your GPU, so moving things like motion compensation into GPU hardware was only way to actually play FullHD content. And this is also part of the reasons why is H.264 somehow special today.
There are always format fanboys but it really wasn't anything like that because the MPEG4-ASP experience still had problems for the average user (it wasn't a big win on file size/quality, compatibility was not a given, people still had to pay for licensed players, etc.).
In contrast, I think H.264 hit the threshold where it's good enough for the average person and you basically never hit the case where a file doesn't work for the person you shared it with because even though it's license-restricted, most operating systems and browsers include support. Moving away from that is going to be hard because most people will not see much advantage — AV1 is clearly better on file-size but most people aren't hitting limits on a regular basis and the feedback loops are often missing (e.g. you hit play in Netflix on your phone — how many people would have any way to tell how much of their data plan that used?).
Instead of focusing on the client, what about the server? How happy would Netflix be to reduce their outbound traffic by 20%? I'm guessing it's quite happy.
https://medium.com/netflix-techblog/toward-a-practical-perce...
For an article talking about the magic of compression, comparing to uncompressed png makes a lot more sense than, say, starting your comparisons to something that's already compressed like jpeg.
That png is a much closer pedagogocal relation to the previously discussed "3D array of pixels, 2 in space and one in time" that he's building on.
I believe it is one reason why MPEG is working on EVC, a Royalty Free Video Codec based on H.264 with a target of 20% improvement.
Hopefully the industry as a whole, mainly Apple and Google can settle on something that is better than H.264 and JPEG.
Right now Google will not support H.265, and Apple isn't fully on board with AV1 yet.
EVC won't deliver much value. VP9 is already royalty-free, already outperforms x264, and already has broad support and use.
Apple should add VP9 support now (like everyone else has) and work to add AV1 support in the future.
> P-frames are frames that will encode a motion vector for each of the macro-blocks from the previous frame.
Actually, P-frames can use data from multiple previous frames, not just the last one.
I think it's worth pointing out, as well, that even though we've technically surpassed H.264 with newer codecs like H.265, VP9, and AV1, all of which are roughly 20%-50% more efficient, this has required tremendous increases in encoding complexity. H.264 is special - it seems to occupy a kind of inflection point on the complexity / efficiency curve. It's far more efficient than previous codecs like Xvid, WMV, and so on, but at the same time even a lot of underpowered devices from over a decade ago can easily play it. We're not likely to see tradeoffs that good again in the video codec space.