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?
https://www.reddit.com/r/AV1/comments/e0...&context=3 explains it with an example also read:
https://www.reddit.com/r/AV1/comments/t5..._guide_to/
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