5 ms·

I don't see how VP9 hardware decoders shipping late means that H.265 wins? There's zero H.265 content on the web right now, so if anything H.265 would need to c

I don't see how VP9 hardware decoders shipping late means that H.265 wins? There's zero H.265 content on the web right now, so if anything H.265 would need to catch up. Also, the ffvp9 software decoder in Firefox is quite efficient. Hopefully Chrome will eventually ship it too.

rasz_pl 10y ago
90% of TV series and movies I watch come in x265 at half x264 file size.
- HNSucksAss 10y ago
  If you're talking about HEVC torrents, you should admit that they look like ASS.
tornadoboy55 10y ago
VP9 is already in all Chromium based browsers. And no, its not nearly as efficient, because there's no hardware acceleration/ You can clearly see this in any Chromium browser: Watch a YouTube video without the H264ify extension and Activity Monitor open. Your 'Energy Use' will spike to about 100. With H264ify its only 40. Safari even stays in the upper 20s.
- TD-Linux 10y ago
  But it uses the libvpx decoder, not ffvp9. https://blogs.gnome.org/rbultje/2014/02/22/the-worlds-fastest-vp9-decoder-ffvp9/ https://blogs.gnome.org/rbultje/2014/02/22/the-worlds-fastes... Also check that you're getting the same resolution on both. H.264 requires more bits, so you might be getting a lower resolution (which also takes less energy to decode).
  - tornadoboy55 10y ago
    Both are 1080p60FPS. Also, VP9 will never be more efficient than H264 on my machine since I have a 2015 13" Macbook Pro, and that model only has H264 acceleration in the CPU. And the 2015 Pro is more modern than 90% of the machines out there..
    - clouddrover 10y ago
      But doesn't that have an Intel Iris 6100 in it (https://www.apple.com/macbook-pro/specs-2015/ https://www.apple.com/macbook-pro/specs-2015/)? If so you should have accelerated VP8 and VP9 decoding. Maybe it's not exposed by the drivers on macOS.
      - tornadoboy55 10y ago
        Nope, only VP8 (which is dead). I meant fixed hardware acceleration (Intel Quick Sync). Draws a lot less power than the GPU. This is the full Quick Sync acceleration sheet for each generation: Version 1 (Sandy Bridge) Quick Sync was initially built into some Sandy Bridge CPUs, but not into Sandy Bridge Pentiums or Celerons. Version 2 (Ivy Bridge) The Ivy Bridge microarchitecture included a "next-generation" implementation of Quick Sync. Version 3 (Haswell) The Haswell microarchitecture implementation is focused on quality, with speed about the same as before (for any given clip length vs. encoding length).[citation needed] It has seven hard-coded quality/performance levels (called "target usages"), compared to the three in previous generations. The highest-quality TU1 setting is intended to be higher quality than Ivy Bridge's version, and the highest speed TU7 setting should be faster, higher-quality, and more battery-friendly for mobile devices. This generation of Quick Sync supports the H.264/MPEG-4 AVC, VC-1 and H.262/MPEG-2 Part 2 video standards. Version 4 (Broadwell) The Broadwell microarchitecture adds VP8 hardware decoding and encoding support. Also, it has two independent bit stream decoder (BSD) rings to process video commands on GT3 GPUs; this allows one BSD ring to process decoding and the other BSD ring to process encoding at the same time. Version 5 (Skylake) The Skylake microarchitecture adds a full fixed-function H.265/HEVC main/8-bit encoding and decoding acceleration, hybrid and partial HEVC main10/10-bit decoding acceleration, JPEG encoding acceleration for resolutions up to 16,000×16,000 pixels, and partial VP9 encoding and decoding acceleration. Version 6 (Kaby Lake) The Kaby Lake microarchitecture adds full fixed-function H.265/HEVC Main10/10-bit encoding and decoding acceleration & full fixed-function VP9 8-bit & 10-bit decoding acceleration & 8-bit encoding acceleration.[13][14]
        clouddrover 10y ago
        Broadwell has VP9 acceleration with the right drivers: https://communities.intel.com/thread/59216 https://communities.intel.com/thread/59216 https://en.wikipedia.org/wiki/Broadwell_(microarchitecture)#New_features https://en.wikipedia.org/wiki/Broadwell_(microarchitecture)#... So you just have a driver problem. Apple was playing with adding WebP support in beta versions of iOS a while back. So maybe they'll add WebP and WebM support in the next major version of macOS and iOS.

