Topic: [Feature] AV1 codec support

Posted under Site Bug Reports & Feature Requests

Requested feature overview description.
AOMedia Video 1 (AV1) is an open source, royalty-free video codec.
Why would it be useful?
AV1 can get about 30% higher data compression than VP9 can.
What part(s) of the site page(s) are affected?
The upload page will allow MP4 containers with AV1 and optionally Opus bitstreams inside.

Updated by KiraNoot

When even youtube only has experimental support right now, should we really be pioneering on this? Then considering that it is using MP4 as container and majority of people aren't able to play the file, I can already imagine the confusion and corrupted file flags.

https://caniuse.com/#feat=av1 at least this does seem better from h.265/HEVC.

With Android, the support was implemented in android 10, which is available for two phones, meanwhile VP9 has been supported since kitkat, meaning 96,2‬% compatibility already.

I'm also waiting for the day when users stop using VP8/Vorbis and use VP9/Opus instead.

Updated by anonymous

Mairo said:
Then considering that it is using MP4 as container and majority of people aren't able to play the file, I can already imagine the confusion and corrupted file flags.

Chrome, Firefox and Opera support AV1 . If someone tries to upload a video in an incompatible codec, the server will stop the upload as soon as it reads the header and redirect to an error message and a list of supported containers and codecs.

Updated by anonymous

felix_nermix said:
Chrome, Firefox and Opera support AV1 . If someone tries to upload a video in an incompatible codec, the server will stop the upload as soon as it reads the header and redirect to an error message and a list of supported containers and codecs.

I forgot to say that the file must be DASH compatible. In FFMPEG it is done with -movflags dash and in Handbrake it is done with the web optimised checkbox.

Updated by anonymous

felix_nermix said:
https://images.anandtech.com/doci/12601/12_AOMedia_AV1_Adoption_Timeline.jpg

Do you have any idea how technology and software adoption works in real life?

We have FLAC, AAC, Opus, etc. but still everyone uses MP3. We have WebP, PNG, etc. and yet, there's many using JPG including web services which are actively converting all image formats into JPG.

It took APNG 11 years to be adopted outside firefox and there's still people complaining how they can't see them.

It took years for people to get android updated over 4.4 so that they could see VP9 encoded WebM files and I still see people who complain when VP9 stuff doesn't play with their mobile device.

I do remember back when e621 did implement WebM support, adoption was already pretty well underway thanks to services like Gfycat, which were trying to make GIFs easier to handle and share by converting them into WebM.

Actually not even sure that will AV1 have the fate of JPG and h264 as in they are "good enough" with wide enough adoption rate that nobody wants to even bother with anything newer. Right now I can only see the comments of "why this isn't working for me" and corrupted file flags which I need to handle with no massive benefits.

Updated by anonymous

Mairo said:
Do you have any idea how technology and software adoption works in real life?

We have FLAC, AAC, Opus, etc. but still everyone uses MP3. We have WebP, PNG, etc. and yet, there's many using JPG including web services which are actively converting all image formats into JPG.

It took APNG 11 years to be adopted outside firefox and there's still people complaining how they can't see them.

It took years for people to get android updated over 4.4 so that they could see VP9 encoded WebM files and I still see people who complain when VP9 stuff doesn't play with their mobile device.

I do remember back when e621 did implement WebM support, adoption was already pretty well underway thanks to services like Gfycat, which were trying to make GIFs easier to handle and share by converting them into WebM.

Actually not even sure that will AV1 have the fate of JPG and h264 as in they are "good enough" with wide enough adoption rate that nobody wants to even bother with anything newer. Right now I can only see the comments of "why this isn't working for me" and corrupted file flags which I need to handle with no massive benefits.

AV1 is royalty-free and is backed by big technology corporations. The licenses are libre software licenses; no fees. In e621 , users are responsible for encoding the files; no server hardware upgrades needed. It will increase profit by a small percentage. Users just have to download a compatible browser or player.

Updated by anonymous

Users just have to download a compatible browser or player.

There is nothing about 'users have to download a compatible browser or player' that deserves the use of the word 'just'. From an admin point of view.

Users must DO NOTHING, AND HOPEFULLY NOTHING BREAKS.

Sure, that's a little exaggerated, but that is what every admin hopes for. You roll out a new feature and the users have to do NOTHING different in order to use it. That's because as soon as users are required to do something, some of them will do it wrong. And they won't just do it wrong in one way, each user will do things wrong in their own particular way. And this -- noise, essentially -- is mixed in with any legitimate reports of your site not handling AV1 properly.

AFAICS the minimum realistic bound for adding support for AV1 is: All major platforms support it, even if some of those implementations are buggy. At most, the user might have to click a checkbox saying that they opt in to the AV1 trial.

As the link Mairo gave shows, we are not there yet, in fact only desktop browsers support AV1 so far.

Updated by anonymous

savageorange said:
As the link Mairo gave shows, we are not there yet, in fact only desktop browsers support AV1 so far.

Android 10 supports AV1 and Opus natively and you can use VLC or other compatible players to play it in older versions.

Updated by anonymous

felix_nermix said:
AV1 is royalty-free and is backed by big technology corporations. The licenses are libre software licenses; no fees. In e621 , users are responsible for encoding the files; no server hardware upgrades needed. It will increase profit by a small percentage. Users just have to download a compatible browser or player.

felix_nermix said:
Android 10 supports AV1 and Opus natively and you can use VLC or other compatible players to play it in older versions.

The only reason why I have android 10 right now is because I bought brand new phone just now which had the update planned immidiately, but there's also new phones which only have 9 out of the box and many even more expensive phones which do not have updates to 10 even planned or models which might be only getting it years from now or only if user is knowledgeable enought to push in custom ROM. My previous nexus only got up to 8 even though it is google branded phone.

Like what about this is so hard to understand? We would be wasting resources of our site coder, who is already busy at doing beta website as is, to add support to a thing that majority of artists and users doing video uploads won't use to users who most likely can't play the files for years from now.

Sure, we can go the route of what we already demand from Apple device users and say to just use VLC, but I still do not see this being worthwile at this very moment when even mainstream services going to be using this still are only partially testing it. Would be differend story if we had more robust video streaming implementation with samples for multiple codecs like youtube or derpibooru does, but we don't.

Let's bring this back up when huge majority of people are on supported platform and/or browser and more userfriendly and widely used video encoders support it (handbrake is the most mainstream which is not planning of supporting it, webm for retards I have recommended a lot which prefers VP8 and can do VP9, xmedia recode is pretty used which doesn't list AV1 being supported in any way).

At least we do have some level of video support now, so that's already better than flash only that many other websites still have, biggest being furaffinity and I haven't seen them even planning on anything more still?

EDIT: Actually yeah, could you go to bother furaffinity instead to get them to move forward? Because all I'm finding on their forums are people complaining how HTML5 isn't ready for prime time, instuction to use puffin on mobile and just artists generally begging for support for something other than flash.

Updated by anonymous

felix_nermix said:
The upload page will allow MP4 containers with AV1 and optionally Opus bitstreams inside.

You can put an AV1 bitstream in a WebM container and it works on Chrome, Firefox, Edge, Opera and Waterfox.

Updated by anonymous

Microsoft Windows and most GNU/Linux distributions support it natively, also there are more devices with android 10. You can download a compatible browser or player for older versions.

Updated by anonymous

I can see that you're excited about this, but e6 isn't a good place for being on the cusp of technology. We want to support things that have been well established and have a large compatibility index. Android 10 is not on most consumer devices outside of high level enthusiast devices. Just, sit on this idea for a while until the technology matures and adoption improves.

Updated by anonymous

  • 1