• 0 Posts
  • 8 Comments
Joined 1Y ago
cake
Cake day: Jun 18, 2023

help-circle
rss



Honestly, I switched to ddg as soon as Google rolled out amp, and found that it was better than google at finding relevant results



Netflix rolled out av1 support for a handful of Samsung smart TV’s about a year and a half ago, then kinda shoved the project under the rug and never mentioned it again. My guess is that the added costs of having to store their entire library twice plus having to re-encode everything made it uneconomical. Besides, av1 doesn’t have a bandwidth advantage over h.265; all of the comparisons that Google likes to use to show off the codec are av1 vs h.264, which is pretty sneaky and misleading imo.


No arguments about it being a good TV, but the vast majority of people do not have shiny new LG oled TV’s. Hell, most people are still using old 1080p lcd’s without any smart TV features, and the people who have got new TV’s over the past few years tend to skew heavily towards buying relatively cheap 4k TV’s that may not have any smart TV features (after all; if i already have a roku/apple tv/chromecast/etc that covers all of my streaming needs, why would I pay a huge premium to get these features a second time?)


The trouble with AV1 is that it’s about a decade behind h.265 in terms of hardware support. Most people aren’t upgrading their gpus every single generation, so by the time AV1-compatible hardware starts to see significant market share, it’s pretty likely that h.266-compatible hardware will be on the market as well.

Of course, there’s also software encoders; but benchmarks of current software encoders put av1 anywhere between 50-1000x slower than x265 for comparable quality and bitrate.

It’s definitely cool that people are working on a royalty-free video codec, but h.265 is the undeniable king for the time being.