View Single Post
Old 22nd May 2017, 22:29   #77  |  Link
hello_hello
Registered User
 
Join Date: Mar 2011
Posts: 4,823
I tried the same thing with v3.1.2d after downscaling to SD, to make sure it wasn't SMDegrain trying to be clever according to the resolution, and while the LSFMod version is oversharpened, to illustrate the difference:

SMDegrain(thSAD=150)


SMDegrain(thSAD=150, contrasharp=500)
Note the bottom row of pixels again.


SMDegrain(thSAD=150)
LSFMod(strength=500)


Edit: Looking at those screenshots again (upscaled to 1080p on my TV), the Contrasharp=500 version has been sharpened/altered compared to the original, so maybe the contrasharp function is meant to be so subtle it's almost impossible to see the effect at normal settings, even when LSFMod is used??

I'll confess I assumed it'd have the same effect as LSFMod on it's own, but maybe that's not how it works. From the help file:

Contrasharp.
In the other hand if your parameter input is an integer, LSFmod() will be used instead. It will be much slower, but maybe better for certain sources. Its value will serve as a contrasharpening multiplier, use one around 50 for similar strength as Contrasharpening().


I assume a "contrasharpening multiplier" is not the same thing?

Last edited by hello_hello; 22nd May 2017 at 23:08.
hello_hello is offline   Reply With Quote