Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Ghosting Problem with Interlaced Frames

  • Ghosting Problem with Interlaced Frames

    Posted by David Olsen on February 17, 2006 at 5:11 pm

    I posted this a while back – am still getting this problem. I’ve tried exporting to M2V through both Compressor 2 and using DVD Studio Pro’s own embedded M2V encoding. The output is the same.

    The ghosting does not appear in Final Cut Pro (the interlacing is visible on computer monitor, you can see the lines and such) – but after being encoded to M2V – and output to DVD, this is the image you get if you pause the frame on TV in certain spots. It’s not really visible when in motion, only paused on moving frames.

    https://img279.imageshack.us/img279/5180/ghosting13pw.jpg
    https://img290.imageshack.us/img290/9033/ghosting29dh.jpg

    The material is being pulled from a Digibeta (and some from a Beta SP). Both seem to come up with this problem. We’re pulling it SDI through a KonaLH capture card at 10-bit, uncompressed. I’ve tried outputting it with various different bit-rate settings – and have tried many of the presets – the result is the same — changing the field order doesn’t seem to help either.

    David Olsen replied 20 years, 6 months ago 2 Members · 3 Replies
  • 3 Replies
  • David Olsen

    February 17, 2006 at 5:33 pm

    We have material that doesn’t exhibit this problem — and when watching it on the monitors we have, the interlacing isn’t visible. (so when watching movement, you don’t see the scanlines – even just framing through it, you won’t see the scanlines)

    BUT, the material that DOES exhibit the problem shows visible interlacing on the monitor (you can see the scanlines during movement).

  • Aaron Neitz

    February 17, 2006 at 8:47 pm

    I’m a little confused on the particulars – but I would copy the MPEG-2 setting, and switch the field order. so instead of evens, or automatic, have it go on the odds.

  • David Olsen

    February 17, 2006 at 11:13 pm

    I’ve tried even (bottom), odd (top), and none (progressive) — even (bottom) is what it’s supposed to take, but gives me the problem I have currently… odd results in a very shakey picture… and progressive makes the image flicker on the (B?) frames.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy