MCTemporalDenoise [v1.4.20 - Update 2010/07/02]

[Terka]

Hi LaTo,
have you tried the pre-search routine for better motion vectors search introduced by Didee in TGMC?

[Didée]

What for? MCTD already offers "normal" pre-filtering for motionsearch, and that is fully sufficient. The routine in TGMC is custom-tailored to remove the typical on-off-on-off resp. up-down-up-down of spatially-interpolated bobbing. For arbitrary non-interlaced input, there is not any benefit to use that particular method. Chances are that it would come out less good than FFT3D-prefiltering.

For very tough cases, sometimes it is benefitial to use some additional stabilization after FFT3D, since FFT3D might leave back some "nervous" areas that still can mislead the motion engine (see the "HQDN3D" addendum in my predecessor-to-MCTemporalDenoise script). (In MCTD, this is partly achieved via debanding - it's not temporal stabilisation, but helps to dimish the sideffects that *floating* banding imposes on the motionsearch).
But that's big guns for big enemies, and not related to what TGMC is doing.

[Terka]

ok. to be clear for me.
(all following is regarding progressive filtering)
1.temporalsoften routine from TGMC part is worse than ttf3d (or fft3d +HQDN3D)
2.how do you check the quality of motion search? (mean for practical testing-which prefilter to use etc.)

[Didée]

Originally Posted by Terka

1.temporalsoften routine from TGMC part is worse than ttf3d (or fft3d +HQDN3D)

No, that's a false statement. If it would be "worse" and FFT3D would be "better", then tell me why I didn't use FFT3D within TGMC?

It's not worse, it's just different. For what is to be done in TGMC, the temp-gauss temporalsoften is method-of-choice. For general noise removal prior to motionsearch, FFT3D is the (most versatile) method of choice.

A hammer for the nails, a screwdriver for the screws. Each for it's own purpose.

( I know you said "(all following is regarding progressive filtering)" - but even in TGMC, all filtering is in fact done on progressive frames...)

2.how do you check the quality of motion search?

Eyeballing + experience. Very rarely, vector visualisation.

[Terka]

my problem is i cant recognize the nails/screws without putting the screwdriver on it.

[mozzle]

Originally Posted by Boulder

Are the older versions available somewhere? I'd like to test versions from v1.3.0.0 on to see whether my odd x264 crashes are due to MCTD. It is pretty much the only thing that I have changed recently and debugging x264 pointed the error to be related to Avisynth.

Hey Boulder. Did you figure out if it was MCTD that was crashing x264. I've been having the same crashing issue and had to revert back to x264 v1400.

[Boulder]

No, at least v1.3.0.9 didn't help and that's where the bigger changes were not yet introduced. I'm currently running a test to see whether a different Avisynth version helps (I used to have 2.6.0-MT but now I'm trying 2.5.8-MT). If that doesn't help, I'll try non-ICL builds of x264.

[~SimpleX~]

First of all, thanks for awesome script, LaTo. But I got some problems when tried to encode my video.

That's the problem: http://www.mediafire.com/imageview.p...ey=4jzvwmmmy2j

And this's the script I used:

setMTMode(2,0)
SetMemoryMax(256)

src=DGDecode_MPEG2Source("C:\Encoding\Cafe Junkie\VTS_01_1.d2v", info=3, cpu=0)

src=src.ColorMatrix(hints=true, threads=0)

progressive=src.AnimeIVTC(mode=1, aa=1, ifade=true)

ECMode="DFTTest().dehalo_alpha_MT(darkstr=0.7,brightstr=1.7)."+
      \ "awarpsharp2(depth=10, blur=2, chroma=2).FastLineDarkenMOD(thinning=12,strength=80, luma_cap=170)"

denoised=progressive.MCTemporalDenoise(\
                                                         settings="low", radius=2, GPU=false, fixband=true, sigma=3, chroma=true      ,\
                                                         edgeclean=true, ECmode=ECMode, ECrad=3, ECthr=16                                  ,\
                                                         enhance=true                                                                                         ,\
                                                         protect=true                                                                                          ,\
                                                         sharp=true, strength=140                                                                         ,\
                                                         post=0                                                                                                   ,\
                                                         deblock=true                                                                                           )



final=denoised.ediaa().Tweak(sat=1.1).Crop(0,0,-2,0).Spline36Resize(720, 540)

final
__film = last
__t0 = __film.trim(0, 36751)
__t0

What am I doing wrong?

[Boulder]

Originally Posted by Boulder

No, at least v1.3.0.9 didn't help and that's where the bigger changes were not yet introduced. I'm currently running a test to see whether a different Avisynth version helps (I used to have 2.6.0-MT but now I'm trying 2.5.8-MT). If that doesn't help, I'll try non-ICL builds of x264.

It seems that Avisynth 2.6.0-MT causes the problem, no crashing with 2.5.8. I'll have to ask SEt to see if he can find anything wrong there.

[ninja_racoon]

there's a problem when I use MT and MCT+global settings together

MT("MCTemporalDenoise(settings="low")",2,0)

how can I get this to work?

[Gavino]

Originally Posted by ninja_racoon

MT("MCTemporalDenoise(settings="low")",2,0)

how can I get this to work?

Use triple quotes to allow nested string literals:
MT("""MCTemporalDenoise(settings="low")""",2,0)

[Poutnik]

Originally Posted by Gavino

Use triple quotes to allow nested string literals:
MT("""MCTemporalDenoise(settings="low")""",2,0)

The question is, if MT() in conjunction of MC scripts is a good idea.
Most people think it is not, because MC need to cover all spatial scope.

[nautilus7]

I get an error when using settings="very low" or settings= "low". It seems that mode doesn't have the correct value in line 1060:

GFc = (enhance==true) ? TTc.GradFun2DBmod(thr=GFthr,thrC=chroma?GFthr:1.0,mode=0,str=AGstr,strC=0.0,temp=temp,adapt=bias,mask=false,show=false)

[Blue_MiSfit]

Meh.. I use MT all the time with MDegrain2. It's not optimal, but I've yet to see hideous artifacts.

SetMTMode is probably preferable, but it's caused more problems in my case.

MCTD is fantastic, especially in a pure 64 bit environment with the latest 2.5.8 builds!!!

~MiSfit

[LaTo]

Originally Posted by nautilus7

I get an error when using settings="very low" or settings= "low". It seems that mode doesn't have the correct value in line 1060:

GFc = (enhance==true) ? TTc.GradFun2DBmod(thr=GFthr,thrC=chroma?GFthr:1.0,mode=0,str=AGstr,strC=0.0,temp=temp,adapt=bias,mask=false,show=false)

Originally Posted by mozzle

I am getting the following error in MeGUI with 1.4.08:

Any help would be appreciated.

Originally Posted by LaTo

Re-download GradFun2DBmod v1.5! (here)

Answer was in the topic, page 15

[nautilus7]

Sorry, my bad.

[Poutnik]

Originally Posted by Blue_MiSfit

....
MCTD is fantastic, especially in a pure 64 bit environment with the latest 2.5.8 builds!!!

I feel little simple-minded but how is it possible to use MCTD in pure 64bit enviroment ?
I know there is 64bit Avisynth, but are there all needed Avisynth plugins ported to 64bit yet?
It would be great news for me.

[levi]

not to get off-topic, but you can find the 64bit avisynth + 64 bit plugins here

[~Revolution~]

I'm not sure if its just me but MDegrain2 with MT always causes a transparent type, very light, grainy horizontal line straight in the middle of the video.

[lych_necross]

How much faster would MCTD perform using a 64bit build of avisynth and 64bit pluigns versus all 32bit avisynth software?