odd color ghost like frame after deinterlace

[mazinz]

Not sure what the proper term would be, but it is almost like a ghosting (or possibly chroma) like effect I am getting after deinterlacing and only occurs on SOME scene changes (not all of them). It does not matter what deinterlace filter (or even decomb/ivtc) is used. The color effect appears for 1 frame only and always in the same spots.


my source is 4:3 720x480 mpeg 2 material (dvd). The clip itself is interlaced at a straight 29.97 fps (homedeck recorder route). The actual source was a vhs tape. NTSC

I am toying with this in virtualdub using the huff codec as output

For arguments sake, lets just say yes I need to deinterlace the material.
Is the frame issue I have solvable or is it a case of "that's just the way it is"? I can live with it if need be, but if I can remove it, even better

sample below- interlaced on the left pane with the deinterlaced artifact on the right

[jagabo]

The problem is the chroma channels of interlaced YV12 treated as progressive YV12. Are you opening the MPG file directly in VirtualDub? If so, use Video -> Color Depth... and set Decompression Format to YCbCr 4:2:2 YUY2 (some of the others will work too). If you're using AviSynth ConvertToYUY2(interlaced=true) or ConvertToRGB(interlaced=true) before giving the video to VirtualDub.

[mazinz]

The problem is the chroma channels of interlaced YV12 treated as progressive YV12. Are you opening the MPG file directly in VirtualDub? If so, use Video -> Color Depth... and set Decompression Format to YCbCr 4:2:2 YUY2 (some of the others will work too). If you're using AviSynth ConvertToYUY2(interlaced=true) or ConvertToRGB(interlaced=true) before giving the video to VirtualDub.

Thank you Jagabo. Yes i am opening the mpeg directly in VD. I did change the color depth decompression and it sort of worked but now it gives me a red effect, check the pic.

[mazinz]

Hey Jagabo

Looks like I might have got it. I keep the color depth decompress as you suggested, but right in front of my blind face I had also installed it's smart deinterlace 2.58 filter. I set that to blend (since it seems like a slight overlap of the frame blending). Setting it to blend took care of the problem as you can see in the pic below. If this still look wrong to you, please let me know-

[mazinz]

Ok truly solved it. I had a severe crash course with avisynth ( AvsPmod is a godsend!!) and finally getting some long over due options I wanted running. This included getting all the filters needed for QTGMC. I read up on that, but though it did a wonderful job it still gave a duplicate frame. So instead I ran the TFM/TIVTC filter and THAT got it going and did a much better job than the Decomb filter in virtual dub. No crazy colors, no dupe frames and nice smooth motion. My end script looked like this

LoadvfapiPlugin("C:\Program Files\Womble Multimedia\MPEG Video Wizard DVD 5.0\WbpVFAPI.vfp", "womble")
womble("C:\Documents and Settings\SOME GUY\Desktop\borders test.wbp")
FlipVertical
AssumeTFF()
ConvertToYv12(interlaced=true)
TFM().TDecimate()
crop(18, 0, -8, -12)
addborders(12, 12, 12, 12)

In my case I am then putting this script into avs2dvd to skip the entire avi step. Either way your mention of avisynth and what to use in post #2 really made me look into it a bit more and I am glad I did

[manono]

Didn't you say the source was a DVD? VFAPI is horrible. Get the DGMPGDec package and read the included docs on making a D2V project file with DGIndex so you can use the DGDecode.dll and MPEG2Source. Then, because the DVD is in YV12 to begin with you won't have the two colorspace conversions and can skip that 'ConvertToYv12(interlaced=true)' line. But I don't understand what you did in Womble and maybe using that necessitated using a VFAPI. But I doubt it.

Also you have in the script:

crop(18, 0, -8, -12)
addborders(12, 12, 12, 12)

and if the source is really a 720x480 DVD, that gives you 718x492 which is very peculiar and won't author as a DVD. You'll need a different set of AddBorders numbers.

[jagabo]

Blend mode in Smart Deinterlace blurs the two fields together resulting in a double exposure look when motions are large. It's one of the worst deinterlacing methods. As you've found, an inverse telecine (TFM().TDecimate()) is the better method of handling telecine film sources. I second manono's suggestion of using DgIndex and Mpeg2Source().

http://neuron2.net/dgmpgdec/dgmpgdec.html

[mazinz]

Didn't you say the source was a DVD? VFAPI is horrible. Get the DGMPGDec package and read the included docs on making a D2V project file with DGIndex so you can use the DGDecode.dll and MPEG2Source. Then, because the DVD is in YV12 to begin with you won't have the two colorspace conversions and can skip that 'ConvertToYv12(interlaced=true)' line. But I don't understand what you did in Womble and maybe using that necessitated using a VFAPI. But I doubt it.

Also you have in the script:

crop(18, 0, -8, -12)
addborders(12, 12, 12, 12)

