The following warnings occurred: | |||||||||||||||
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.3.12-nmm1 (Linux)
|
When will the AV1 codec be implemented in Hybrid? - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: When will the AV1 codec be implemented in Hybrid? (/thread-649.html) Pages:
1
2
|
RE: When will the AV1 codec be implemented in Hybrid? - Selur - 10.10.2018 yes, libaom used should be: commit df7131064bf37fb5c7ee427ba564c31a2ed8bbbe (HEAD -> ab-suite) The whole av1 support, like all av1 tools is still experimental. Cu Selur Ps.: will test aomenc encoder later today RE: When will the AV1 codec be implemented in Hybrid? - Selur - 10.10.2018 Just tried encoding with aomenc and muxing worked fine here. -> would need a debug output of the job processing to see the calls which crash for you. Cu Selur RE: When will the AV1 codec be implemented in Hybrid? - JKyle - 11.10.2018 (10.10.2018, 17:34)Selur Wrote: Just tried encoding with aomenc and muxing worked fine here. Hi. I just tried aomenc and my job succeeded too. It's very weird but maybe there was something wrong with my first setting. BTW, the minimized version of the job command line log shows a misleading description about the muxing process. It says it's creating an avi file, not an av1 file or a webm file with ffmpeg. I think this is a typo. Can you please fix this? Thanks. RE: When will the AV1 codec be implemented in Hybrid? - Selur - 11.10.2018 Lol, yes thats a typo, will fix. Command line should be finde. |