Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optical Flow Fruc Grid Size and other artifact issues questions #586

Closed
VisionHDR opened this issue May 9, 2024 · 3 comments
Closed

Optical Flow Fruc Grid Size and other artifact issues questions #586

VisionHDR opened this issue May 9, 2024 · 3 comments

Comments

@VisionHDR
Copy link

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:

Parameters

double Convert to double framerate, this mode will result in higher performance.

fps=<int>/<int> Convert to framerate specified, the performance will be low compared to double.

Examples

Example: Convert to double framerate
--vpp-fruc double

Example: Convert to 59.94fps
--vpp-fruc fps=60000/1001
@rigaya
Copy link
Owner

rigaya commented May 10, 2024

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.

@rigaya
Copy link
Owner

rigaya commented Aug 1, 2024

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.

@rigaya
Copy link
Owner

rigaya commented Aug 12, 2024

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.

@rigaya rigaya closed this as completed Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants