I love Kassandros Filter Stuff, but its quite uncomfortable to get an overview of his filters as all do have a separate domain.

Boulder, do you know a link-collection of "his" domains? Or do you even know all his filters/domains? As I wasn't that active the past months in the avisynth dev area

Uh, I'm often confused as well

I'd say look for removedirt, removegrain, avstimer, avsrecursion and ssetools (under construction) - add the word in www.xxx.de.tf.

As his documenting style is very verbose, I guess he decided to make separate domains for each one. One single page with all the links would have been really great, maybe I should ask him to do that.

Nowadays I use Didée's LTSMC for my analog captures so I haven't had to keep up with all the different plugins, IIRC that one uses RemoveGrain and SSETools from kassandro's plugins. kassandro's forum is a good place for information, and he's also very positive towards any new ideas - as you can see from RemoveGrain, which contains ~30 modes already

Really ?

@ Boulder

Ahhhh ...

www.RemoveGrain.de.tf

www.RemoveDirt.de.tf

www.ReduceFlicker.de.tf

www.AvsTimer.de.tf

www.AvsRecursion.de.tf

www.mdeblock.de.tf

www.SseTools.de.tf (preparation stage)

Btw when searching for LTSMC() I saw this nice "Bazzzzzong" Site:
http://www.avisynth.info/?%B4%D8%CF%...E5%A1%BC%A5%B9

Also interesting for avs 2.56 betas users which still want to use Mpeg2Dec3.dll on DVD2Avi generated d2v projects:
http://videoprocessing.11.forumer.com/viewtopic.php?t=2

The latest release has 25, and I think kassandro's got some new ones for the official v1.0 Of course, not all of them are really useful.

whow, great (and slow) function.

I tweaked around a bit and with:

I got a picture quality which to my eyes looks better (more detail) and has a smaller filesize than with a lanczosresize.

I'm really impressed with it's capabilities!

I see u use a 2x Supersampling on Width & Height (ss_x, ss_y), a supersampling does slow down the process significantly as the picture like explained above will be temporal upsized by the given value. If doing a large supersampling I found out that you can go higher in the "strength" without getting artifacts. Also sometimes its only needed to supersample only one way (x or y) .... thats on every source individual.

The dest_x,dest_y is also very useful by adding the resize parameters from Fitcd if LS() is at the beginning of your script (I for my taste prefer putting that fuction more towards to the script's end as Im used to put the sharpener as one of the last steps.

That LS() in combination with the (fast!) LRemovedust(4,1) function on good DVD sources gives me a hughe enhancement.

I dont care that much about the Speed of LS() in this workout purpose as it will be compensate by the time the OPV encodings do need compared to 2pass. But that always was the rule of tumb: Complexer functions do need more time, but often it's worth the time consumption ... well depends on the function .

Remember VagueDenoiser ? Everyone droped it because if its speeds.

For the LS I hope that will be acceptable on my 1.6Ghz () else I will have to wait before to play with it

I do clearly remember VagueDenoiser and the hype on it. I NEVER was that addicted on it when it came out as I experimented a lot with it and the quality wasn't worth the speed drop. (just imho). See the "how funny" thread in here

But I do also remember Pixiedust() which is still used by many experienced persons as it supports motionvector based denoising.

Now back to LS().

There are two parameters which do cause each by its own a hughe speed decrease.

If Supersampling values are bigger than 1 (ss_x, ss_y) which causes temporal total upsizing by *x ...
and if Edgemode is bigger than 0, cause this forces LS() to use a very complex mask and a maskedmerge finally. Even its a double sobel matrix based one, it often keeps some details out. So IF u go into a movie using LS() which is a very clean DVDsource like my StarWars example above I personally do switch that mask off using Edgemode = 0. BUT you should use a good detailkeeping denoiser before so that a unwanted rest of significant irritations or significant uneasy pixels won't be sharpenend too.
If using Edgemode = 0 and the frames do result in more "detailed" noise, then switch the edgemode on using 1.

I tried to find a compromise between details less noise and speed

This is just a first approach NOTHING defenitely for me as it could result even better:

its quite fast, do set the sharpening level using the "strength" value

A hint: DON'T apply LS() on typo parts like beginning or end credits. It does a nice "subjective" job on natural scenes but on typographics it behaves subectively too strong imho. An ApplyRange() Routine should keep these unwanted scenes not to be treaten by LS().

Yep .. diff Sources are diff. to handle.
For making Titanic 4:3 to 16:9 I used this one finally and its fast:
(Both upsized vertically to 16:9 before)


I have to use converttoYUY2().converttoYV12().LRemovedust(4,2) including that "nonsense" Colorspace conversion as it seems my version of Removegrain does have a chroma memory align bug. If I dont use these, The LRemoveDust() Function drops significantly in its speed.

What the hell is that line ?

Edit: you explained it after, sorry.

Note: what really surprise me is how bad is your source. I should take a snapshot from the KDVD I did from mine just to compare. Yours is so blur that I wonder how I never noticed that. Remember me the time where is this scene and I'll try to pick the same frame.

As told that is a 9,95 Euro trash DVD Edition, means heavy quantisation as much trailers of other moviepreviews are included and took space from the main movie and it has been produced as letterboxed 4:3 !
That's why I decided to take that worst orig DVD case as source

Keep in mind that the blur got even more as I sized it up vertically to restore back the wanted anamorph state.

I did also (the only time I ever use the "4:3 -> 16:9" feature of DVDRebuilder). This movie has never been edited in anamorphic. But my DVD has only the movie, and not a single bonus nor other "precious bits" eater .

Did you try align=true in Crop()?

Yep, that was the first I tried. But no way. I do have an Athlon XP and Im not shure if Im using the latest release of Removegrain and its dlls.

I've got this one : http://home.arcor.de/kassandro/Remov...emoveGrain.rar (RemoveGrain v1.0 prerelease) and the last SSETools from the official RemoveGrain v0.9 package. Confusing, huh

I'm using the latest Avisynth beta package from SourceForge with the fixed avisynth.dll, which can be found here.

Some earlier Avisynth beta caused a huge degrade in LRemoveDust's performance on my system, due to the changes in the alignment I think.

thanks! Ill have a look at it, even I think its the one Im also working with.

Thanks#2!
Thats a really good hint as the degraded performance of LRemoveDust() is exactly my issue when not doing the YUY2.YV12 forth'n back conversion.

I also recognised if you got a nice very detailed but noisy DVDsource, even LRemovedust(4,1) does attack some fine details, thats why a combo of that function and LS() is a good way to go for me.
I wanted to try out the latest LTSMC() Function from Didée, but had no time. Im waiting for how "fast" it will perform as IIRC MVtools() are used

Anyway, Didée is very innovative with his script developings.

LTSMC (like LimitedSharpen) is pretty slow with non-multithreading processors. I got quite a nice speedup with both of them with the MT plugin on my P4. Needless to say, the cleaning capabilities are superior.

Have you tried LRemoveDust(17,1)? It should be a bit more conservative when it comes to thin lines.

In which plugin is the LRemoveDust ?

I can't find it in the RemoveGrain doc. Is is in RemoveDust ?

As far as I know it's a function from Didee:

Kassandro had made an SSE optimized version, but I don't have it at hand right now.

btw you need to load removegrain and repair for this, both founded in the removegrain package.