and if the source is really a 720x480 DVD, that gives you 718x492 which is very peculiar and won't author as a DVD. You'll need a different set of AddBorders numbers.

Blend mode in Smart Deinterlace blurs the two fields together resulting in a double exposure look when motions are large. It's one of the worst deinterlacing methods. As you've found, an inverse telecine (TFM().TDecimate()) is the better method of handling telecine film sources. I second manono's suggestion of using DgIndex and Mpeg2Source().

http://neuron2.net/dgmpgdec/dgmpgdec.html

Hey guys, sometimes using the Dgindex I would get problems either with the actual mpeg reading or script errors (and more plugins to find). I use womble for this purpose. I just put my clip in womble and save the project. It frameserves but you do not need womble open at all. It serves in a similar way to what DGindex is doing. Thing is it works without giving me an issue, so I use it.

For some reason though avs (and favc) would ignore that I have interlaced and deinterlace it anyway. I would get that issue using dgindex and even though I would have a similar script like this one (ConvertToYv12(interlaced=true) to force it, it would still deinterlace without me adding in any deinterlace script command. I also would get sync issues on occasion when I shouldn't have them using DG. So in the end I use womble and so far so good

The add/crop I had because I am going to be compositing (later) two sources into one film. Both of these sources (2 different versions of the same film) have some nasty black (or skewed) video signal on the edges that you would get when not viewing it with any over scan (except on all sides). I wanted to fix this so I crop each one to where it has to (so now each has nice picture at the edge and no black border). I then added in a border of 12 for each side so it gives it a "center" kind of look. Now each film has the same amount of border (to compensate for overscan) and each one is transitioned in the same spot

AVS2dvd (with 2 pass henc) takes care of the resizing since each is a multiple of 4 and it adds the pulldown flag as well

tinkering to have it multiples of 2 so this should be fine
crop(16, 0, -8, -12)
addborders(12, 6, 12, 6)

using the crop/borders from above it came out like this:



In my head I was thinking that if I did not keep the convert to=interlace command it would think the clip was progressive to begin with. Since I am just going to be doing an ivtc on it would it be safe to say I can remove the ConvertToYv12(interlaced=true) command from the script?

[manono]

Since I am just going to be doing an ivtc on it would it be safe to say I can remove the ConvertToYv12(interlaced=true) command from the script?

No, since your VFAPI is RGB and the IVTCs don't work in RGB, I don't believe. None of what you said about MPEG2Source is correct. It isn't responsible for the actual mpeg reading or script errors (but you may be, though) or any audio going out of synch.

As for FAVC forcing a deinterlace, that's hardly the fault of MPEG2Source. If you can't find a setting to turn that off, use a different program, perhaps Avs2DVD. Which you do sometimes?

tinkering to have it multiples of 2 so this should be fine
crop(16, 0, -8, -12)
addborders(12, 6, 12, 6)

Yes, that's better. What you did before changed the aspect ratio, no matter how slightly. It does make it slightly less compressible, though (those 6 and 12 edges). I do similar sometimes.

AVS2dvd (with 2 pass henc) takes care of the resizing...

You can do it yourself in the script, if necessary.

[mazinz]

Since I am just going to be doing an ivtc on it would it be safe to say I can remove the ConvertToYv12(interlaced=true) command from the script?

No, since your VFAPI is RGB and the IVTCs don't work in RGB, I don't believe. None of what you said about MPEG2Source is correct. It isn't responsible for the actual mpeg reading or script errors (but you may be, though) or any audio going out of synch.

As for FAVC forcing a deinterlace, that's hardly the fault of MPEG2Source. If you can't find a setting to turn that off, use a different program, perhaps Avs2DVD. Which you do sometimes?

tinkering to have it multiples of 2 so this should be fine
crop(16, 0, -8, -12)
addborders(12, 6, 12, 6)

Yes, that's better. What you did before changed the aspect ratio, no matter how slightly. It does make it slightly less compressible, though (those 6 and 12 edges). I do similar sometimes.

AVS2dvd (with 2 pass henc) takes care of the resizing...

You can do it yourself in the script, if necessary.

Avs2dvd would do that sometimes as well. So when I checked the end result sometimes my clips were deinterlaced and progressive, but it would be a bit random as to when it would happen. Never really found a reason why so i just pay more attention to it.

Thanks for the script info. As to some of the other issues (like losing sync) doing it with the dv2 method produced that, but if I framerseved (lets say to the older tmpg 2.56) that did not occur. That too was not a constant and it would happen on occasion. Could possibly be some over site on my end that I missed or even dgindex not seeing the clip info correctly. Either way it is still here on my pc and will look further into it down the road. For now and for what I need to do the womble vfapi is working so I am going to stick with that. The end result still looks nice. And even with the two pass it only took 90 mins (film is about 82 mins) which is not bad at all.

I appreciate the info. I am starting to like avisynth a lot more than I ever have before