Learning to use LSFmod

[carlmart]

I am trying to learn to better use the LSFmod filter capabilities.

Until now I had been mostly using its smode parameter. But on some restoration cases it has proven too much using just that parameter. I believe it might be useful to use the other parameters. But for that I need to know what they are or do.

The filter is is here:

http://avisynth.org/mediawiki/LSFmod

Even if maybe my questions may sound rather basic for many, here they go.

1) When there's no parameter listed to fill in, like on "strength [int]", what do I put inside?

2) Smethod (sharpen method): what does Kernel mean or what the parameter Min/Max controls?

3) Skernel: what does this parameter modify?

4) Lmode: how does limit affect sharpening in over or undershoot? It softens the borders?

5) The parameters "overshoot" or "undershoot" should go before or after Lmode?

6) Soothe: what is temporal stabilization?

I have other questions, but let's start with those so I can begin testing with reasonable parameters and not all over the place.

[LaTo]

1. Just put nothing

2. Kernel and Min/Max are 2 way to sharpen

3. Don't touch this unless you know what you are doing

4. It avoid some artifact to appear when sharpening (example: halo)

5. Like you want, it is the same

6. It help to have a more stable picture

[carlmart]

First of all thanks for the filter. It seems to work quite well, and I hope to learn to manage it.

I have just used it to correct things on a DVD that I have that was originally released in letterbox 4:3. The film is "The bride wore black", by François Truffaut, and apparently there's no other release but this.

When I view it on my 42" plasma, there are black bars on all sides. If I zoom it with the TV, I lose the subtitles. If I zoom it with the DVD player, I lose screen information. BTW: this is the case with almost every letterboxed 4:3 film I have, so I am willing to process them all as long as I can preserve the quality.

In this sense, LSFmod came very handy. The script I ended up using was:

TFM()
TDecimate(Mode=1)
lsfmod(smode=5, Smethod=3, kernel=19, soothe=true)
Lanczos4Resize(720,480,0,66,0,-66)

After some trim tests, I processed the whole film with that. Compared to the original the results were spectacular. The only problem is it took quite long to process it. Usually I take 3-4 hours with a regular DVD to resize it. This one took 13.

[LaTo]

The only problem is it took quite long to process it. Usually I take 3-4 hours with a regular DVD to resize it. This one took 13.

try defaults="fast"

[Didée]

And also, crop the major part of black borders beforehand:
crop(0,64,-0,-64)
TFM()
TDecimate(Mode=1)
lsfmod(smode=5, Smethod=3, kernel=19, soothe=true)
Lanczos4Resize(720,480,0,2,0,-2)
Same result, but 26.6% less area to process for all the filters.

[carlmart]

Thanks LaTo. I have added "fast".

Thanks Didée. Which is the reasoning to get to that figure combination?

When AR is larger than 16:9 I've learnt to compute the results quite well, using resize and addborder. But it's been hard to get to a way to compute other sizes like 1.33 or 1.66.

In any case, after that long conversion I burned a DVD-RW with the results. And I think it needs further work using the filter combo I tried.

To start with halos have popped up where didn't seem to be any. So I now think I have to be careful on what to use.

Using dehalo is not quite an option, as I know it even less and the last time I tried it it had softened things too much, like a fog filter.

Perhaps I should show here a jpg of the same image with and without LFSmod for you to see what I mean.

[poisondeathray]

To start with halos have popped up where didn't seem to be any. So I now think I have to be careful on what to use.

Using dehalo is not quite an option, as I know it even less and the last time I tried it it had softened things too much, like a fog filter.

Perhaps I should show here a jpg of the same image with and without LFSmod for you to see what I mean.

One option is to lower the sharpening strength

[carlmart]

One option is to lower the sharpening strength

Tried that. Things improved and looks less flat than without it on the resize.

Another thing I tried was DegrainMedian, as the film or copy is rather grainy. Things seem to improve a bit, but it gets slightly artificial, like plastic.

Is there a way to increase the screen size in AvsP? You can see the changes, but they are difficult to see sometimes, and they are there. Textures is what I am talking about, skin texture particularly.

But there's a halo or chromashift, don't know how to call it really, on the left, on black things. It's on the original and pops up a little with LSFMod. Curing that might help improve resolution. It's certainly a telecine problem.

[carlmart]

After I completed my first run with this project, I realized I was cropping the image on all sides, not just the black bars. My fault.

