This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

When will the AV1 codec be implemented in Hybrid?
#10
(10.10.2018, 05:30)Selur Wrote: Had a quick look at the muxing call used by Hybrid, which is for example:
ffmpeg -y  -i "E:\Temp\test_05_23_16_7610_01.ivf" -vcodec copy -map 0:0  -aspect 181818:100000 -metadata handler_name="Hybrid 2018.10.09.1" -r 25 "E:\Output\test.webm"
since Hybrid sets the 'handler_name' tag I suspect that the problem with the tagging is probably a MediaInfo bug with webm.
Since calling
ffmpeg -i "E:\Output\test.webm"
on the output, properly shows
[libaom-av1 @ 0000024874713980] 1.0.0-708-gdf7131064
Input #0, matroska,webm, from 'e:\Output\test.webm':
 Metadata:
   HANDLER_NAME    : Hybrid 2018.10.09.1
   ENCODER         : Lavf58.18.104
 Duration: 00:00:17.16, start: 0.000000, bitrate: 240 kb/s
   Stream #0:0: Video: av1 (Main), yuv420p(tv), 640x352, SAR 1:1 DAR 20:11, 25 fps, 25 tbr, 1k tbn, 1k tbc (default)
   Metadata:
     DURATION        : 00:00:17.160000000
At least one output file must be specified

Regarding the aomenc crash I would need a more details (read sticky), probably a debug output level 9 of the job processing.

Cu Selur

Thanks a million.

Now I finally figured out why the rav1e encoded IVF file couldn't be converted to the webm/mkv format via the media-autobuild_suite built FFmpeg. The libaom ver. 1.0.0-729-ged7d0d090 was the culprit. It's the most recent version available the most recent version that doesn't conflict with libvpx as of now (see m-a_s issue #954 that I opened to report this bug), and the media-autobuild_suite script fetches this version in order to build aomenc.exeaomdec.exe along with libaom-av1 in FFmpeg. It is, however, problematic and the resulting libaom-av1 constantly fails to decode AV1 frames. And since I couldn't encode an AV1 mkv video from an AVC mp4 file via libaom-av1, it is certain that this version of libaom-av1 has an issue with encoding as well.

I downloaded the Zeranoe version, and it solves all the problems. There, the libaom-av1 version is 1.0.0-691-gbb8157b89.

Since Hybrid 2018.10.07.1 succeeds in rav1e encoding including webm conversion while failing in aomenc encoding and webm conversion ― based on my test ― I suspect that the libaom version that Hybrid adopts has an issue with encoding while it is OK with decoding. Well, this is just my guess, and I need to double check this with further testing. I will set up the debug mode and set the output level to 9 and report the log file if the problem persists.

(BTW, I can see that the libaom version of Hybrid 2018.10.07.1 is 1.0.0-708-gdf7131064. Correct me if I'm wrong.)

And about the metadata tag, I could confirm that it was a MediaInfo bug. Thanks for letting me know.
Reply


Messages In This Thread
RE: When will the AV1 codec be implemented in Hybrid? - by JKyle - 10.10.2018, 08:34

Forum Jump:


Users browsing this thread: 3 Guest(s)