Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Log and Tranfer bug?

  • Log and Tranfer bug?

    Posted by Dan Dujnic on December 29, 2008 at 8:47 pm

    I found something weird using FCP 6.0.5 with footage that was shot on P2 at DVCPROHD1080i60, 24p using the 2:3 pulldown.

    Using FCP 6.0.2, Log and Transfer brings it in correctly: The clip created in Final Cut is 1080i60. But using FCP 6.0.5 the footage comes in as 1080p30.

    When the 60i clip is opened in the Viewer it has the familiar look of 59.94 footage with a 2:3 pulldown (stepping through does not reveal interlaced frames). But the 30p clip has interlacing issues when watched in the Viewer (two frames with obvious interlacing).

    Opening both clips in QT and stepping through, it seems that the clips have identical frames, despite being labeled differently in the Info window.

    I put both into a 1080i60 sequence and they play back correctly on an HD monitor. Put the 30p clip into an SD sequence (like in one of our offlines) and you get harsh interlacing. The interlacing is not present with the 60i clip in an SD sequence.

    Editing (and finishing) in HD shouldn’t be a problem since it’s playing correctly in a 1080i60 sequence, but I’m going to re-transfer some footage through 6.0.2 for an SD offline edit. FCP 6.0.5 (and 6.0.4, after a quick test) seems to be mis-reading or mis-labeling the MXF files when it sticks them in their quicktime wrapper.

    Anyone else experience this?
    -Dan Dujnic
    The system using 6.0.2 is a Mac Pro, QT 7.3.1.
    The systems using 6.0.5 were two Mac Pros and one G5, QT 7.5.5.

    Jeremy Garchow replied 17 years, 4 months ago 2 Members · 1 Reply
  • 1 Reply
  • Jeremy Garchow

    December 30, 2008 at 12:57 am

    [Dan Dujnic] “FCP 6.0.5 (and 6.0.4, after a quick test) seems to be mis-reading or mis-labeling the MXF files when it sticks them in their quicktime wrapper. “

    Yes, this appears to be a bug and I would alert Apple by sending them feedback as this is the third or forth time I have seen someone post about this.

    If you need to go SD, try setting your SD timeline to have a “field dominance” of none as I am sure your 1080p30 footage is tagged as progressive in FCP and the improper ‘metadata’ tagging between you footage and timeline can make your footage display improperly.

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