Creative Communities of the World Forums

The peer to peer support community for media production professionals.

  • Richard Herd

    April 27, 2012 at 10:10 pm

    I’m screaming this one again: RANGE BASED EXPORT!! Maybe they can hear me in Cupertino.

  • Oliver Peters

    April 27, 2012 at 10:15 pm

    Post your feature requests to Apple’s feedback site.

    https://www.apple.com/feedback/finalcutpro.html

    It’s the only place they officially monitor. Posting them here is only venting.

    – Oliver

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

  • Bret Williams

    April 27, 2012 at 11:45 pm

    Then all is pretty much lost?

  • Derek Andonian

    April 28, 2012 at 2:15 am

    John Heagy Don’t expect Apple to “make it pro” if you don’t list what you want.

    But the thing about that is, it was ALREADY PRO before Apple butchered it…

    ______________________________________________
    “THAT’S our fail-safe point. Up until here, we still have enough track to stop the locomotive before it plunges into the ravine… But after this windmill it’s the future or bust.”

  • David Powell

    April 28, 2012 at 5:06 am

    Seriously? There’s no range based exports? You know the more I’m tempted to jump in and try X out, the more I get scared that simple things I’ve become accustomed to will be missing and making me tear my hair out. I’ve Been cutting on MC and I don’t get you ex-avid users that hate it so much. Especially if you’ve used 5-6.

  • Thomas Frank

    April 28, 2012 at 9:39 am

    Is your question asking if you should get FCPX?

  • John Heagy

    April 28, 2012 at 3:57 pm

    [Jeremy Garchow] “- More reliable/user controlled Project/Event backup system.
    – “Show matte” on Color Mask selections
    – Color Coded Roles
    – Expand Audio shows all audio tracks, not a mix down
    – Range based Project Export

    Interesting list Jeremy. It points out how different people’s needs are when it comes to FCPX.

    I’m looking for foundational items before we start asking for edit features. My 5 are:

    -Read embedded Reel/Tape ID in QT and export user defined reel in exported movies.
    -Include an “xml export” metadata tab where whatever is selected is exported in the xml.
    -Read only Xsan locations so other users can add the same location owned by another user.
    -Include all ProRes codecs in the Project Render setting.
    -Direct Renders where we want. Having renders be part of the Project location will blow up our Project volume and drastically impact our project backup policies.

    I have one request for AV Foundation:

    -Reference movie support so it can be added to FCPX.

    John Heagy

  • Miriam Lefkowitz

    April 28, 2012 at 4:19 pm

    FCPX is the only FCP program taught at the SVA film and video department in NYC. The dept. seems convinced apple is eventually going fix the major mistakes made with FCPX . The number of Avid classes has increased somewhat.

  • Oliver Peters

    April 28, 2012 at 4:34 pm

    [Miriam Lefkowitz] “The dept. seems convinced apple is eventually going fix the major mistakes made with FCPX “

    The reality is that they have no more advanced information about that than anyone on this forum. They are merely hoping.

    – Oliver

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

  • Jeremy Garchow

    April 28, 2012 at 4:40 pm

    [John Heagy] “I’m looking for foundational items before we start asking for edit features. My 5 are:”

    I figure there’s a ton of stuff thats missing foundationally, that Apple must be working on it. Perhaps it’s naive. A peep in to the metadata list seems to point to a lot of future XML potential.

    Also, with native MXF support and other roadmap features coming, it suggests a foundational beef-up to me.

    So I’d rather request to fix the interface parts, and hope that Apple is constantly beefing up the foundation.

Page 3 of 4

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