rasz_pl 10y ago

90% of TV series and movies I watch come in x265 at half x264 file size.

HNSucksAss 10y ago
If you're talking about HEVC torrents, you should admit that they look like ASS.

tornadoboy55 10y ago

VP9 is already in all Chromium based browsers. And no, its not nearly as efficient, because there's no hardware acceleration/ You can clearly see this in any Chromium browser: Watch a YouTube video without the H264ify extension and Activity Monitor open. Your 'Energy Use' will spike to about 100. With H264ify its only 40. Safari even stays in the upper 20s.

TD-Linux 10y ago
But it uses the libvpx decoder, not ffvp9. https://blogs.gnome.org/rbultje/2014/02/22/the-worlds-fastest-vp9-decoder-ffvp9/ https://blogs.gnome.org/rbultje/2014/02/22/the-worlds-fastes... Also check that you're getting the same resolution on both. H.264 requires more bits, so you might be getting a lower resolution (which also takes less energy to decode).
- tornadoboy55 10y ago
  Both are 1080p60FPS. Also, VP9 will never be more efficient than H264 on my machine since I have a 2015 13" Macbook Pro, and that model only has H264 acceleration in the CPU. And the 2015 Pro is more modern than 90% of the machines out there..
  - clouddrover 10y ago
    But doesn't that have an Intel Iris 6100 in it (https://www.apple.com/macbook-pro/specs-2015/ https://www.apple.com/macbook-pro/specs-2015/)? If so you should have accelerated VP8 and VP9 decoding. Maybe it's not exposed by the drivers on macOS.
    - tornadoboy55 10y ago
      Nope, only VP8 (which is dead). I meant fixed hardware acceleration (Intel Quick Sync). Draws a lot less power than the GPU. This is the full Quick Sync acceleration sheet for each generation: Version 1 (Sandy Bridge) Quick Sync was initially built into some Sandy Bridge CPUs, but not into Sandy Bridge Pentiums or Celerons. Version 2 (Ivy Bridge) The Ivy Bridge microarchitecture included a "next-generation" implementation of Quick Sync. Version 3 (Haswell) The Haswell microarchitecture implementation is focused on quality, with speed about the same as before (for any given clip length vs. encoding length).[citation needed] It has seven hard-coded quality/performance levels (called "target usages"), compared to the three in previous generations. The highest-quality TU1 setting is intended to be higher quality than Ivy Bridge's version, and the highest speed TU7 setting should be faster, higher-quality, and more battery-friendly for mobile devices. This generation of Quick Sync supports the H.264/MPEG-4 AVC, VC-1 and H.262/MPEG-2 Part 2 video standards. Version 4 (Broadwell) The Broadwell microarchitecture adds VP8 hardware decoding and encoding support. Also, it has two independent bit stream decoder (BSD) rings to process video commands on GT3 GPUs; this allows one BSD ring to process decoding and the other BSD ring to process encoding at the same time. Version 5 (Skylake) The Skylake microarchitecture adds a full fixed-function H.265/HEVC main/8-bit encoding and decoding acceleration, hybrid and partial HEVC main10/10-bit decoding acceleration, JPEG encoding acceleration for resolutions up to 16,000×16,000 pixels, and partial VP9 encoding and decoding acceleration. Version 6 (Kaby Lake) The Kaby Lake microarchitecture adds full fixed-function H.265/HEVC Main10/10-bit encoding and decoding acceleration & full fixed-function VP9 8-bit & 10-bit decoding acceleration & 8-bit encoding acceleration.[13][14]
      - clouddrover 10y ago
        Broadwell has VP9 acceleration with the right drivers: https://communities.intel.com/thread/59216 https://communities.intel.com/thread/59216 https://en.wikipedia.org/wiki/Broadwell_(microarchitecture)#New_features https://en.wikipedia.org/wiki/Broadwell_(microarchitecture)#... So you just have a driver problem. Apple was playing with adding WebP support in beta versions of iOS a while back. So maybe they'll add WebP and WebM support in the next major version of macOS and iOS.