Closed VisionHDR closed 3 months ago
Yes, there is artifacts created with --vpp-fruc, and you should not expect too much from it. There are also many limitations, like it can only generate in 8bit and does not support 10bit. (I've actually added this for test and fun)
There are surprisingly very little parameter available for NVOFA FRUC, only parameter which can be set is actually the time of the frame to interpolate, and that is all. Therefore, you cannot change Grid Size or something else. There will be no parameter added unless the FRUC library is updated in the future.
NVEnc 7.58 improves handling of FRUC when used with fps mode. It will greatly improve performance, and removes most of "Grid Size" messages. However, I feel artifacts are still there, it shall be limitation of FRUC library.
I'll close the issue, as --vpp-fruc fps mode has been improved in NVEnc 7.58, and remaining problems shall be limitation of FRUC library.
Hello,
I was trying to completely understand the behavior and usage of this specific function.
I use the "double" command and it works fast, but there are severe artifacting here and there i don't think it's the proper output considering i use a powerful NVidia GPU and if it were like this, Nvidia should never even use it for anything. I notice pixels moving and even shaking randomly, making the whole idea of motion interpolation using optical flow completely useless.
I notice there are "Grid Size", where is always set to "4". How do i change this (if even matters to help reducing the artifacting?)
Is there any scene detection threshold or setting you are going to add? This may be good to avoid these issues?
What are the complete options to use? Because you only mention: