SpotLess - Temporal denoise

[FranceBB]

I know, I wasn't complaining, I was just pointing out that I had the very same issues you had on some scenes, that's all.
Anyway, I'll provide the script if it helps others.

[johnmeyer]

Originally Posted by FranceBB

I know, I wasn't complaining, I was just pointing out that I had the very same issues you had on some scenes, that's all.
Anyway, I'll provide the script if it helps others.

Got it. Thanks!

[StainlessS]

Just noticed, mistake in docs [fixed]

    Tm,      TrueMotion Default True. Some folk swear truemotion=false is better.    # Was False

[johnmeyer]

I was able to eliminate a lot of the rainbows in the clip provided in a thread over at Videohelp. This post shows the SpotlessS script I used, along with one "before/after" snapshot:

https://forum.videohelp.com/threads/...=1#post2595644

[kedautinh12]

Originally Posted by johnmeyer

I was able to eliminate a lot of the rainbows in the clip provided in a thread over at Videohelp. This post shows the SpotlessS script I used, along with one "before/after" snapshot:

https://forum.videohelp.com/threads/...=1#post2595644

Can you try ASTDR derainbow??
https://github.com/realfinder/AVS-St...0up/ASTDR.avsi

[johnmeyer]

Originally Posted by kedautinh12

Can you try ASTDR derainbow??
https://github.com/realfinder/AVS-St...0up/ASTDR.avsi

I'll try to remember to do that when I get back to my office computer tomorrow. I really only wanted to kill the rainbows, but not do any denoising, and SpotlessS uses a function which desnoises as well as averages. I'll let you know if it works.

[StainlessS]

John, you posted on VideoHelp, non current script,

   RadT     = Default(RadT,2)                              # Temporal radius. (MCompensate arg)
    ThSAD    = Default(ThSAD,10000)   # SAD threshold at radius 1 (Default Nearly OFF).
    ThSAD2   = Default(ThSAD2,10000)                        # Setting lower, sets SAD thresold to limit blurring effect of more distant reference frame BAD matching blocks. (MCompensate arg)

should be (and for good reason)

   RadT     = Default(RadT,1)                              # Temporal radius. (MCompensate arg)
    ThSAD    = Default(ThSAD,10000)   # SAD threshold at radius 1 (Default Nearly OFF).
    ThSAD2   = Default(ThSAD2,ThSAD)                        # Setting lower, sets SAD thresold to limit blurring effect of more distant reference frame BAD matching blocks. (MCompensate arg)

Changing ThSAD also changes default ThSAD2.

We dont really want gazllions of versions of the function floating about, there are already more than enough official ones.

[johnmeyer]

Originally Posted by StainlessS

John, you posted on VideoHelp, non current script, <snip>

We dont really want gazllions of versions of the function floating about, there are already more than enough official ones.

Sorry about that. I don't think it will make any difference, since I fed my own numbers into the script so the new presets in your current version will be overridden.

[StainlessS]

Update SpotLess(), v1.06, see 1st post.

    v1.01, Remove RadT Max check. Add MSuper(hpad=16,vpad=16). Add BlkSz arg.
    v1.02, Add some stuff.
    v1.03, Frame size auto config of args removed (found instances where caused problems). Added Glob and bBlur args.
    v1.04, Script breaking changes, I guess is more flexible if can also set ThSAD, inserted ThSAD 3rd arg. RadT now default 1, was 2, dont over denoise unless requested.
    v1.05, Additional checks on args.
    v1.06, Glob Default true, Almost always better.

[StainlessS]

Dont know if this is of any use at all (I usually like to get rid of interlacing).

Function SpotLessI(clip c,String "Bobber",int "RadT",int "ThSAD",int "ThSAD2",int "pel",bool "chroma", int "BlkSz",Int "Olap",bool "tm",Bool "glob",Float "bBlur") {
/*
    SpotLess use on Interlaced material.
    Input requires correct parity, use AssumeTFF/AssumeBFF before use.
    RadT etc applied to Bobbed fields rather than frames, Might want to use at least RadT=2 (default is 1).
*/
    c
    Bobber = Default(Bobber,"Bob")      # Your Favourite Bob deinterlacer whotsit
    Last.Eval(Bobber)
    SpotLess(RadT,ThSAD,ThSAD2,pel,chroma,BlkSz,Olap,tm,glob,bBlur)
    SeparateFields.SelectEvery(4,0,3).Weave
    Return Last
}

