AV2 when?Will they use it to upgrade the standard of AVIF?
>>108443047Use case?
>>108443047AV1 improvement, VVC is already created.Buy it today!
>>108443047>Will they use it to upgrade the standard of AVIF?you can build libavif right now with AV2 support, retard
>>108443047AV2 is realistically like a decade away from being a thing, the spec needs to be finalized, the software encoder/decoder optimized, security vulnerabilities patched, etc. Even then I doubt AV2 will be used for anything less than 8K video resolution similar to how people still use x264 for compressing DVDs instead of AV1.>Will they use it to upgrade the standard of AVIF?That would be a very bad idea as the main driver of AVIF adoption today is that it can use existing AV1 hardware decoders which means you can load a non-animation sequence of images into a valid AV1 video file, have them decode as "video", recover them back as individual AVIF images later, all while being 100% decodable by AV1 hardware decoding. AV2 would break this. https://desuarchive.org/g/thread/107717483/#107717483The AVIF hardware limitations aren't the best (still destroys 512x512 8-bit HEIC) but they create an excellent compatibility layer across devices that unifies them in a sort of "safety box". You can still create non-hardware compliant AV1 streams like YUV 444 12-bit at 100 megapixel resolution and Dav1d will gladly decode it (assuming it's even used as a fallback on devices with AV1 hardware decoding) but people on low end devices aren't going to be happy about the lag or potentially their computer locking up which already happens with highres JPEG XL using this parameter: --override_bitdepth=10
>>108443647fuck me i've been using AV1 to compress my older 4k h264 vr porn stash but leaving 8k as HEVC. should i not be?
>>108443678HEVC is not at all suited for 8K res which is why they're punking out VVC to fix that. AV1 does way better but AV2 is going above and beyond so VVC can die stillbirth. >HEVC replaces macroblocks, which were used with previous video standards, with CTUs which can use larger block structures of up to 64×64 pixels and can better sub-partition the picture into variable sized structures.https://en.wikipedia.org/wiki/Coding_tree_unit>Similar to the concept of a macroblock, superblocks are square-shaped and can either be of size 128×128 or 64×64 pixels. Superblocks can be divided in smaller blocks according to different partitioning patterns. The four-way split pattern is the only pattern whose partitions can be recursively subdivided. This allows superblocks to be divided into partitions as small as 4×4 pixels.https://en.wikipedia.org/wiki/AV1
>>108443047AVIF has been deprecated by JXL. It won't be upgraded to a newer video codec.
>>108444205Does JXL have hardware support now? Not having that was the biggest downside afaik.
>>108443647>AV2 is realistically like a decade away from being a thingMore like 3-4 years. Bit stream is gonna be 2-3, then maybe a year before first semi-usable software encoders appear. They won’t be mature but they will be kind of usable.
>>108444565Yeah but you'll need like a 9800X3D to decode 4K AV2. AV1 still has problems being accepted because you need like a 2500K CPU or better and apparently expensive Tesla EVs have CPUs weaker than that...https://streaminglearningcenter.com/codecs/tesla-rolls-back-youtube-from-av1-to-vp9.html
>>108443747>can die stillbirthIt already did, SVT-AV1 closed the gap a few months ago at a comparably ludicrous speed to VVC
