AVCHD 1080i / GraphEdit / VDub: De-Interlaced problem?

[MagnumRT]

Hello!

The video makes it to VDub. The problem is that even when I use a de-interlace filter in VDub, it is still ghosting badly.

Here's how I'm doing it.

1) TsMuxeR to demux AC3 and 264 files.

2) Created a GraphEdit file. The mapping is:
.264 file from Sony 1080i camera > Cyberlink Demux > Cyberlink AVC/264 Decoder (I have PowerDVD 7.3 installed)

3) My AviSynth file looks like this:

DirectShowSource("C:\Docume~1\Admini~1\Desktop\alan2.grf",

audio=false)



4) Resulting "File Information" in VDub
http://chuckundercover.com/vdub.jpg


So, for the life of me, I am confused and tired of searching for clues. This same setup works flawlessly with my ripped HD movies because they are progressive.

Anyone can throw me a bone? lol Thanks!

[neuron2]

What deinterlacer and settings are you using?

[Leak]

Also, were you looking at the input or the output pane, or at the encoded result?

The effect an interlacer (or any VDub filter) has, if any, will not be visible in the input pane, which by default might be the only pane visible if your monitor's resolution is smaller than your video file's.

But to be honest I'd use an AVISynth deinterlacer anyway since there's a much broader (and more recent) selection of deinterlacers available and you're already using AVISynth to boot...

[MagnumRT]

Thanks for responding.

Yes, I am looking at the output pane. I've tried both VDub's internal deinterlace (blend mode) and also Grisoft's Deinterlace. Both make absolutely no difference and the ghosting is exactly the same as in the input pane.

I have come across a few AviSynth deinterlace tutorials but they are overwhelming. I can't find any concrete examples for me to follow. I'd be interested in learning how but if I could be pointed to the right direction, I'd really appreciate the help!

Thanks guys

[Leak]

Both make absolutely no difference and the ghosting is exactly the same as in the input pane.
Wait - weren't you talking about interlacing? Blending and interlacing are absolutely not the same thing, and a deinterlacer can't help you with blending (hence the name).

http://leak.no-ip.org/Stuff/Interlacing.png ... interlacing
http://leak.no-ip.org/Stuff/Blending.png ... blending

So which is it?

Also, come to think of it - VDub's "deinterlace (blend mode)" deinterlacer does exactly that: it blends both fields together. I don't know the other deinterlacer you mentioned.

If you want no blending you'll (obviously) have to use a deinterlacer that doesn't blend...

I have come across a few AviSynth deinterlace tutorials but they are overwhelming. I can't find any concrete examples for me to follow. I'd be interested in learning how but if I could be pointed to the right direction, I'd really appreciate the help!
Ummm... putting, say, LeakKernelDeint(order=0, threshold=4) after your DirectShowSource line should be a start... (if the resulting video is jerky you probably need order=1)

[MagnumRT]

It's definitely the blending picture you posted.

What I've noticed in VDub is that when I load (directly into VDub) a regular interlaced MPEG2 file recorded from my TV card, VDub distinguishes the frames as I, P, B. So I assume it knows that it's interlaced.

In the case of loading the AVC 1080i file with AviSynth / GraphEdit, VDub does not distinguish the frames. They are all "K" frames. So, I assume, VDub believes it's a progressive source so it can't deinterlace...right or wrong?

Anyway, as you say, I'm sure this can be solved by doing it via AviSynth. I tried your code after DSS line, but it did nothing.

I'm starting to think it's my GraphEdit map...

[neuron2]

What I've noticed in VDub is that when I load (directly into VDub) a regular interlaced MPEG2 file recorded from my TV card, VDub distinguishes the frames as I, P, B. So I assume it knows that it's interlaced. That's a total non-sequitur. The picture coding type has nothing to do with interlaced/progressive nature of the content.

In the case of loading the AVC 1080i file with AviSynth / GraphEdit, VDub does not distinguish the frames. They are all "K" frames. So, I assume, VDub believes it's a progressive source so it can't deinterlace...right or wrong? Wrong. The frames are all shown as keyframes because Avisynth has decompressed them and is delivering raw video to VirtualDub. Instead of going in circles with all this uninformed talk, you should just post a short *unprocessed* sample of your source stream. Then we can tell you exactly what is going on.

[florinandrei]

Right after DirectShowSource() try to add AssumeTFF() and see if that makes ghosting disappear.

DirectShowSource(...blah...)
AssumeTFF()

[MagnumRT]

That's a total non-sequitur. The picture coding type has nothing to do with interlaced/progressive nature of the content.

Wrong. The frames are all shown as keyframes because Avisynth has decompressed them and is delivering raw video to VirtualDub. Instead of going in circles with all this uninformed talk, you should just post a short *unprocessed* sample of your source stream. Then we can tell you exactly what is going on.

Thanks for that quick lesson. I'll see what I can do about some clips...

Right after DirectShowSource() try to add AssumeTFF() and see if that makes ghosting disappear.

DirectShowSource(...blah...)
AssumeTFF()

Just tried it. Didn't make any difference. I have a feeling that my GraphEdit is not setup properly... Although when I play/render the video file in GraphEdit, it's crystal clear, smooth and deinterlaced.