Argh interlaced stuff is killing me...

I'm dealing with a completely interlaced NTSC source, which is TFF and has an alternate scan type, according to bitrate viewer... Anyway, when I use autodetect in dif4u it wants to deinterlace it...ok, no problem, but after I encode it I notice that the video is fine except in high motion scenes, where there is a ghosting effect...so then I deselect TFF in DoCCEWS and try again, and I get the same problem :( So then I just try to keep it interlaced: so then disable autodetect in dif4u, let it do its thing, load up DoCCEWS and select only TFF and Alternate Scan, and the whole thing is jerky on my TV...I try again, disabling TFF and get similar results :( Anyone know if there's something specific i'm missing in dealing with this?

no idea. telecine works fine for me... When you CCE something, you set the parameters up as what the final output will be. So for deinterlacing, it matters not if you select TFF or BFF. The important thing would be that you use zigzag, not alternate, as the output is going to be progressive.

Regarding your jumpy video when you didn't deinterlace, it sounds like the field precedence is backwards. Your video is playing fields in the order 2-1-4-3-6-5 instead of in the order 1-2-3-4-5-6. You can use pulldown to correct the field order without re-encoding. The syntax is something like: Code:

i think i'll try that pulldown trick out right now... so, if the source is TFF and alternate, in doccews i select "TFF" and "Alternate" right? Only reason I ask is, upon researching a couple of threads in this forum i've read conflicting suggestions; some say to deselect "TFF" if bitrate viewer says its TFF, others say to select it........... :(

using pulldown/even worked perfectly! :) thanks for the tip, this was a major hurdle for me as most of the material i deal with is interlaced...

You can use these approaches to find the field order of the original, but it won't work to check the field order on your output. The field order on playback is determined by the TFF flags in the MPG stream. For example, the AviSynth and TMpgEnc approaches will show the same even=smooth, odd=jerky behavior on your output, regardless of how you have the TFF flags set (and incidentally, even=smooth or jerky will exactly match the original, regardless of TFF setting - it can be very misleading). As far as I'm aware, the only truly explicit way to check the field order is to play it on a TV.