Before I go further with the image filters, I really have to learn to resize things from letterbox 4:3 properly. Perhaps you can help me understand how.

The problem is with images whose ratio is less than 1.77 (16:9). How can I compute things properly on such cases?

Just to be specific with my example: the ratio of my letterbox image is 1.66. How do I set the crop, resize and addborder variables to get me a non-cropped, pilar sized 16:9 720:480 image?

[manono]

Just to be specific with my example: the ratio of my letterbox image is 1.66. How do I set the crop, resize and addborder variables to get me a non-cropped, pilar sized 16:9 720:480 image?
I already explained how I did it in your Videohelp.com thread about this:

http://forum.videohelp.com/topic372789-30.html#2005813

Or, put another way, find the original crop values (I use GKnot for this) and plug into FitCD the new cropped resolution and set it as DVD 720. In this example I cropped 48 from both the top and bottom:

[carlmart]

In fact today I went look for help on another thread of mine you helped me with, in Videohelp.

On it you suggested using this combo:

Crop(0,60,0,-60)
Lanczos4Resize(720,480)

Changing the crop values you can adjust to several ratios. Using it in AvsP until I cropped nothing, I got to this combo:

Crop(0,46,0,-44)
spline36resize(720,480)

FitCD is still a tough nut to crack to me. Let's hope I get to manage it sometime.

[manono]

On it you suggested using this combo:

Crop(0,60,0,-60)
Lanczos4Resize(720,480)
You have to cite the thread or post. That's a standard 4:3 to 16:9 script, but for films 1.78:1 or wider. It wouldn't apply to 1.66:1 films unless you want to crop well into the active video and turn it into 1.78:1. If converting your 1.66:1 4:3 DVD to 16:9, given your crop values, I'd do it like this:

Crop(0,46,0,-44)
LanczosResize(656,480)
AddBorders(32,0,32,0)

[Gavino]

Crop(0,46,0,-44)
spline36resize(720,480)
That's clearly wrong as it does not produce a pillar-boxed result. So the resize needs to be to a width less than 720 and the last step needs to be adding borders to the sides to bring the width up to 720.

However, I don't understand how FitCD arrives at the numbers shown in Manono's post, where it resizes 720x386 to 656x480. Working it out manually, I get this:

Changing height from 386 to 480 means width becomes 720 * 480/386 (at original PAR)
Allowing for change in DAR from 4:3 to 16:9 means compress horizontally to 3/4 width,
hence final width = 720 * 480/386 * 3/4 = 672 (instead of 656)

[carlmart]

Manono & Gavino:

You're both right. I do not want to crop things.

Manono, when I loaded your FitCD numbers on AvsP I get an image that has borders all over. In fact I should get an image with pillars on the sides only.

But I would love to understand how to load values in FitCD.

Gavino, I must be a real blockhead (you don't have to agree!) but I couldn't understand your reasoning.

Maybe this time I can learn to do things right in less than 1.77 frames.

[manono]

However, I don't understand how FitCD arrives at the numbers shown in Manono's post, where it resizes 720x386 to 656x480.
If you turn on ITU resizing in FitCD you get pretty much what you figured. I had mentioned this earlier in carlmart's other thread over at Videohelp.com to which I linked several posts up:
Then the only remaining decision is whether or not to use ITU resizing.
http://forum.videohelp.com/topic372789-30.html#2005813

I use it almost always myself, although I don't think the eye will be able to tell one way or the other, and carlmart's having enough trouble understanding the basics of how FitCD works without adding another level of complexity with ITU resizing:

[carlmart]

This is what I get if I load that script in AvsP.

[mavinashbabu]

Sorry carlmart, a bit off topic question, Manono can you please tell the software that you used in the attached screenshots, it seems to help a lot... Thanks

[g-force]

Just to be specific with my example: the ratio of my letterbox image is 1.66. How do I set the crop, resize and addborder variables to get me a non-cropped, pilar sized 16:9 720:480 image?

What you're asking for is not possible unless you:
a) squish the height
b) over-crop the top and bottom
c) add black borders to the sides

If one of these options is of interest to you, then please state which way you want to go. You're basically trying to fit a square peg in a rectangular hole. So you've either gotta use a smaller square, or shave off the sides of the square to make it more rectangular.

BTW, I'll answer the question you posed to Didée, "Which is the reasoning to get to that figure combination?"
He took your original script, which had this at the end:

