This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

A clash of the order (interlacing issues)

I've got my dm368 H.264 codec encoding and streaming std definition interlaced video captured from the composite input.  The problem is that I'm experiencing a clash between the spacial and temporal order of the fields.  It goes like this....

case A) Top field first. My encoder's input buffer pointer is the top field first, then the bottom field.  This produces an output that has a correct spacial order when using the DM368 decoder. I.E. a static picture looks correct.  However, when things are moving horz in the picture you get a double ghost image.  This is being played on a old CRT type NTSC monitor.

case B) Bottom field first.  If I send the encoder the bottom field first, then the decoder displays an incorrect spacial order.  I.E. you can visually see the fields are flipped.  But, the temporal order is correct and the things moving horz in the picture are displayed correctly.

If I view that video with top field first (case A) on VLC then the spacial order is correct.  So it looks like top field first is definitely the correct encoding order.  However with VLC it's hard to tell the temporal order.  I'm suspicious that the temporal order is wrong in case A, but can't be sure.

If the temporal order is encoded incorrectly in case A then I can only conclude that the capture driver is capturing fields from two separate frames.  I.E. it's capturing the bottom field from frame n and storing it as the top field of frame n+1.

Any comments?

John A