Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro 10.0.8 Update is Out

  • 10.0.8 Update is Out

    Posted by T. Payton on March 28, 2013 at 5:44 pm

    Check your App Store. Stick to the FCP X update code. Zip up your old 10.0.7 App and don’t update mid project.

    Looks like mostly maintenance. Which frankly is a great thing. The flashing green render is in the release notes.

    ——
    T. Payton
    OneCreative, Albuquerque

    Jeff Kirkland replied 13 years, 1 month ago 9 Members · 23 Replies
  • 23 Replies
  • Erik Lindahl

    March 28, 2013 at 6:05 pm

    ProRes Log C support is a great added feature!

    Wonder if they support S-log from Sony / Canon cameras as well…

  • T. Payton

    March 28, 2013 at 6:46 pm

    It looks like this is indeed a maintenance release for just a few things. That nasty green frame being the biggest one.

    At first glance
    – launch times is better
    – event browser is scrolling through multiple events quite smoothly
    – keyboard commands for changing the appearance of the timeline (but for some reason clip height adjustment by keyboard is missing. Perhaps I just missed it.)

    Hopefully there is a lot of little bug fixes that we will discover in the next few days.

    ——
    T. Payton
    OneCreative, Albuquerque

  • Nate Weaver

    March 28, 2013 at 8:19 pm

    Bigger than maintenance for me, had my F55 for 3 weeks now having to batch transcode XAVC in Resolve for weeks.

    Also LogC LUTs automagically applied is big deal too.

    Gonna see how well that 4K XAVC plays…!

    Nate Weaver
    Director/D.P., Los Angeles
    https://www.nateweaver.net

  • Steve Connor

    March 28, 2013 at 8:42 pm

    [Nate Weaver] “Gonna see how well that 4K XAVC plays…!”

    You need an updated Sony plugin for it to work, which should be uploaded shortly according to Sony.

    Steve Connor

    There’s nothing we can’t argue about on the FCPX COW Forum

  • Gary Adcock

    March 28, 2013 at 9:11 pm

    [Nate Weaver] “Also LogC LUTs automagically applied is big deal too.”

    Careful,

    the Alexa LogC support seems to require the Camera’s version 6.0 software or later. No Alexa media I have prior to that build is being seen by the app.

    But on the other hand look at the Alexa Metadata it can read from the file in 10.0.8!

    gary adcock
    Studio37

    Post and Production Workflow Consultant
    Production and Post Stereographer
    Chicago, IL

    Follow my blog at https://www.garyadcock.com

    Or follow me on Twitter
    @garyadcock

  • Oliver Peters

    March 28, 2013 at 9:17 pm

    The interesting thing is that this metadata is camera-specific based on Apple’s camera import SDK. The Log Processing that’s there is specific to Alexa files. I had a test event with several native formats and enabled the Log Processing button in my settings view in the Inspector. When I clicked on a C300 clip (Canon log), the button went away.

    – Oliver

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

  • Erik Lindahl

    March 28, 2013 at 9:28 pm

    Seems a bit silly not to simply have a * log conversion as there are more than one manufacturer using log-mode while filming. That said, perhaps ALEXA Log C is the most common to use, it would be better with a plug-in / user editable solution.

    I do find it frustrating that output via a video card still is sluggish in FCPX with the latest Apple hardware. Using an iMac 27″ i7, 680MX, 32GB RAM and Fusion Drive with an BM Ultra Studio Mini Monitor and it’s still lagging with 10.0.8. With lag i mean I hit play, there is a slight pause before playback begins. Turning off A/V Output removes this. Really feels like editing with rubber bands! Even having RGB Parade Scopes up with out A/V output has virtually zero lag (which should be far more resource intense IMO). This playback lag was never an issue in FCP7 even back in the days of G4’s. I’m using ProRes 422 1080p25 media off an external SSD drive via USB 3.0.

  • Jeremy Garchow

    March 28, 2013 at 9:30 pm

    [Oliver Peters] “The interesting thing is that this metadata is camera-specific based on Apple’s camera import SDK. The Log Processing that’s there is specific to Alexa files. I had a test event with several native formats and enabled the Log Processing button in my settings view in the Inspector. When I clicked on a C300 clip (Canon log), the button went away.”

    I wish there was a way to have it work like the “ColorSpace Override” drop down in which you could choose a transform LUT.

  • Oliver Peters

    March 28, 2013 at 9:36 pm

    [Erik Lindahl] “Seems a bit silly not to simply have a * log conversion as there are more than one manufacturer using log-mode while filming. That said, perhaps ALEXA Log C is the most common to use, it would be better with a plug-in / user editable solution.”

    Not silly at all. It’s NOT a global setting put into place by Apple. This is based on the camera SDK from Apple. Each manufacturer exposes the info they choose. Both ARRI and RED have supplied lots of support. In the case of Alexa, the Log setting is embedded metadata from the camera into the QT file itself. FCP X reads that setting and turns on the processing. You have to enable the Log Processing button into the Setting View, if you want to turn it off. It is NOT a filter or LUT per se, but rather a manipulation of the color sync info, like automatic color balance. Except with ARRI’s Log C curves.

    – Oliver

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

  • Erik Lindahl

    March 28, 2013 at 9:39 pm

    So in theory the same could be applied to Sony och Canon footage?

    Just did a grade in “good old” Color with Sony LogS and it was hard to find a LUT for it. That said it wasn’t particularly hard getting a good grade with out it. For the editorial however a which in the app would be terrific.

    That they still haven’t come to terms with video output is a bit shocking though. PremierPro had issues but as of CS 6 that particular problem seems fixed even on older hardware.

Page 1 of 3

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