When will the AV1 codec be implemented in Hybrid?

[JKyle]

I'll look into it whether using ffmpeg for muxing to 'webm' and restricting AV1 to webm would be a solution.
+ I'll ask Mosu whether the av1 inside webm specificaiton is finished.

Cu Selur

Hi.

I'm a happy user of FFmpeg (CLI) on Windows 10 built by the media autobuild suite and recently I decided to try encoding an AV1 video in FFmpeg via libaom-av1 and in rav1e (since FFmpeg does not wrap rav1e yet) respectively.

First off, FFmpeg encoding via libaom-av1 to an mkv file fails for no reason ― it simply stops encoding. (My FFmpeg build is the most recent one.) I faithfully followed the AV1 encoding guide on the FFmpeg site but it doesn't help. I didn't know why but I found out from your post that mkvmerge doesn't support muxing an AV1 IVF file as of yet.

Second, rav1e encoding succeeded but converting the resulting IVF file to the webm format via FFmpeg fails. I don't have any idea how I can do this. BTW, the IVF file plays OK in MPC-HC albeit not seekable.

Seeing the Hybrid update notice yesterday that the new version 2018.10.07.1 includes 'AV-1 support through aomenc and rav1e, I decided to see how Hybrid does it. And the result is that Hybrid does it successfully in rav1e encoding albeit in the webm format only but fails (muxing crashes) as well in aomenc encoding.

My aomenc encoding setting that caused crashing is as follows:

And the error message:

But I think it's pretty weird since the rav1e encoding succeeds using almost the same muxing process. Anyway, here's my question:

According to the Jobs log, it seems that Hybrid muxes the resulting IVF file from rav1e encoding to an avi file via FFmpeg and gets a webm file. How is that possible and what command line does Hybrid use?

Second, the resulting webm file from rav1e encoding has the Hybrid version info as a 'Movie Name' metadata field.

I think you should change the metadata field name for the Hybrid version info.