rigaya / NVEnc

NVENCによる高速エンコードの性能実験
https://rigaya34589.blog.fc2.com/blog-category-17.html
Other
1.1k stars 114 forks source link

vpp-fruc is not workling correctly #565

Closed rainman74 closed 8 months ago

rainman74 commented 9 months ago

Tests: --vpp-fruc double -> works and is incredibly fast ✅🚀 --vpp-fruc fps=60000/1001 -> is ignored, double is used ❌ --vpp-fruc fps=50000/1001 -> is ignored, double is used ❌ --vpp-fruc fps=50.0 -> works, but you get debug messages ❌ --vpp-fruc fps=60.0 -> works, but you get debug messages ❌

You get tons of these debug messages:

Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4351 kb/s, remain 0:00:19, GPU 20%, VE 6%, est out size 9.2MB
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4357 kb/s, remain 0:00:17, GPU 19%, VE 6%, est out size 9.1MB
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4357 kb/s, remain 0:00:17, GPU 19%, VE 6%, est out size 9.2MB
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4359 kb/s, remain 0:00:17, GPU 15%, VE 5%, est out size 9.3MB
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4367 kb/s, remain 0:00:18, GPU 21%, VE 5%, est out size 9.4MB
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4374 kb/s, remain 0:00:15, GPU 26%, VE 6%, est out size 9.3MB
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4
Optical Flow Grid Size: 4 fps, 4380 kb/s, remain 0:00:15, GPU 14%, VE 4%, est out size 9.4MB
rainman74 commented 9 months ago

and in help output there is missing a carriage return after ...(fast):

--vpp-fruc [<param1>=<value>][,<param2>=<value>][...] enable frame rate up conversion filter. params double double frame rate (fast) fps=<int>/<int> or <float> target frame rate

rigaya commented 9 months ago

Thank you for your report, fps=x/x will be fixed in next release (you can still try --vpp-fruc fps=59.94 at this time for 60000/1001).

You get tons of these debug messages:

Yes, this is unavoidable as this is coming from FRUC library (or NVOF library) and I were not able to find ways to suppress them.

Please note that fps mode ( = non double mode) is really slow as it requires re-initialization every frame, due to limitation of the library.

rigaya commented 9 months ago

The fps in fraction issue and the help will be fixed in NVEnc 7.44.

rainman74 commented 8 months ago

Problem is fixed!