MeGUI failing to detect Interlacing

Siberian · 27th May 2009, 13:37

After reencoding several dvds using meGUI i noticed that 1 ep in particular had some very noticable interlacing artifcats in the final encode. DGIndex detects the source as interlaced TFF. But the MeGUI analysis detects it as progressive.

I made a d2v of a small 1 min section of the source and put that in MeGUI and it detected it as partially interlaced with varying field order. So obviously the analysis detects the interlacing when on a small specific section fo the source but not when doing the whole thing. I tried changing analysis percent to 100 but with no luck.

So are there any options i can change to help MeGUI detect it as interlaced? Or at the very least is there some way that i can make a new avisynth profile and force deinterlacing?

Guest · 27th May 2009, 13:53

Quote:

Originally Posted by Siberian

DGIndex detects the source as interlaced TFF.

That doesn't mean the content is necessarily interlaced.

Inspector.Gadget · 27th May 2009, 16:59

You can always force deinterlacing simply by putting it in your script. The original preview window that MeGUI opens will not apply any processing and you can look for interlacing or pulldown patterns. FYI, I've had source detection fail on short sources as well - generally animated sources with slightly blurred fields or a combination of interlaced areas and aliasing. If source detection fails, and I find interlaced areas but no pulldown pattern (or less than at least 1 combed dupe frame out of every 5 frames for low-motion sources), I just throw YADIF at it using the field order from the VOB. If that looks bad, I try the opposite field order. Generally, one of the two is OK, and any remaining jagged lines I clean up with a combination of SAA() and MSharpen().

Is your source animated?

Siberian · 28th May 2009, 01:03

No the source is not animated. Its is a standard 40 min tv show. I did a couple of episodes and didnt notice anything even though DGIndex was stating it was interlaced and megui wasnt picking it up. But one ep was really bad as the flashes from weapons fire was replaced with some nice black bands. So it is clearly interlaced but most of the ep doesnt move fast enough to notice it.

I was trying to make a forced deinterlace avisynth profile so that i could still use oneClick so i dont have to manually set it to interlaced everytime but i dont think that is possible. I can manually add the yadif call to the script but ColorMatrix wont be set to interlaced by the profile. So i can manually add the Colormatrix to the script and disable the check box for it but then it wont work as DGDecode wont be set to export hints.
Is there anyway to force this in the avisynth profile?

27th May 2009, 13:37	#1 \| Link
Siberian Registered User Join Date: Jul 2008 Posts: 4	MeGUI failing to detect Interlacing After reencoding several dvds using meGUI i noticed that 1 ep in particular had some very noticable interlacing artifcats in the final encode. DGIndex detects the source as interlaced TFF. But the MeGUI analysis detects it as progressive. I made a d2v of a small 1 min section of the source and put that in MeGUI and it detected it as partially interlaced with varying field order. So obviously the analysis detects the interlacing when on a small specific section fo the source but not when doing the whole thing. I tried changing analysis percent to 100 but with no luck. So are there any options i can change to help MeGUI detect it as interlaced? Or at the very least is there some way that i can make a new avisynth profile and force deinterlacing?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

27th May 2009, 16:59	#3 \| Link
Inspector.Gadget Registered User Join Date: May 2008 Posts: 1,618	You can always force deinterlacing simply by putting it in your script. The original preview window that MeGUI opens will not apply any processing and you can look for interlacing or pulldown patterns. FYI, I've had source detection fail on short sources as well - generally animated sources with slightly blurred fields or a combination of interlaced areas and aliasing. If source detection fails, and I find interlaced areas but no pulldown pattern (or less than at least 1 combed dupe frame out of every 5 frames for low-motion sources), I just throw YADIF at it using the field order from the VOB. If that looks bad, I try the opposite field order. Generally, one of the two is OK, and any remaining jagged lines I clean up with a combination of SAA() and MSharpen(). Is your source animated?

28th May 2009, 01:03	#4 \| Link
Siberian Registered User Join Date: Jul 2008 Posts: 4	No the source is not animated. Its is a standard 40 min tv show. I did a couple of episodes and didnt notice anything even though DGIndex was stating it was interlaced and megui wasnt picking it up. But one ep was really bad as the flashes from weapons fire was replaced with some nice black bands. So it is clearly interlaced but most of the ep doesnt move fast enough to notice it. I was trying to make a forced deinterlace avisynth profile so that i could still use oneClick so i dont have to manually set it to interlaced everytime but i dont think that is possible. I can manually add the yadif call to the script but ColorMatrix wont be set to interlaced by the profile. So i can manually add the Colormatrix to the script and disable the check box for it but then it wont work as DGDecode wont be set to export hints. Is there anyway to force this in the avisynth profile?