2 ms·
The problem is that reference implementations of AV1 are 100x slower than HEVC at encoding. And so hardware decoding may ether be (a) impossible on current devi
by threeseed 8y ago
The problem is that reference implementations of AV1 are 100x slower than HEVC at encoding. And so hardware decoding may ether be (a) impossible on current devices or (b) likely to destroy battery life. The only option is some breakthrough in the complexity of the encoding algorithm.
These issues unless solved relegates AV1 to being a Youtube and Netflix format and pretty much irrelevant for everyone else.
- 1ris 8y agoI means that the reference implementation is slower. Nothing more. Reference implementations are not about performance, they are documentation. They are not supposed to be used for anything else but documentation. Your conclusion is ridiculous. There is absolutely not reason assume that av1 is fundamentaly more power consuming that HEVC. A tank uses more gasoline that a VW Beetle. This statement is true, and as irrelevant as your statement.
- ksec 8y ago>Reference implementations are not about performance, they are documentation. They are not supposed to be used for anything else but documentation. That is valid for all H.262 , H.263, H.264 and H.265, as well as the up coming H.266 VVC. The current Av1 isn't a documentation. Nor it is a Reference Implementation in the regards of all MEPG codec. The AV1 is built on a working, professionally made libvpx encoder built on VP9. >There is absolutely not reason assume that av1 is fundamentaly more power consuming that HEVC. It definitely will be more complex, both encoding and decoding. Its fundamental complexity is much higher then HEVC, how far could they optimise so they are close to 5 - 10x of HEVC is a different story.
- aseipp 8y ago> Youtube and Netflix and pretty much irrelevant for anyone else I like it when the goalposts move in such a way that "used by services in over 50% of US households and services where 70% of all video usage come from mobile, and offers excellent bandwidth improvements for millions of users" apparently means AV1 is a failure, somehow, based on preliminary numbers for a use case (encoding) that largely isn't relevant to mobile devices (and will improve dramatically over time making encoding more usable, anyway, as all prior codecs did.) Unfortunately for the AV1 designers, they could have realized this fatal flaw sooner, had they only consulted the grand expertise of..... a random internet forum user.
- BurningCycles 8y ago>And so hardware decoding may ether be (a) impossible on current devices or (b) likely to destroy battery life. The development of the codec has been done with constant input from the hardware developers who are backing AV1 (Intel,AMD,Broadcom,NVidia etc) in order to make it effective when used with hardware acceleration. Just watch some of the developer presentations on Youtube. Your fear that all the streaming and hardware giants would cooperately develop a codec that won't be effective on mobile hardware is unfounded.
- clouddrover 8y agoSo use VP9 until AV1 is ready. Netflix uses it for their mobile encodes: https://medium.com/netflix-techblog/more-efficient-mobile-encodes-for-netflix-downloads-625d7b082909 https://medium.com/netflix-techblog/more-efficient-mobile-en... YouTube and Netflix adopting VP9 before others doesn't make VP9 irrelevant for everyone else. The same is true for AV1.