This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Feature Request: add --vpp-smooth to Nvenc
#1
Hello Selur

I noted that in Nvenc it is available another denoise filter "--vpp-smooth". I was unable to find this option in Hybrid.
The syntax of the option is the following:

--vpp-smooth [<param1>=<value1>][,<param2>=<value2>],...
parameters
  • quality=<int> (default=3, 1-6)
    Quality of the filter. Larger value should result in higher quality but with lower speed.
  • qp=<int> (default=12, 1 - 63)
    Strength of the filter.
  • prec
    Select precision.
    • auto (default)
      Use fp16 whenever it is available and will be faster, otherwise use fp32.
    • fp16
      Force to use fp16. x64 only.
    • fp32
      Force to use fp32.
It could be useful add it in Hybrid.

Thanks
Reply
#2
will look into it over the weekend Smile
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
fp16 is broken here.
-> reported to the NVEncC author (https://github.com/rigaya/NVEnc/issues/295)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#4
Issue is fixed in NVEncC 5.25, build a new dev version and send you a link via pm.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
Tested with Nvenc 2.25 and now the precision equal to "fp16" is working, but the encoding speed drop from 439fps to 95fps. Probably the "speed" advantage is available only on 32bit OS, but on Windows 10 64bit, precision equal to "fp32" is faster.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)