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.

Add AOMEnc 3.5.0
Hi Selur,

can you add the new AOM Encoder?

I dont know which Version you have integrated in Hybrid, but i think, you dont have the newest integrated?

iirc latest public release came with v3.3 since that was the latest at that time.
I add the newest builds whenever I release a public version.
So yes, the next release will container a build that is then up-to-date.

Since the command line didn't really change, you could replace the existing aomenc.exe with a newer one and add niot supported command line parameters through aomenc->Misc->Command line addition.

Cu Selur
ah, cool, i do that, thank you
What exactly do --enable-fwd-kf ? I dont get it, anyone know what it exactly do in the AOM Encoder? It says its forwarding Reference Frames, are there any benefits in activating it?
#5 explains it with an example also read:

In short: It's basically a way to improve the coding efficiency of the stream, similar to the effect of using I- vs. IDR-frames in HEVC. The only downside I see is for editing (especially cutting with smart-encode) such streams will probably get more tricky.
=> So normally this should stay enabled. (it's enabled by default, so the question should be: What reason could one have to disable it?)

Cu Selur

Forum Jump:

Users browsing this thread: 1 Guest(s)