Lanczos4Resize(720,480,0,66,0,-66)

which is the same as cropping 66 off the top and bottom and resizing the result to 720x480.

So, he was thinking, why not just crop by a nice (divisible by 16) number like 64 from the top and bottom first, do all the "slow" stuff, and then do another crop by 2 (top and bottom) at the end to get to the 66 of of your original script. Now I assume that you have since realized that this crops your video too much, as you have recently stated that 46 off the top and 44 off the bottom is the maximum without over-cropping. BUT he was working under the assumption that your original script had the correct values.

-G

[Gavino]

Gavino, I must be a real blockhead (you don't have to agree!) but I couldn't understand your reasoning.
Basically, it goes like this:
- in your 4:3 DVD, actual picture occupies area 720x390 (based on your info that you need to crop off 90 pixels to remove black bars);
- for some reason, FitCD only uses 386 of these, so I took that as my starting point;
- you want to scale that up to occupy the full height available of 480, so to maintain AR, you need to scale the width by the same factor, ie 480/386;
- but our final target has 16:9 DAR while the original is 4:3, so we need to squeeze it anamorphically by a further factor of 3/4 (ie (4/3)/(16/9)) to allow for the different PARs;
- therefore, actual width required = 720 * 480/386 * 3/4 = 672

@Manono - this reasoning is independent of whether ITU resizing is used or not, it just requires it to be used consistently - for both input and output, or for neither - and then its effect cancels out. From the results shown, it seems that FitCD always uses it for output calculations, but for input only uses it when selected.

[carlmart]

What you're asking for is not possible unless you:
a) squish the height
b) over-crop the top and bottom
c) add black borders to the sides

The last option would be the one.

What I think I am doing is eliminating as much black space as possible, and for that I would have to zoom the image and anamorphize it. That is convert the 4:3 "spheric" image I have now into a 4:3 anamorphic one, containing a 16:9 image with pillar bars on the sides.

BTW, I'll answer the question you posed to Didée, "Which is the reasoning to get to that figure combination?"
He took your original script, which had this at the end:

Lanczos4Resize(720,480,0,66,0,-66)

which is the same as cropping 66 off the top and bottom and resizing the result to 720x480.

Apparently I have to start thinking this in a different way. I need to know which is the better combination, the one that will be better quality wise.

[carlmart]

- therefore, actual width required = 720 * 480/386 * 3/4 = 672

So how do I feed that up into the script to make it work properly?

Like this:

Crop(0,46,0,-44)
LanczosResize(672,480)
AddBorders(24,0,24,0)

It certainly looked quite right when I fed it to AvsP.

[g-force]

So how do I feed that up into the script to make it work properly?

Like this:

Crop(0,46,0,-44)
LanczosResize(672,480)
AddBorders(24,0,24,0)

It certainly looked quite right when I fed it to AvsP.

This would be a bit more accurate by my calculations:

Crop(0,46,0,-44)
LanczosResize(664,480)
AddBorders(28,0,28,0)

-G

[g-force]

Apparently I have to start thinking this in a different way. I need to know which is the better combination, the one that will be better quality wise.

Your original script and Didée's script will give you exactly the same output. His just gets there faster.

-G

[carlmart]

This would be a bit more accurate by my calculations:

Crop(0,46,0,-44)
LanczosResize(664,480)
AddBorders(28,0,28,0)


Why?

Numbers precision will help me better in future cases, so I don't have to come back here for help.

[Gavino]

If you use 390 in place of 386 in my calculation, you get g-force's result. As I explained, 390 corresponds to your crop values, but I started with 386 as that is what FitCD was using, and the point of my question was to query the calculation used by FitCD.

[carlmart]

If you use 390 in place of 386 in my calculation, you get g-force's result. As I explained, 390 corresponds to your crop values, but I started with 386 as that is what FitCD was using, and the point of my question was to query the calculation used by FitCD.

OK. In any case the difference is very slight.

FitCD sets 386 as "accurate", but keeps 390 for maximum height. Perhaps to keep "dirty" lines out?

As it is now, and adding up all your suggestions, my script should be:



SetMTMode(2,2)
MPEG2Source("d:\bride wore black\bride.d2v")
defaults="fast"
Crop(0,44,0,-42)
TFM()
TDecimate(Mode=1)
Undot()
DeGrainMedian(limitY=2,limitUV=3,mode=1)
lsfmod(smode=3, Smethod=3, kernel=19, soothe=true)
LanczosResize(664,480,0,2,0,-2)
AddBorders(28,0,28,0)


