Deleting a branch is permanent. It CANNOT be undone. Continue?
#1737 Update AV1 reference implementation (libaom)
Closed
opened 2 months ago by Moonchild
·
10 comments
Labels
Milestone
No Milestone
Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
This issue currently doesn't have any dependencies.
Loading…
There is no content yet.
Delete Branch '%!s(MISSING)'
There are some audio issues with the version of libaom we have now -- most notably lack of audio. It looks like the bitstream format has changed after our initial implementation, so we need to pull at least a few updates (and preferably to the 1.0 implementation) of libaom.
Aside from that we probably want to update it further to 1.0 from Bug 1445683 (Firefox 63) but that’s more involved and might not be necessary right away.
ALTERNATIVELY: we can import libaom 1.0 straight away and write our own build system plumbing around it.
If my memory serves the import of bug 1314147 was complete, but the initial import included some extraneous config files that didn’t end up being needed and were cleaned up later.
I believe applicable patches from 1369950 have also already been ported.
That threw me off when looking at trying to apply the diff as it couldn’t find the files to patch.
OK I’m officially confused about the state of this now.
Checking what we have it seems to be a 1.0 version and the whole cmake parser thing is already in place.
Our source is not the same as what is in Firefox 63, but I can’t tell if what we have is older or newer than what’s there.
I’ll look into this and see if I can sort out what version we have. I’ll also look at updating it to something newer as time permits.
I’ve been puzzling on this and I think I got the updates in place. Will just have to test. Since we’re currently at 2.0.2 upstream that’s what I aimed for.
Well, shoot. I updated libaom successfully but it didn’t solve the sound issue on 9gag etc.
I’m reassigning this to you for when you have time, Travis. There’s something still wrong but I have no clue what and don’t know our media glue and/or demuxer code at all.OK so a few frustrating hours later it just seems like the audio issue on 9gag is an isolated thing that might not be related at all to the aom lib, but be something separate 9who knows might be crap encoding on their end that trips up the demuxer).
Discussed with Tobin, including the very mixed signals from the interwebs where part says AV1 is too immature and another part says it’s gonna be required, and there’s a serious lack of test opportunities in the wild so I give up.
@trav90 You could have a look if you have time but I think this issue as-is with the lib update should be considered done. i’ll spin off a follow-up to make it easier for users to select different codecs at their own leisure (or peril) from preferences, borrowing some Borealis code.
Sounds good.