ghosting on source?

[ministrix]

Hello!
I did a AssumeTFF().SeparateFields() in avs on this NTSC dvd. Still i got this ghosting artifact (chk pic). Does that means the ghosting is on source and therefor cant be dealt with or...?

[techreactor]

pic is yet to be approved, but still you can compare your source with the results and if the ghosting exists in both, you have an answer.

[ministrix]

And how do i compare? Looking at the vob in dgindex, it just looks like a lot of interlaced frames. I thought by doing the Assumetff.... setting in avs will show the source by field and then you can determine how to deal with it. Maybe im wrong...? Btw heres a url to the image http://img221.imageshack.us/img221/6408/vobsamplesc1.jpg

[foxyshadis]

Definitely fieldblended, or ivtc-blended, only a snippet could tell. Time to try MRestore.

[ministrix]

tx for the tip. tried with mcbob() mrestore(). didnt work. Do you got any suggestions for some parameters? Seems like mcbob is really heavy on resources on my machine. takes like 10 sec to get 1 frame forward in vdub. Also tried mvbob() mrestore) Got better result but still frames that are blended and this is also very heavy on system resources. Time is not such a great issue for me when it comes to encoding but its kinda annoying when i chk the avs in vdub. leakernelbob(order=1) and mrestore() seems to be close but not totally cigar, same goes for tdeint(mode=1) and mrestore(). both remove some troubled frames but still there some left. Maybe there are some tweakings here i can do?
Btw, how can i find out if its fieldblended or ivtc-blended?

[Didée]

Once more: MCBob is suited for true-video only, not for anything else. In particular, it's not suited for bobbing fieldblended sources.
(For fieldblended sources, motion compensated bobbing is not suited generally: you can't compensate a blended field with its not-blended neighbours, nor vice versa.)

For this task, use a motion adaptive bobber, e.g. TDeint.

[MOmonster]

@ministrix
The code for the ntsc sources currently isn´t complete. Maybe you can upload a small sample. This would be really helpful. You should also try repal and restore24 on your source. Maybe they perform better for you.

[ministrix]

Hello!
Yeah ive already tried repal. Did a good job but still not perfect. Gonna try restore24 later. But ill up a sample for you. Try grabbing here http://www.megaupload.com/?d=VMUU0SUN. Btw when i did
ord = last.getparity() ? 1 : 0
leakkernelbob(order=ord,dclip=last.crop(8,8,-16,-8))
Mrestore(bthresh=0.1)
i got the error msg of dclip does not exist as a argument, im i using the wrong version (1.5.4)?

[ministrix]

just try pasting a new link since the last one doesnt work.
Ill check tomorrow if it still works
http://files-upload.com/214484/sample.vob.html. Just x out the annoying ad

[MOmonster]

I could download the first sample and I tested it with repal, restore24 and Mrestore (all default settings).
Restore24 had some smaller problems with the blenddetection (tweaking necessary), repal give a fluid output but also don´t remove all blends and Mrestore give the same fluid output, but there are only four blends in your sample left. The code of Mrestore is not complete, but in my opinion it does a nice job with your sample.
It didn´t work so well for you, because you used the last version in the zip. This function is absolutly not recommed for NTSC sources. You should use this one (http://forum.doom9.org/showthread.php?p=998764#post998764).
In your script you use the dclip parameter in leakkernelbob, but it is a parameter of Mrestore.:)
The final version makes good progress, so I think I´ll finish it next week.

[ministrix]

tx for the help. Yeah with that new mrestore.avs (2.0 rc) it worked better. I think repal and mrestore gives pretty much same result. When it comes to the dclip parameter, i used the avs from your Mrestore.txt so you got yourself to blame. hehe. I found that
LeakKernelBob(order=1)
mrestore()
worked the best. You got other ways to mrestore thats a good bet?
I'm looking forward to test your finished version, so keep up the good work:)

[MOmonster]

@ministrix
Please wait for the final release in some days. There is a decimation bug in the current build. Mrestore will have problems with longer NTSC sources.

[~bT~]

^ yes, already encountered that prob 3 times. look 4ward 2 the final version.