It provides quite a cleaner image. I would like to have a larger preview in AvsP to check on DeGrainMedian results instead of burning a test DVD.

[Gavino]

I would like to have a larger preview in AvsP
Did you know AvsP has a "Zoom" option under the Video menu?
I've been using it for over 18 months and only realised this the other day. :)

[carlmart]

Did you know AvsP has a "Zoom" option under the Video menu?
I've been using it for over 18 months and only realised this the other day. :)

Then let me tell you about another one I just discovered, exploring your tip!

Zoom increases the garbage when going for more %, like all zoom options generally do.

There's another option more interesting there: "Fill window". That is the one I was looking for, which popped up when I processed an audio script.

[carlmart]

Now for the final touch on what I might do to improve the image.

Please look at the halo that borders the character's dark coat and on his chin.

Is there a way I can correct that? Making that halo more visible is what makes using LSFmod critical. But LSFmod compensates quite well the resizing, so it would be nice to use it.

[manono]

Removed.

[BigDid]

Hi,

...
It provides quite a cleaner image. I would like to have a larger preview in AvsP to check on DeGrainMedian results instead of burning a test DVD.

Mplayerc(classic) or other player(s) should be able to play your avs script as a "preview".

...
DeGrainMedian(limitY=2,limitUV=3,mode=1)
lsfmod(smode=3, Smethod=3, kernel=19, soothe=true)
LanczosResize(664,480,0,2,0,-2)

I see you use degrainmedian mode1 (with limiters) but if you have strong grain you may want to explore more suited filters like Mdegrain2 (or 3). Even a fft3dfilter() well tuned may be able to give a less softer result.

If rebuked by the Mdegrain script, you may want to try the softsharpen() script. It's a all in one script that uses Mdegrain1 for denoisT=1 to 8, Mdegrain2 for denoisT=9 to 14 and Mdegrain3 for denoisT=15 to max.
The sharpening part of this script is different from LSF or LSFmod (only sharping on static parts of the source) but can be disabled with sharp=0; Other params can also be disabled (with =0) if wanted.

Did

[g-force]

Hey calmart,

can you post that last screenshot without LSFmod applied?

-G

[canuckerfan]

Now for the final touch on what I might do to improve the image.

Please look at the halo that borders the character's dark coat and on his chin.

Is there a way I can correct that? Making that halo more visible is what makes using LSFmod critical. But LSFmod compensates quite well the resizing, so it would be nice to use it.
if your halos are present in the source even before calling lsfmod than there's nothing lsfmod can do about that. you'll have to get rid of those with another script (like dehalo_alpha).

you can try using lsfmod with its preblur="dehalo_alpha()" (or your dehaloer of choise) in order to prevent any further halo sharpening. it works pretty well.

[carlmart]

Hey calmart,

can you post that last screenshot without LSFmod applied?


LDFMod was not applied on that screenshot. If I applied it the halo would be more apparent.

The idea was to show that, even before applying the filter, the halo was there.

[carlmart]

if your halos are present in the source even before calling lsfmod than there's nothing lsfmod can do about that. you'll have to get rid of those with another script (like dehalo_alpha).

Applying dehalo_alpha didn't prove too good the last time I tried it. It looked more like a fog filter working all over. Also running times were long.

you can try using lsfmod with its preblur="dehalo_alpha()" (or your dehaloer of choise) in order to prevent any further halo sharpening. it works pretty well.

That I can certainly try and see.

[carlmart]

I see you use degrainmedian mode1 (with limiters) but if you have strong grain you may want to explore more suited filters like Mdegrain2 (or 3). Even a fft3dfilter() well tuned may be able to give a less softer result.

If rebuked by the Mdegrain script, you may want to try the softsharpen() script. It's a all in one script that uses Mdegrain1 for denoisT=1 to 8, Mdegrain2 for denoisT=9 to 14 and Mdegrain3 for denoisT=15 to max.
The sharpening part of this script is different from LSF or LSFmod (only sharping on static parts of the source) but can be disabled with sharp=0; Other params can also be disabled (with =0) if wanted.


So many filters, so little time...

From my first tries, one element that is serving as my parameter is men's beard. The challenge is how to diminish the grain without affecting the look of shaved faces.

This is being fun.

