Simple Picture Improving script

[o2xygen]

I did a search on the forums for denoise but there are A LOT of denoisers ...

Many comparatives are out dated though.. Many support that FFT3DFilter is the best for denoising, but I couldn't find a simple script for this, and I know nothing of script writing...
What I want is a simple script that will make your DV (pal movies not anime) footage better looking... Removing some noise, and making your picture crisper...
There should be a sticky topic with sample scripts IMO...
thanks

[scharfis_brain]

for time-independent people:

mvbob().ltsmc().iip()

but that will probably kill every machine out there :)
far too much CPU and memory needs...

[Didée]

mvbob().ltsmc().iip()
w00t! That's 1fph (frame per hour), or so ... :D

[MOmonster]

I thought, he asked for a simple picture improving script. :confused:
Maybe the results of the scripts are amazing (I never has used these functions), but of course, also if I have much, much time, I still wouldn´t use it, that way.
For sharpening have a look at limitedsharpen or try the alternative for ssxsharpen (warpsharp + asharp). For the denoising of DV-sources try undot + deen or peachsmoother with light settings. Removedirt or the function removedust is also worth to have a look at. The results of the FFT3D filter are also really nice. Have a look at the thread, there are some examples how to use this filter right. Play a little bit with the settings and use the sharpening after the denoising. :D

[mg262]

Also the functions in the dust filter by steady, which remain my preferred denoisers for most purposes (although I haven't tried fft3d yet).

[Backwoods]

@o2xygen

FFT3DFilter(OH=16,OW=16,BH=48,BW=48,BT=3,Sigma=1,Sharpen=1)

Give that line a shot and if you want more noise removed, increase the sigma.

@Didée
Which version of MVTools does LTSMC use?

[sasam]

There should be a sticky about this.
Have a look at this big script from paviko, it is really great: http://forum.doom9.org/showthread.php?p=622247#post622247

[mg262]

There should be a sticky topic with sample scripts IMO...There should be a sticky about this.Then make one! Or at least, stickies can arise out of normal threads if the mods feel that they are useful (and objective in light of rule 12, etc.) enough... so you are free to start collating the data to try and build such a thing, and perhaps one day it will turn into such a thing or be the basis for it :).

[o2xygen]

this will seem the most amateurish thing you have ever been asked...

This is what I understood so far. You specify the clip, then the plugin and in the end the options.. I thought that this will be it, but when I run the script, it says

Invalid arguments to function FFT3DFilter

clip = AVISource("C:\avisynth\badnoise.avi")

LoadPlugin("C:\avisynth\fft3d\fft3dfilter.dll")



FFT3DFilter(OH=16,OW=16,BH=48,BW=48,BT=3,Sigma=1,Sharpen=1)

return clip


thanks

[o2xygen]

omigod. I managed to make the paviko's script work.. :)
Do I hear any bells ringing?

[mg262]

I'm not sure whether you still want this... but anyway:

most filters implicitly take a video clip output from the previous filter as an argument, like this:

LoadPlugin("C:\avisynth\fft3d\fft3dfilter.dll")

AVISource("C:\avisynth\badnoise.avi")
FFT3DFilter(OH=16,OW=16,BH=48,BW=48,BT=3,Sigma=1,Sharpen=1)

but if you put the output into a variable, it doesn't get used as an implicit argument, so you must write this:

LoadPlugin("C:\avisynth\fft3d\fft3dfilter.dll")

clip = AVISource("C:\avisynth\badnoise.avi")
FFT3DFilter(clip, OH=16,OW=16,BH=48,BW=48,BT=3,Sigma=1,Sharpen=1)

or this, which is equivalent

LoadPlugin("C:\avisynth\fft3d\fft3dfilter.dll")

clip = AVISource("C:\avisynth\badnoise.avi")
clip.FFT3DFilter(OH=16,OW=16,BH=48,BW=48,BT=3,Sigma=1,Sharpen=1)

[o2xygen]

Thanks... I started to realize how it works.. IS not so difficult after all. Thanks again :)

[o2xygen]

I tried some tests on a video I found in the forums
Source
http://briefcase.pathfinder.gr/download/christos_00/16695/467426/0/source.jpg

Paviko's Method
http://briefcase.pathfinder.gr/download/christos_00/16695/467427/0/dtestPaviko.jpg

Peachsmoother (not by me)
http://briefcase.pathfinder.gr/download/christos_00/16695/467428/0/dpeach.jpg

FFDShow PostP and Xsharpen
http://briefcase.pathfinder.gr/download/christos_00/16695/467429/0/dffdshowNONRXSHA.jpg

I found that peachsmoother is the best.. It softens without losing much detail...
Paviko's method seemed to do much sharpening...
FFdshow was the fastest but the picture is not sharp...

I have to find a script for Convolution3d and peachsmoother...

[Didée]

@ o2xygen:

