exist any filter specially done for (deinterlace) flicker

[Adub]

For one, post your script.

For another post the error that you are getting. What happens when you drop the script into virtualdub or media player classic?

[thetoof]

You say there are no errors.... so I guess that what's going on here is simply that tgmc is too slow for you. Of course it'll hang in MPC... it is not meant for speeds such as 60/50 fps. And for megui, you could simply do a lossless rendering pass to speed up encoding.

1st - try drag & drop your avs in virtualdub. If something else than an error appears, it means it works (you could hit file-run video analysis pass to confirm)
2nd - In vdub : video-compression-Lagarith (YV12 mode) / video-fast recompress / file-save as (about 20-40GB per hour of
footage (unless you use selecteven/odd or some decimation)
Then use that file to create a new avs file and use that for x264.

If step 1 works, it means there is no problems. If you want to skip step 2, fine, but be prepared to wait for a while and make sure that you have enough ram to run this. If you're doing a 2 pass encode, a rendering pass is strongly recommended (this way you don't have to run the filters twice = overall major speed-up)

[News Bot]

I got it working ok, a preview comes up now. I had to use the "mt=false" command (I'm running a Quad Core). However now I get a dreaded "CAVISynthStream: System exception - Illegal Instruction at 0x46b4c86" instead of the video itself being rendered. I get it with everything from MPC, VirtualDub, MeGUI etc. It will encode, but the output will just be that error for the length of the video, as will the preview.

Any way to fix this? I've installed and uninstalled several versions of AviSynth but all give the same error.

As for my script:

ffmpegsource("sample.mp4")
AssumeTFF()
TempGaussMC_beta1mod(mt=false,edimode="NNEDI",tr2=1).SelectEven()
Spline64Resize(596,384)
maa()
LSFmod(strength=50)

I've tried using purely TempGauss alone, but it will not budge. Is there any way to fix this issue?

[thetoof]

I can't reproduce your issue. Do you have the TGMCb1mod that uses mvtools2? http://www.mediafire.com/download.php?zjmtgc2qrzi
Guess I should've put some version numbers of something... (at first, this was only meant as something to include in the requirements.7z of animeivtc, but I ended up posting it here and there. My bad.)

[News Bot]

Yeah, I've used every version of TGMC there is, but I still get hit with the same error.

[thetoof]

Have you updated your mvtools version? Does it work with another type of source? (avi, mpeg2..)
The latest ffmpegsource uses a 2 pass decoding :
ffindex("file"), then it'll say it did not return a video clip, and you run
ffvideosource("file")

[News Bot]

I've singled out MVTools as the reason for the error now. The ONLY filter I get it with is TempGauss but it is certainly an issue with MVTools.

I'm using Windows Vista Ultimate 64 bit with Service Pack 1. But I've heard that it works for others, so I'm totally confused on the whole issue. =/

[Terka]

have a look at:
http://portal.acm.org/citation.cfm?i...=portal&dl=ACM

[Terka]

can be TGMC be upgraded to use mvtools 2?
will be there any spead/quality gain?

[thetoof]

It has been "upgraded", though not officially. Check tempgaussmc_beta1mod (you can get it on the wiki).
You can test and report for the *whatever* gain.

[Terka]

is there any spead/quality gain?

[krieger2005]

Originally Posted by thetoof

You can test and report for the *whatever* gain.

:P. As i heard here in the forum it seems that it work better with MT, so with MT there should be an speed gain. Qualitywise there should't be any difference, since i think fizick just ported the internal processing from v1 to v2. But fizick can give here a better answer

[thetoof]

MT should be faster, but then you won't benefit of further upgrades (idx removal (requires less memory), MVDegrainx chroma shift correction (done in 1.10.2.1 and MT is 1.9.7.7... but Didée had corrected it for tgmc with the masktools anyways) and a few other thingies (see the latest MVTools2 changelog for more info)).
So, it doesn't work "better" (nothing really does in this forum ), but it's up to you to decide if the v2 upgrades are worth letting go of the MT speed boost.
On a side note, it'd be interesting to see the difference between SetMTMode(2,x) + mvt2 and mt=true.

[Boulder]

Is there an up-to-date TempGauss version with variableblur.dll being used? I seem to recall that it was supposed to be a bit faster, and the memory leak in the dll was fixed by neuron2 some time ago.

[Didée]

Can't tell for sure, but probably there isn't. Anyway, it doesn't matter. The Resize().Resize() combo (that replaces BinomialBlur()) on its own would perform multiple-times-realtime. So in the overall picture, the speed penalty is absolutely neglectable.

[Terka]

Which parametrs tweak in tgmc to calm static details like grass? Standard settings produce areas moving here and there.
see original:
http://rapidshare.com/files/25061661/Psi.rar
is it suitable to denoise/deblock (DV compression) before processing tgmc?

[2Bdecided]

Originally Posted by Terka

Which parametrs tweak in tgmc to calm static details like grass? Standard settings produce areas moving here and there.
see original:
http://rapidshare.com/files/25061661/Psi.rar

You've been deinterlacing that clip for nearly two years!

There's a bit of aliasing, which causes some instability. You can try some of the mo-comped super resolution stuff from other threads as a post-process, and then re-size back to SD. Painfully slow, but it helps a bit.

At least TGMC_alpha3 is more stable than mcbob. I'd be happy more than with it, I think - though it's too slow for most uses!

Cheers,
David.

[Terka]

is it possible to speedup the tg following way:
interlaced.separatefields() #not bobbing
calming
motion estimation
>so the calming an mo-est. is done on halve size clip.
is it possible to use the "halve_height" mo-vectors on original clip?

[Didée]

It could be done using MVIncrease(), but there's several problems. Accuracy (half- vs. full-pel) is one problem. A bigger one is that MVIncrease does *not* support block overlapping, so the process would be highly prone to introduce block artefacts.

[Terka]

the bobbed clip can be split to two using separatefields(); 2 clips processed used same mo-vectors. and weaved back.