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?
#9
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
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Messages In This Thread
RE: When will the AV1 codec be implemented in Hybrid? - by Selur - 10.10.2018, 05:30

Forum Jump:


Users browsing this thread: 1 Guest(s)