Oh. You tried your luck on a particular poor analog captured source.*) That's not necessarily what you should compare the methods on ... you mentioned DV footage, which would have completely other "characteristics", so the various filtering methods would lead to quite "different" result ...
*) "analog capture, poor input" -- not "poorly captured"


@ Backwoods: MVTools v0.9.9.1, PM for an updated W.I.P function

[o2xygen]

OK so I will try it on DV footage and see...

[phædrus]

I've been using AVS scripts for about a year now, but most of the time I haven't wanted or needed very much complication. Load the plugins, load the clip, crop, IVTC with telecide and decimate if necessary, undot(), resize.

This is a little OT, but not totally...
Recently I was working with a clip of The Third Man which was very grainy, so I tried deen() in addition to undot because one of the stickies at the top suggested that it was a pretty fast filter and improved compressability a fair amount. I thought it worked very well, just a little too powerful at the default. I like to see a little more grain even if I have to increase the bitrate to handle it, because I don't want too much smoothing. Overall, I liked the effect though. Still, I have been searching through this AVS forum for about an hour trying to find some varying settings for deen that I might apply instead of the default deen(), with not a lot of luck. Maybe I am poor at searching. I found one setting "deen("a3d",2,3,0,7,0)" which from the context sounded like it might be closer to what I want, but I'll just have to blindly try it and see.

Now back on the topic of the first post, this forum is very hard for the beginner to read. It's like a beginners AVS forum might be helpful, with more sticky guides with suggestions for different filtering situations and needs. I'll never understand all the technical ins and outs discussed here, but I admire the people who are experimenting at this level. Unfortunately I can't make sense of a lot of it, hence I can't begin to use it effectively. I guess I want to chime in with o2xygen and wish for someone to help us kindergarten AVS users advance to at least the first or second grade. :-)

I've been playing with DVDShrink, but now I'm about to advance to DVD-RB, so I'd like to advance my AVS skill, at least a little bit.

[Wilbert]

Now back on the topic of the first post, this forum is very hard for the beginner to read. It's like a beginners AVS forum might be helpful, with more sticky guides with suggestions for different filtering situations and needs.
That's very difficult, because it very much depends on your source. Also a lot of new filters pop up regularly. Btw, did you read the AviSynth section of the analog capture guide? This might be very useful for you to get you going.

[mg262]

Incidentally, o2xygen, something just struck me about your first post:

>Many comparatives are out dated though.. Many support that FFT3DFilter is the best for denoising, but I

Rereading that I remembered that FFT3DFilter wasn't actually out the last time I tried a denoiser comparison.* I just checked and it's only nine months old... so anything you have read that cites it shouldn't be that out of date. I don't suppose you can remember which threads you're talking about? I'm not sure I've seen them and I would like to...

*That's another story, but... no actually, it is relevant; but I will finish the paragraph first!

Denoiser comparison: well, at the time, I was totally new to doom9 (I really mean that -- my post count was something like 3) and I wanted to know which denoiser to use for the content I had. But I was a bit too scared to post. So I spent quite a while trawling through the forums for filters and (more or less generic) scripts, pasting them all into notepad as I went along, and eventually I downloaded all the filters and just tried them all head-to-head. It all took absolutely ages, but I it was a good way to get past that first stage of not really being sure what to do next.

I wouldn't advocate that everyone try and do this... but I found the best first step was to try and understand something, some small area, fairly well; doesn't matter how small. Then you can read posts dealing with that area and because you understand 90% of the post to begin with you can often make sense of the remaining 10%... so your knowledge slowly ripples outwards. Not sure how helpful any of this is!

Incidentally, phædrus, do you think that people have trouble understanding the syntax of AVISynth or is it just choosing filters that is hard?

[phædrus]

mg262, I personally don't have trouble with the syntax of AVS. I started out using a script generated by Gordian Knot as a guide, and making little modifications here and there, to start to get the hang of it. My standard scripts for 4:3 and 16:9 source material are derived from those GK scripts, though I've changed some of the plugins, and I can manipulate things like cropping and resize very easily. What I find confusing is the filtering plugins -- understanding what each one is supposed to do, vaguely understanding how it accomplishes its job (and what side effects it might produce as a result), but worst of all is the specific settings for each filter when you depart from defaults. Those are usually as confusing as all get out.

Decomb -- I use that quite a lot, and I've read through dg's guide for that several times, and I still have great difficulty grasping some of the thresholds, and what kind of results I might expect if I changed some of them. And most filters do not give you instructions nearly as thorough and clear as Donald does with his plugins. I wish each author of other filters would give you some sample parameters to set for a "light" effect, normal effect, or "heavy" effect. Or perhaps design the filter so that you could just "dial in" the overall strength of it on a 1 to 10 scale, without needing to adjust each parameter individually. I realize it isn't always as simple as this, and it certainly is the author's perogative to make it as difficult as possible, if he wants to. :-)

Wilbert, although I have not done capturing, I have read some of the guide. I don't remember if I looked at the AVS part of the guide or not, but that's a good suggestion. Thank you. I'll take a look.