![]() ![]() Before then, you're just attempting to build use cases rather than actually having one. AV1 as a format will only make sense at scale and with everyone having decoding support (eg: a video platform like YouTube or Netflix saving millions a year on bandwidth because of how much video they serve and people's laptops having AV1 decoding support built into their processors and/or video cards). ![]() And while technically true, my time transcoding an AV1 file would be better spent by taking another 15 minutes to download an h.265 of comparable quality and doing anything else for 2+ hours. 00001% of people that actually would benefit from "receiving an AV1 file in order to transcode it" to get a better image is vanishingly small. Getting a good result takes at least some level of knowledge to know what all these encoding options do and how to best utilize them. I've personally found all of the presets on Handbrake to "not be great". ![]() Most people don't know how to get a proper conceptual export out of a program like Davinci Resolve or Premiere. The folks with the technical knowledge to do this well are vanishingly small. And then the other issue of how many people would know that they "could" or "should" transcode to another format. It also raises the question of why anyone would distribute a file that people can't immediately view in the first place, which I would argue is bad practice. The increased cost to bandwidth is more than offset vs hours and CPU cycles used by everyone else. That would only be compounded if instead of just 1 person downloading that file, it was a thousand or ten-thousand. But, when considering time as a value: spending hours transcoding that to another format is very compute and time inefficient. It could be stated as being "less bandwidth efficient" to send an h.265 file of comparable image quality. Anyway, that's a digression from the main point that AV1 is years away at best from wide scale adoption.Ĭlick to expand.While "technically true", it doesn't make sense to generate AV1 files, send those to people, and then have them go through a very lengthy transcoding process. Most of that all has to do with "money" and who controls what formats. Google is majorly backing AV1 (to the point of even using it as an option on YouTube), but Apple wants to stick with h.265. ![]() However the problem there is that it's semi-politicized. That will likely increase adoption faster than anything else. The way to push its relevance though is to get decoding (and perhaps encoding) support into cellphones/tablets. I think it will be at least the same before AV1 really enters into the conversation. It took Intel, as an example, the better part of 10 years to support the myriad of features h.265 has. Most people don't have any hardware with even partial AV1 decoding support, and we're years off of full support. But that then comes with the compromise of either needing highly specialized decoders or brute force to decode. AV1 is incredible, in terms of what it's able to do with compression. This is great in the sense of trying to push a format forward, but for most it won't move the needle anytime soon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |