I should probably have uploaded both the originals with the encoded so people could easily check and give their opinion.... Kinda would like to hear from people on it.

Here a zoom on the original, it is not overall good from the beginning but one can see there is no glitch in front of the man.

Weird.... it does not seem the glitch shows up in the SVT encoder version at CFR 36 and 7 in preset....
And AOM should be the better one of the 2, yet.... it seems clean.

Why did it break the image.......

I tried running the AOM at 25 CFR, preset 5, pretty high quality, and the glitch although a lot less, is still showing up - hard to capture.

It is weird because the AOM should be the better one of the two encoders and yet seems to have this weird issue of this glitch. Although the SVT encoder file is somewhat bigger, but still a lot smaller then the AOM 25 CFR, has none of it. Just weird.

Testing SVT a little more - I did try to fix the AOM with experimental 1 but apparently nothing worked. Tried compiling and all, but I do not know, it kinda did not have the features I was trying to get.

Weird enough SVT seems to work more like expected on 1 setting - like more CPU/Preset in AOM, as to say lover number - makes the files bigger, so it does not seem it really compresses more, but also makes the size bigger - kinda weird.
Were as SVT actually do make the files smaller when you use more CPU/Preset - and I guess quality as well.

All these nonsense games of working differently and positive and negative numbers, but apparently very very hard for programmers to have sanity and keep to some solid foundation overall. They just have do reinvent the wheel over and over again.

Higher numbers better quality makes sense, not lowering the number. But this is what we have with ffmpeg AV1 - and apparently CPU/Preset makes 2 different outputs on AOM and SVT, make it make sense.

Now of cause, AOM still have that weird glitch - which SVT just does not have. It is just weird. Trying to make a 0 SVT and see how that works out on Size and Quality, although takes the longest, being the highest setting.

I did find out that SVT also do make something, although a little difference of glitch at the place - but it is there. More like a black dot thing....

Anyway, it seems I have found out that changing -lag-in-frames might solve the issue - so I am doing some testing on that at the moment, but everything I have made until now, whether smaller then 35 as per default or more seems to solve the glitch. Dunno why..... Weird the default would be the one having the issue. But I am now trying 34 and 36 to see if it is there or disappear.