41–50 of 210 posts
Perhaps this might seem like a basic question, but why has it taken so long for processors to support AV1, given that it has been out for years?
Chicken & egg problem. No AV1 videos -> no pressure to add hardware support -> difficult to justify encoding videos in AV1
Microsoft Edge does support AV1, but weirdly only through a Microsoft Store extension [1], even though Chrome has support built-in. This actually really sucks because in practice hardly any normal consumers would bother to install a strangely named extension, and so web developers have to assume it's largely unsupported in Edge. Safari ties support to a hardware decoder, which I suppose is understandable to avoid acc…
What’s so special about AV1?
Compared to H.265/HEVC, AV1 has no patents and so anyone can implement it without worrying about licensing (there seem to 3+ groups that need to be paid off).
The trade-off is that it is more computation intensive than H.264 (as is H.265).
What’s so special about AV1?
Earlier quoted context omitted.
Chicken & egg problem. No AV1 videos -> no pressure to add hardware support -> difficult to justify encoding videos in AV1
I thought Google was the main one behind AV1. Couldn’t they use their position as one of the world’s biggest video platforms to break that chicken egg loop?
What’s so special about AV1?
Earlier quoted context omitted.
> improve upon HEVC on every metrics Color me the skeptic here, but which benchmark(s) are we talking about? Even h264 vs h265 is not a settled matter - if we truly consider every possible metric, including e.g. SW encoding.
For software encoding Intel suggest you can beat all the other classic SW encoders with AV1 as long as you have enough cores: https://d1qg7561fu8ubi.cloudfront.net/blog/BD-rate_fiugure5.... Lower and to the left is "better" Edit: resolution on that graph image is terrible but they've been sharing it for a while in slide decks so you can probably find better quality by following links from here: https://networkbuilder…
According to the article, it's supported by every browser except Edge. It will be interesting to see who ultimately ends up making a better IE, Safari or Microsoft. So far, it seems Safari is winning, given the ever growing set of standards they don't support, but maybe this is Edge trying to catch up?
Earlier quoted context omitted.
For software encoding Intel suggest you can beat all the other classic SW encoders with AV1 as long as you have enough cores: https://d1qg7561fu8ubi.cloudfront.net/blog/BD-rate_fiugure5.... Lower and to the left is "better" Edit: resolution on that graph image is terrible but they've been sharing it for a while in slide decks so you can probably find better quality by following links from here: https://networkbuilder…
SVT-AV1 has still a lot of visual quality issues. PSNR, SSIM, VMAF are useful metrics, but optimising for these won't get you the best encoder. x264 didn't get its reputation for going after PSNR and SSIM.
Earlier quoted context omitted.
Keep in mind that standards are moving slow, CODEC standards more so. The golden standard is still h264/AVC, which dates back to the nineties. This is primarily due to many appliances (set top boxes, cameras, phones, TVs) using the absolute cheapest hardware stack they can get their hands on.
+1 Indeed. Compared to other standards in streaming media, I'd say that AOMedia has found adoption a lot quicker. h265 (HEVC) was all but DoA until years after it's introduction Apple finally decided to embrace it. It is still by no means ubiquitous, mostly due to patent licensing, which significantly drives up the price of hardware in single digit dollars price range. Anecdotally, consider that Apple's HTTP Live Str…
Really? Muxing generally doesn't require one to decode the actual data - merely shuffle around blocks of data with memcpy() so should be really cheap.