[BigDid]

So many filters, so little time...
The challenge is how to diminish the grain without affecting the look of shaved faces.

This is being fun.
Hi,

A Old french movie and french actors, good challenge. Title being, I suppose, either:
- The bride wore black (1968) or
- Vagabond humor (1971)

I am willing to test but with a sample from the source not a pic; preferably including one or both of your pics.

Thanks.

Did

[carlmart]

I am willing to test but with a sample from the source not a pic; preferably including one or both of your pics.


The film is ""The bride wore black". I am a big Truffaut fan.

Of course you can't try anything on a picture. I can upload some sample on the web. Will do that today. Thanks.

[carlmart]

The file is here:

http://www.mediafire.com/file/r2rnvnnn2y1/bride1.m2v

[BigDid]

The file is here:

http://www.mediafire.com/file/r2rnvnnn2y1/bride1.m2v
Hi,

Thanks, I will have a look later today.

Did

Edit: it will need quite some work cause I see:
- blocking
- grain
- dirt
- halos
- some banding after sharpen ...;)

[BigDid]

Hi,

2 methods for denoising/sharpening:
-1st is Mdegrain3 + your LSF script (quicker but less details)
-2nd is MCtemporaldenoise (from LATO) with included sharpening (slower, more details)
Softsharpen is not used because Mdegrain2 would have been used instead of Mdegrain3, so less quality. I will see with Leon if the thresholds can be changed. Would have replaced MCTD in script2:
softsharpen(preset="film", sharp=15,denoisT=10,denois=0, blur=0,derin=0)

Will give scripts without multithreading but available on request.
Each script has same beginning with deblocking and ending with deringing and dehaloing

-1/ Mdegrain3 + LSF script
#Preprocess
DeGrainMedian(mode=5)
LanczosResize(720,432)
BlindPP(cpu2="xxxxoo", quant=31) #deblocking, part of dgdecode

#Denoise
super = MSuper(pel=2, sharp=2)
bv1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
fv1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
bv2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
fv2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
bv3 = MAnalyse(super, isb = true, delta = 3, overlap=4)
fv3 = MAnalyse(super, isb = false, delta = 3, overlap=4)
MDegrain3(super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=300) #Mdegrain3, strength=300

#Sharpen and postprocess
lsfmod(smode=3, Smethod=3, kernel=19, soothe=true)
BlindPP(cpu2="ooooxx", quant=4) #deringing, also from dgdecode
blinddehalo3(ppmode=-3) # didée script for dehalo
Pic for 1/
http://www.mediafire.com/file/4rv0nwojmmd/Bride1_Mdegrain3_300_Lsf_19_fr987.png

2/ McTemporaldenoise; I am sure it can be better tuned - I am not accustomed to new version:

#Preprocess
DeGrainMedian(mode=5)
LanczosResize(720,432)
BlindPP(cpu2="xxxxoo", quant=31) #deblocking, part of dgdecode

#Denoise and adaptative sharpen - sigma= str of denoising; strength=str of sharpening
MCTemporalDenoise(settings="medium",sigma=20,adapt=true,strength=8,protect=true,flat=true)

#postprocess
BlindPP(cpu2="ooooxx", quant=4) #deringing, also from dgdecode
blinddehalo3(ppmode=-3) # didée script for dehalo
Pic for 2/
http://www.mediafire.com/file/qwizttyhoyj/Bride1_MCTD_med20_Sharp_8_fr987.png

All these scripts and filters should be available here at doom9.

Did

Edit: for MCTD, the sharp is too low and so maybe the denoising;

3/ MCTD new values approaching script1:
MCTemporalDenoise(settings="medium",sigma=40,sharp=true,strength=60,protect=true,flat=true)
Pic for 3/
http://www.mediafire.com/file/kc4zzetdajo/Bride1_MCTD_med40_Sharp_60_fr987.png

[LaTo]

MCTemporalDenoise(settings="medium",sigma=20,adapt=true,strength=8,protect=true,flat=true)

strength=8? strength works the same as LSF/LSFmod: default=100

and adapt=true is default for all settings

;)

[leon1789]

Softsharpen is not used because Mdegrain2 would have been used instead of Mdegrain3, so less quality. I will see with Leon if the thresholds can be changed
Hello. :)
With SoftSharpen 7.2, let's try this script

