Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Relinking loses Log-C LUT flags

  • Relinking loses Log-C LUT flags

    Posted by Oliver Peters on December 31, 2016 at 7:48 pm

    See my other post about moving files and relinking. This library is made up largely of ARRI Alexa footage, encoded as Log-C. Normally FCPX automatically applies a Log-C-to-Rec709 LUT. In the new location, after relinking, nearly all of the clips in any project no longer carry the LUT flag and, therefore, show up as flat Log-C. Clips in the events do show up with the LUT applied. Somehow the clips edited into the project have “forgotten” the LUT. Seems like a definite bug.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

    Jeremy Garchow replied 9 years, 7 months ago 3 Members · 7 Replies
  • 7 Replies
  • Noah Kadner

    December 31, 2016 at 9:02 pm
  • Oliver Peters

    December 31, 2016 at 9:16 pm

    Already done.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Noah Kadner

    December 31, 2016 at 9:26 pm

    Going to go out on a limb and say they probably won’t be getting back to you until next year.

    Noah

    FCPWORKS – FCPX Workflow
    FCP Exchange – FCPX Workshops
    XinTwo – FCPX Training

  • Jeremy Garchow

    January 1, 2017 at 4:47 pm

    I’ve seen this too, even when copying an event to a new library. Definitely seems buggish.

  • Oliver Peters

    January 11, 2017 at 1:32 am

    I’ve been able to do a bit more testing on this issue. Here are the scenarios:

    You have camera files like Alexa, where FCPX automatically adds a Log-C-to-Rec709 LUT. If you keep these files external and then move the files/library to another drive and relink, the LUTs are lost. Not only are they lost, but you cannot add the Log Processing setting back to the metadata view to re-apply the built-in LUT. If you try to add a third party filter with a Log-C LUT, the color correction doesn’t match the native version. So that’s not a viable solution.

    OTOH, if you imported/copied the file into the Library, and then when you move the Library (with embedded media) to another drive, the log processing and LUTs are retained.

    Bottom line – IF you have log camera files – and IF your camera files are external to the library – you CANNOT effectively create a back-up of the production with proper color in tact.

    Unfortunately embedding several TB of camera files into the Library is NOT a useful workflow.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Oliver Peters

    January 27, 2017 at 12:03 am

    After a bit more testing this appears to be the result of a refresh issue. When the files are external and you move the project and camera files, you have to relink the “missing” files. When you do, the need for LUTs is not detected and you are stuck with flat, log images.

    However, once you quit FCPX and reopen the app and that Library, the files are refreshed and LUTs are once again automatically applied. This seems to be similar as to when the yellow error icon stays there even after clips are relinked. This, too, goes away by quitting and reopening the app and Library. Clearly some sort of refresh issue.

    So based on this testing, it does seem like you can leave the media external if you so choose.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Jeremy Garchow

    January 27, 2017 at 1:21 am

    Thanks.

    I found his exact same solution as well and forgot to post back! 🙂

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