Avisynth: a Better Filter than Deen?

[Fluffbutt]

I've found a better filter than deen (which is brilliant on its own)

eDeen.

eDeen - Spatial monster for avisynth 2.5

Needs : YV12 colorspace, Avsiynth 2.5 & SSE capable cpu (Athlon XP, PIII)

syntax : edeen(r,ty,tuv,ly,luv,hqc)
defs : edeen(7,14,21,2,3,true)

- r :
radius, like always, 7 = (virtual) area of 15x15. max : 20

- ty,tuv :
threshs, like always. the bigger the stronger. max : 255,255

- ly,luv :
lowratios, the stuff who made the power of msoften despite his
monstruous problems. calm big thresholds with big raduis, to 
allow a very powerfull filtering without too much artefacts (max : thr/r)

- hqc : 
High-Quality Chroma filtering.
ahhh, another cool stuff ^^. you can notice it, even with defaults
parameters, especially on anime/cartoon content. 1/3 slower, because
everything is not mmxed, but quality really deserves it.
desactivate if you want speed or if you don't filtre like a beast chroma.

so, this would be the only beta version

Copyright (C) 2003 MarcFD - 19 jan 2003

Oh we can't attach images - I'd give you a demo if I could..

Suffice to say that deen is 9/10, but gives rough area on gradient changes in colour, and some halos on edges (anime). eDeen gives same quality with no halo, and gradients are treated perfectly 9.5/10.

Or do you all know this? Damn it, i'd just onve like to post something you lot don't know....[/IMG]

[incredible]

Yep, ... its not better its more impacting!!
Thats why its called a spatial "monster" ... so do watch out as you can't do that fine tuning like its possible when using just the regular Deen()!

I did many tests on both ... for anmies, means pictures using much plain surfaces and less complex natural details, eDeen() is a very effective one, but on natural movies you will losse very much of details ... check the overplained skins and plain hair structures of actors after using eDeen() and you will understand my preocupations

Uops .. I do see you did your tests on animes ... so you already did figured that out by yourself

[Fluffbutt]

Yes, incredible, I tried edeen on a 'real' movie, and the people turned out like anime paintings ( ) FUNNY!!!!!

While I've got you reading this, can you confirm something for me..

Softening and blending and smoothing a movie will actually cause blocking in the final (s)vcd - the encoder sees the smoothed areas as being the same and then compresses them highly (like jpg artifacts)???

So in a way it's better to have noisy bits; so how do you judge just how much noise to add/leave (too much would also mean a high file size where the encoder treats each little bit of noise as an area to compress) Or am I just talking out of my (_o_) ??

((?? blockbuster ??) - are there any docs for this?)

**Incredible - don't worry mate - i found it here
http://mf.creations.nl/avs/filters/Blockbuster.html
Thanks.

[jorel]

blockbuster ??
the SansGrip site is full working again. see all "read-me" and downloads:
http://www.indeus.com/sansgrip/avisynth/

SansGrip last post( 28-04-2004):
http://www.kvcd.net/forum/viewtopic....ghlight=#76000



Fluffbutt(last post) and ink, i agree with your opinions about eDeen!

[incredible]

I think its not logic to first kill "valuable" details using edeen() and then adding "nonsense" details like noise

You should find a way to combine the regular deen() with other, maybe temporalfilters as a real good approach is the usage of spatio/temporal treating scripts.

Cause with the example above in case of edeen() and Blockbuster() you will end up in an uneasy "people to anime converted" view

Better would be to make noise for example in captures not totally "dead" as by this you keep details and on the other hand the encoder gots still some "living" informations on surfaces which avoids blocks -- which is also the way of blockbuster as its a noise generator.

IF you use Blockbuster ... use it as a veeery fine "spray", that spray (if settet right) would be quantizised off and this quantizing lets the encoder work not different on plain surfaces --- cause where does the encoder quantize brutally?? On surfaces where are not that much details! = Blocks very fast on these surfaces.

So in case of blockbuster do look out for the blockbuster settings in Phils Optimal Script V4 i.E. where he offers a nice setting of blockbuster

[Boulder]

Has anybody experimented with RemoveDirt? Faster than Deen, compressibility is a bit lower since it's a temporal-only filter but did work wonders on my TV caps.

http://forum.doom9.org/showthread.php?s=&threadid=70856

[kwag]

Here's the author's site: http://www.removedirt.de.tf/

Did you compare it to STMedianFilter

-kwag

[Boulder]

Actually, no. I've not used STMedianFilter since it seems to be dead slow..I also prefer temporal-only filters since they keep the details a lot better even with higher thresholds.

I also haven't tried different settings for RemoveDirt, the defaults have worked very well. There might be a lot of tweaking to do

[incredible]

Hi Boulder.

I just found a posting at geitz.de where a Guy explains how to get rid of the Peachsmoother phenomenom, mens the moving contours in some cases like Kwag explained a time ago.

Ill search, translate and Quote it today in here, maybe that is also then a nice solution.

According to temporalfiltering I agree with you, only problem is if set too high ... that "static dots on surfaces while movement" no matter which temporal filter used phenomenom appars

[Holomatrix]

@ incredible - Can you post the Blockbuster line that you say 'Phils Optimal Script' includes. I can't seem to find it. I do low bitrate encodes and I find that blockbuster helps with the blocks on flat areas. I want to keep a really simple/fast script what to you think I should use to help get rid of the moskito effect around objects? Undot() at the end? I mostly encode from DVD. To keep my script fast and great quality I would like to do a lanczos/fluxsmooth/blockbuster/undot combo of some sort.
Thanks

[bigggt]

Hi

This one is from Phil's V4

Blockbuster(method="noise",detail_min=1,detail_max=10,variance=0.3,seed=5623)

[Holomatrix]

Thanks. Any comments on the rest of my script?

[Dialhot]

Quote:

Originally Posted by Holomatrix

Thanks. Any comments on the rest of my script?

Which script ?

[Holomatrix]

Sorry, just something fast, simple and with good quality:
[AVISYNTH_LanczosResize_Undot_FluxSmooth_Blockbuste r]
0=LANCZOSRESIZE(^TargetWidth,^TargetHeight)
1=undot()
2=FluxSmooth(^H_Value,^V_Value)
3=Blockbuster(method="noise",detail_min=1,detail_m ax=10,variance=0.3,seed=5623)
^H_Value=3
^V_Value=3

[bigggt]

Hi Holomatrix i was doing too many things at a time ,and in Phil's optimal script there are 2 blockbuster lines here is the other one

Blockbuster(method="noise",detail_min=1,detail_max=3,variance=0.1,seed=1)

You will have to wait for Phil again to tell you which one to use but i would think it would be this one because the other ones is commented out and only used sometimes

Here is the link to all his optimal scripts to help

http://www.kvcd.net/forum/viewtopic.php?t=7223

[Holomatrix]

Ok, thanks