Christopher Degawa

I can wait, main reason why I wish to merge this is so that in the future my pr's don't include so much whitespace changes

Can you try some more minimal reproduction cases? ```bash ffmpeg -i bbb-2m-4k-30fps.mp4 -an -c:v libsvt_vp9 -g 30 -minrate 6000k -maxrate 17400k -b:v 12000k -f null - # and ffmpeg -i...

I am able to reproduce the issue even on bare metal, so I will try to see if I can debug further as a note, I was able to do...

One thing that is possible is to use a well known clip such as big buck bunny and jelly fish and iterate through the tests and do vmaf, psnr, or...

It requires a lot of effort and cleanup to upstream the patch and we do not have the resources and time to do so at this moment.

Consider porting over https://github.com/AOMediaCodec/SVT-AV1/blob/master/.github/workflows/msvc.yml instead

> ffmpeg version N-98035-gda5634c9ef-g**801c8a961a**+2 Copyright (c) 2000-2020 the FFmpeg developers That `+2` at the end means that he has 2 extra patches on top of the base commit he pulled...

It's set by ```bash _patches=$(git rev-list origin/master.. --count) [[ $_patches -gt 0 ]] && do_addOption "--extra-version=g$(git rev-parse --short origin/master)+$_patches" ```

SVT was indeed originally designed for x86_64 only, but it is possible to extend the base technology to other architectures, as shown by SVT-AV1

Update: had a typo in my comment, meant to say, it's possible to extend to other architectures