4 ms·

Note, no support for hardware encoding was announced by Qualcomm. Decoding only. This seems to repeat the trajectory of VP9, where it exists and is supported so

Note, no support for hardware encoding was announced by Qualcomm. Decoding only. This seems to repeat the trajectory of VP9, where it exists and is supported solely thanks to YouTube, while the whole world is utilising H.265 for everything else, including recording video on smartphones. It very well may be AV1 and H.266 will play the same roles in the future.

ksec 5y ago
It will be interesting to see if Google will include AV1 encoder in their Pixel Phone and eventually give away hardware AV1 encoder IP. But Google has never been a coherent company.
- aesh2Xa1 5y ago
  What does it take to integrate an encoder into hardware? Could you explain? AV1 is an open, royalty-free codec, so I don't understand how Google could help competitors. Maybe Google is in a place to give away knowledge, although I doubt they know more about a competitor's chip design.
  - oefrha 5y ago
    The reference software implementation (libaom) is royalty-free. Any company can come up with their own proprietary implementation, including in hardware. There are no royalty-free hardware designs at the moment.
    - lapinot 5y ago
      Well, the actual standard is royalty-free and that's what we usually mean by royalty-free in this context. A royalty-based standard requires you to purchase a license for developing your own implementation of it.
      - oefrha 5y ago
        Yes. The codec itself and the reference implementation are both royalty-free, so we’re both right. The implementation part is more relevant here since gp was asking about it.
- ZeroGravitas 5y ago
  Google bought a chip design company and has been releasing codec chip designs for years, probably during the VP8 era but certainly VP9. It's now at the stage when they don't really need to it mostly just happens.
axiolite 5y ago
> This seems to repeat the trajectory of VP9, where it exists and is supported solely thanks to YouTube, while the whole world is utilising H.265 for everything else, including recording video VP9 came too close on the heels of VP8. Thanks to WebRTC in particular, VP8 encoding support is everywhere. AV1 has a lot more backing, thanks in no small part to the H.265 licensing mess.
- threeseed 5y ago
  > VP8 encoding support is everywhere At least for iOS/OSX it is only supported for WebRTC and nothing else.
ZeroGravitas 5y ago
> the whole world is utilising H.265 for everything else. This is very hyerbolic. There's plenty of places that the HEVC licencing catastrophe stopped its use. The release of 3 more MPEG codecs that compete with it is not a good sign for example.

ksec 5y ago

It will be interesting to see if Google will include AV1 encoder in their Pixel Phone and eventually give away hardware AV1 encoder IP. But Google has never been a coherent company.

aesh2Xa1 5y ago
What does it take to integrate an encoder into hardware? Could you explain? AV1 is an open, royalty-free codec, so I don't understand how Google could help competitors. Maybe Google is in a place to give away knowledge, although I doubt they know more about a competitor's chip design.
- oefrha 5y ago
  The reference software implementation (libaom) is royalty-free. Any company can come up with their own proprietary implementation, including in hardware. There are no royalty-free hardware designs at the moment.
  - lapinot 5y ago
    Well, the actual standard is royalty-free and that's what we usually mean by royalty-free in this context. A royalty-based standard requires you to purchase a license for developing your own implementation of it.
    - oefrha 5y ago
      Yes. The codec itself and the reference implementation are both royalty-free, so we’re both right. The implementation part is more relevant here since gp was asking about it.
ZeroGravitas 5y ago
Google bought a chip design company and has been releasing codec chip designs for years, probably during the VP8 era but certainly VP9. It's now at the stage when they don't really need to it mostly just happens.

axiolite 5y ago

> This seems to repeat the trajectory of VP9, where it exists and is supported solely thanks to YouTube, while the whole world is utilising H.265 for everything else, including recording video VP9 came too close on the heels of VP8. Thanks to WebRTC in particular, VP8 encoding support is everywhere. AV1 has a lot more backing, thanks in no small part to the H.265 licensing mess.

threeseed 5y ago
> VP8 encoding support is everywhere At least for iOS/OSX it is only supported for WebRTC and nothing else.

ZeroGravitas 5y ago

> the whole world is utilising H.265 for everything else. This is very hyerbolic. There's plenty of places that the HEVC licencing catastrophe stopped its use. The release of 3 more MPEG codecs that compete with it is not a good sign for example.