Have I done it correctly, any comments and testing welcome.
If is of value, I'll add to main script, otherwise if no response I'll give it a miss.

EDIT: Or any suggestions on single/doublerate use (maybe skip last step SeparateFields.weave).
EDIT: Or could use above as a template.
EDIT: Possibly of best use where original clip was progressive with noise before artificial conversion to Interlaced.

EDIT: Alternative.

Function SpotLess2i2(clip c,int "RadT",int "ThSAD",int "ThSAD2",int "pel",bool "chroma", int "BlkSz",Int "Olap",bool "tm",Bool "glob",Float "bBlur") {
/*
    SpotLess use on Interlaced material, fields filtered separately.
    Input requires correct parity, use AssumeTFF/AssumeBFF before use.
*/
    c
    e=Separatefields.SelectEven.AssumeFrameBased.SpotLess(RadT,ThSAD,ThSAD2,pel,chroma,BlkSz,Olap,tm,glob,bBlur)
    o=Separatefields.SelectOdd.AssumeFrameBased.SpotLess(RadT,ThSAD,ThSAD2,pel,chroma,BlkSz,Olap,tm,glob,bBlur)
    Return interleave(e.AssumeFieldBased,o.AssumeFieldBased).Weave
}

[FranceBB]

That is actually correct.
You're bobbing, filtering, dividing in fields, so that's alright.
By the way, I would encourage users to do it themselves rather than relying on it 'cause it's definitely gonna work for truly interlaced sources which will be bobbed to 59.940p or 50p, however, on telecined sources it will make the temporal prediction of MVTools useless, besides, even with truly interlaced sources, with Bob, fields would jump "up-down-up-down" making it harder to analyze and filter, so it's always better to let users handle it (hoping they'll use something decent as a deinterlacer and that they're aware of their source).
As to the alternative, again, you're right, as you're filtering each field separately and then putting them back together.
The second approach is probably the safest and I prefer it more than bobbing and re-interlacing.


Well done, Stainly, you're really following the government advice:

[StainlessS]

Cheers FaB, tanks for feedback.
I'll not bother adding to base script then.

EDIT: By the way, Bobber default of "Bob" is only because its a builtin filter, I would not recommend it.

[Emulgator]

FranceBB, now that poster is brilliant !

[piscator]

NOT FOR cartoon/anime, live video only, sorry.

What limitations are there that it should not work so great for cartoons? I have some DVDs with old children cartoons from 1956+ (Mole TV series, children cartoon) which I am trying to clean up. I have been looking for a bit to clean the spots and scratches (black and white, some quite large) from it and SpotLess works great on it Thanks, StainLessS!

[StainlessS]

Thanks for the feedback piscator,
MvTools motion compensation type stuff dont usually work to well on anime.
Did you use any non default args ? [maybe large block size, which I thought might help].

[piscator]

I just used default arguments.
Perhaps it works so well because this cartoon is quite 'static'. The background is usually completely fixed with sometimes a bit of panning /zooming on it. So, it is all really quite slow / limited motion.

[StainlessS]

static background might help,
anyways glad you are happy.

[FranceBB]

That's because cartoons / anime are generally not with the real framerate.
I mean, if you go through an anime encoded at 23.976fps, you'll almost definitely find repeated frames, but it's not a mistake, they're there by purpose as whoever animated it (I mean the studio) wasn't really able to deliver so many frames per seconds in terms of each individual character moving a part of the body etc. These repeated frames don't generally work well with MVTools, hence the assumption that it might not work for anime.
In your case it worked absolutely fine, so don't get me wrong, you might be lucky and have it working perfectly fine, but generally speaking, MVTools doesn't like non-live contents.

Originally Posted by Emulgator

FranceBB, now that poster is brilliant !

Ehehehe thanks

[piscator]

I mean, if you go through an anime encoded at 23.976fps, you'll almost definitely find repeated frames

Thanks, I can understand why that would make it more difficult. My source was just 25fps interlaced. And the motion is so slow, that when dropping half of the frames, you barely see a difference

I encoded this source for fun on crf 30 (x265, Ultralow) and it looks the same as on higher bitrates. But degraining, descratching and removing the spots make it much better.

[Frank62]

An idea:
Maybe possible to
-drop the dups, log it, maybe in StainlessS' database thing
-removedirt/spotless
-take the logged dups in another clip
-removedirt these
-bring everything together again
Could be a cleaning-chance for old anime