# Preprocess + Denoise + adaptative sharpen + beginning of postprocess
SoftSharpen(denois=6,width=720,height=432,debl=31,DenoisT=6.3,sharp=15,blur=0,derin=4)

# end of postprocess
blinddehalo3(ppmode=-3)

denois=6 <--> RemoveGrain(mode=27)
denoisT=6.3 <--> Mdegrain3(300)

[carlmart]

BTW, you experts certainly know more about this than I do. But I started with these before going for LSF and Degrain, and it cleaned things quite a bit:



TFM()
TDecimate(Mode=1)

[LaTo]

Edit: for MCTD, the sharp is too low and so maybe the denoising;

3/ MCTD new values approaching script1:
MCTemporalDenoise(settings="medium",sigma=40,sharp=true,strength=60,protect=true,flat=true)

Pic for 3/
http://www.mediafire.com/file/kc4zzetdajo/Bride1_MCTD_med40_Sharp_60_fr987.png

:eek:

Why not sigma=500?
Useful range is 2-20... 40 is really too high for this type of source!

[carlmart]

BigDid,


So that this does not become a tennis game where I don't know what are the rules, can you start by telling me what you diagnose as the problems you see?

Then perhaps I can start to understand what you look for on the available tools.

From what I could try on my AvsP, using your suggestions 1, 2 and 3, the only one I could not get to run was MCTemporalDenoise. It asks me for things I already have, but when I show the path it gets stuck.

[LaTo]

... the only one I could not get to run was MCTemporalDenoise. It asks me for things I already have, but when I show the path it gets stuck.

Screenshot or exact error message..?

[carlmart]

This is the error I am getting.

[BigDid]

BigDid,
...
From what I could try on my AvsP, using your suggestions 1, 2 and 3, the only one I could not get to run was MCTemporalDenoise. It asks me for things I already have, but when I show the path it gets stuck.
Hi,

MCTD is quite picky about needed dll revs. To get the MCTD (1.3.00) working, I have:
LSFmod (1.8)
MVtools2 (2.4.7)
Mt-Masktools (2.0.36)
Gradfun2dbmod (1.3)
... other filters as in the needed filters read me from here:
http://forum.doom9.org/showthread.php?t=139766

Once you get it working, it will be up to you to tune the MCTD preset. If I follow LATO advice and not crank up sigma, it should tend towards something like:
MCTemporalDenoise(settings="high",sigma=20,sharp=true,strength=50,protect=true,flat=true)
but, as I was wrong until now, follow his advices, not mine for his script.

Did

Edit:
BTW, you experts certainly know more about this than I do. But I started with these before going for LSF and Degrain, and it cleaned things quite a bit:

TFM()
TDecimate(Mode=1)

Certainly not an expert on the subject but, your source being NTSC pure film (from DGIndex info), could be processed by Tdecimate() or tfm+tdecimate(); see:
http://avisynth.org.ru/docs/english/externalfilters/tivtc.htm

[BigDid]

Hi,

After exchanging with Leon, he made some internal changes to get SoftSharpen (SS) process the temporal denoising more like Mdegrain (specially MD3). Softsharpen rev 7.3 is needed and preset=light is to be used. The resulting script:
#Preprocess
DeGrainMedian(mode=5)
LanczosResize(720,432)
BlindPP(cpu2="xxxxoo", quant=31) #deblocking, part of dgdecode

#Denoise and adaptative sharpen , temporal-denoise str=6 (=thsad-300) Mdegrain3 used, light spatial denoise str=2
SoftSharpen(preset="light",denois=2,DenoisT=6.3,sharp=15,blur=0,derin=0)

#postprocess
BlindPP(cpu2="ooooxx", quant=4) #deringing, also from dgdecode
blinddehalo3(ppmode=-3) # didée script for dehalo

Pic, snapshot for frame 985, same as the others:
http://www.mediafire.com/file/demmmzxkvnl/Bride1_cut_SS15_6.3_2_fr985.png

SS has internal params for deblocking, denoising (both temporal and spatial), deringing and debanding.
Some of these options were used outside SS for paralleling the script with other filters (Mdegrain3, LSF, and MCTD) and also not all options, like deblocking, are full-MT capable.

After quite some time involved for these tests, my conclusion is that for good processing Softsharpen does the job and quite quickly.
If more sharp is needed, use SS with sharp=0 and use LSF after (slower).
If very good processing is needed switch to MCTD and fine tune the many options to your needs (slow to very slow).

Did