Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP Export QT color shift bug?

  • FCP Export QT color shift bug?

    Posted by Terje Rian on March 28, 2009 at 11:21 pm

    Hello,

    I just can´t seem to get rid of (what I believe to be) an export QT bug in FCP 6.0.5? I have an example of the color shift that occurs after export. The example is three screen dumps made into a short and uploadable movie (.vmw format). I´m not sure how to uploaded the movie here, but I can mail it on request.

    Background:
    The original footage is shot with a Sony EX-3 and imported into a XDCAM timeline in FCP. From there the footage is color corrected in Color and sent back to FCP as ProRes HQ. I then make a QT export (self contained movie) of the file(s) using ProRes HQ. The exported file is imported into AFX CS4, downscaled from HD to SD (and additional graphics are added, but not on this particular shot). Export from AFX CS4 is ProRes HQ. After importing to FCP again all the final cuts are assembled into a master sequence. Lower thirds are added (made in AFX CS 4, exported as Animation with alpha) and of course the sound mix (from Pro Tools HD) is also added. The master is then exported as a self contained file to be compressed according to needs.

    The color shift error is traced back to the lower thirds. The problem seem to happen on three (of twelve) lower thirds during the 15 minutes long presentation. At least three where the error is clearly visible. There is a small visible error right before the lower third is introduced as well, but this error isn´t that noticable. I´ve got to nudge frames to see it. I´ve gone into AFX CS4 and tried to adjust the lower third in several ways (ie how the lower third fades out), but without any luck.

    The error isn´t visible until the master sequence in FCP is exported. Exporting the sequence without the lower thirds solves the issue. I´ve also tried to export through Compressor without any luck.

    The total amount of files on the FCP timeline is at most three stereo audio tracks, plus a master video track and the track where the wipes and lower thirds reside.

    I´ve tried to trash FCP Preferences and the User Data Folder.

    Can anyone tell me how to approach such an issue? Thank you for your time and help.

    Kind regards,
    Terje Rian

    Equipment used:
    Mac Pro Dual 2.66 GHz Dual-Core
    8 GB RAM
    Mac OS 10.5.5

    Caldigit HDOne 4 TB RAID
    Blackmagic Design Multibridge Pro

    Apple Final Cut Pro ver 6.0.5

    Adobe After Effects CS4

    Sunil Kumar replied 17 years, 1 month ago 2 Members · 4 Replies
  • 4 Replies
  • Sunil Kumar

    March 29, 2009 at 5:12 am

    Can you try adding the lower thirds to the master sequence in AE and exporting the final QT from AE?
    If the color shift is still happening, it might then be a Quicktime problem rather.

  • Terje Rian

    March 29, 2009 at 9:16 am

    Thank you fot taking the time to respond, Mr. Kumar. I´ll report back as soon as I´ve tested your suggested approach.

    Best,
    -terje

  • Terje Rian

    March 29, 2009 at 6:33 pm

    Hello,

    An update:

    The issue is now solved. By exporting the master sequence from FCP without lower thirds, I´m able to add the lower thirds in AFX and render out a useable master from there. Exporting files between FCP to AFX needs to be planned very carefully to be successful, it seems. The color shift bug is probably caused by how each software treats RGB vs YUV (AFX vs FCP). The ProRes codec is excellent as long as I stay inside Apple´s world, but not so good if I need to do work outside it. Hopefully this issue will be solved some day? I´ve spent at least two days to find out how to deal with this issue. Workarounds are great, but only if you know of them. Consider yourself warned.

    Best,
    -terje

  • Sunil Kumar

    March 29, 2009 at 9:41 pm

    Glad you could finally sort it out.

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