Avisynth: Removegrain + Removedirt - Page 2

Dialhot · #21 09-15-2004, 12:27 PM

Quote:

Originally Posted by J-Wo

Any Mpeg2source("",cpu=x) or BlindPP post processing is also much too strong

As I mentioned in my first post, I was wondering about the fact that this PP can be "too much" in this script. As I did all my tests on only one source, the answer was "no, it is not too much". But for sure, as you told, the source does matter.

For the mode=8, I revised my opinion : in the tests I did for avi sources, mode=8 was too bad also. I returned back to default (mode=2).

Quote:

BicubicResize(688, 448, 1/3, 1/3, 0, 8, 720, 464)

I'm just telling my opinion here : I find bicubic standard too soft for my eyes. That is why I always use Lanczos.

J-Wo · #22 09-15-2004, 12:45 PM

Quote:

Originally Posted by Dialhot

For the mode=8, I revised my opinion : in the tests I did for avi sources, mode=8 was too bad also. I returned back to default (mode=2).

Then we are in agreement!

I think the default is just fine, as the docs say mode=2 is simply a "smarter" undot, and that's true. It compresses a bit more but is also a lot faster than undot.

I think for DVD sources you want to preserve as much detail as possible. So mode=2 is best for me. But maybe for some other material (tv caps?) mode=8 will be just fine. I suppose one will just have to test and see for one's self.

Quote:

Originally Posted by Dialhot

I'm just telling my opinion here : I find bicubic standard too soft for my eyes. That is why I always use Lanczos.

heheh, ya I do know you've mentioned that several times.

But to my eyes, I really can't see a difference between bicubic standard/precise vs. lanczos. And this is on a 53" HDTV. Unless more people tell me I'm dead wrong, I'll stick with bicubic standard for now for the higher compression.

J-Wo · #23 09-16-2004, 01:00 PM

Quote:

Originally Posted by Dialhot

Code:

AviSource("PATH\NAME.avi",false)
BlindPP(cpu=4)
GripCrop(WIDTH, HEIGHT, overscan=1, source_anamorphic=false)
GripSize(resizer="LanczosResize")
Blockbuster(method="noise",detail_min=1,detail_max=3,variance=0.1,seed=1)
DRemoveGrain()
Deen()
GripBorders()

Hey Dialhot, just wondering if you've made any progress in your new avi script. Any particular reason you're using a RemoveGrain + Deen combo instead of REmoveGrain + RemoveDirt? I'm going to try the latter as it should make the encode run faster (might not compress as well though)

edit: okay I did a little minitest on a 2000 frame clip using the above script. It's a Deen vs RemoveDirt test.

Test 1:
RemoveGrain() + Deen()
size = 21,036 kb
speed = 1.74

Test 2:
RemoveGrain + RemoveDirt()
size = 21,693 kb
speed = 1.96

So in my eyes, RemoveDirt compresses less than Deen only by 3%, but is 12% faster. Results look the same on my computer but I'll burn and test on my standalone (it always shows faults more readily).

incredible · #24 09-16-2004, 03:36 PM

Well J-WO the problem "when altering just not too much the noise" in your script is that you do a double spatial filter job, thats why your compression gain rises

Removedirt is a spatial denoiser only.
Deen() at default is a spatio-temporal, means 3d denoiser!

So two times spatial smoothed means more details killed - but your eyes will tell you the truth as this now is theoretical.
Removegrain was primary build to give removedirt() a hand on its job.

Removedirt does its fantastic (at right settings individual to the source) job as it seems that its working a bit motioncompensated (but Im not shure).

To get rid out of theese temporal filter artifacts you should look out for depan.dll as its a motioncompensation filter which avoids such temporal artifacts in combination with a temporal denoiser.

Code:

avisource("progressivePALfilm.avi")
#converttoyv12()
data=depanestimate(last,pixaspect=1.094,zoommax=20  ,improve=true)
depaninterleave(last,data,pixaspect=1.094)
YOUR TEMPORAL SMOOTHER HERE()
selectevery(3,1)

Code:

avisource("progressiveNTSCfilm.avi")
#converttoyv12()
data=depanestimate(last,pixaspect=0.911,zoommax=20  ,improve=true)
depaninterleave(last,data,pixaspect=0.911)
YOUR TEMPORAL SMOOTHER HERE()
selectevery(3,1) # not shure if NTSC needs here other values

Dialhot · #25 09-17-2004, 03:43 AM

Quote:

Originally Posted by J-Wo

Results look the same on my computer but I'll burn and test on my standalone (it always shows faults more readily).

And then you will probably understand why I choosed RemoveGrain+Deen and not Removedirt

(even if for DVD sources, it's the opposite).

Quote:

Originally Posted by incredible

Removedirt is a spatial denoiser only.
Deen() at default is a spatio-temporal, means 3d denoiser!

That is exactly that.
My original script add a "temporalsoften" after the Undot+Deen lines. I removed this, and that is probably why RemoveDirt is not enought and Deen is better.

Note: I didn't test RemoveGrain+RemoveDirt+TemporalSoften.

Uruk-hai · #26 09-17-2004, 04:00 AM

Quote:

Originally Posted by incredible

Removedirt is a spatial denoiser only.

Are you sure? It was said in the very first line of the help file Removedirt.htm that RemoveDirt is temporal:

Quote:

RemoveDirt is a so called temporal cleaner for Avisynth 2.5x.

Dialhot · #27 09-17-2004, 04:10 AM

Quote:

Originally Posted by Uruk-hai

Are you sure? It was said in the very first line of the help file Removedirt.htm that RemoveDirt is temporal:

Quote:

RemoveDirt is a so called temporal cleaner for Avisynth 2.5x.

It seems I'm as tired as Inc is

. Of course RemoveDirt is purely temporal. (but deen is still more efficient as it is spatio/temporal). So forget my line about testing wiht temporalsoften

incredible · #28 09-17-2004, 04:55 AM

Yep I AM TIRED

To clearify this (after having 8 cups of coffee *lol ):

RemoveGrain = Spatial Only

RemoveDirt = Temporal Only

J-Wo · #29 09-17-2004, 06:46 PM

okay, i'm hoping someone might post an optimal dvd or avi script soon, as i'm getting mighty confused! I just tried a removegrain + removedirt + dctfilter on my Alias DVDs, but I had the same problem as with sci fi sources like Babylon 5. During certain panning shots, you can see pixels "twinkling" in and out. Like if it's a night sky pan, stars will disappear randomly, or if you see a skyscraper in the distance then certain windows will have their lights randomly turning on or off. It's RemoveDirt at fault, because as mentioned it is temporal only. In the past I've experimented with scripts like this:

Code:

(resize here)
removegrain(mode=2)
TemporalSoften(2,4,6,6,2)
DCTFilter(1,1,1,1,1,1,0.5,0)

I'm really hoping someone can provide some more tips!

Dialhot · #30 09-20-2004, 04:16 AM

Quote:

Originally Posted by J-Wo

I'm really hoping someone can provide some more tips!

Kinda answer :
http://www.kvcd.net/forum/viewtopic.php?t=14141