Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations FCP X Summit: new features/news

  • Noah Kadner

    October 31, 2017 at 3:05 pm
  • Shane Ross

    October 31, 2017 at 3:37 pm

    [Erik Lindahl] “I wonder if they’re going to sort out the compound clip nightmare when sending edits to apps like Resolve.”

    You can un-compound them in Resolve. Simple right-click menu option away.

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Erik Lindahl

    October 31, 2017 at 5:35 pm

    De-compose compound clips work sometimes and sometimes not. Also if you get a 20 min short film where every single clip is a compound clip and a lot of them even have compounds with-in compounds and you want to send clips to VFX… iiiiish!

  • Erik Lindahl

    October 31, 2017 at 5:36 pm

    AV output via a video interface is pretty much broken. Very laggy and almost unusable for anything but play-though of a final edit.

  • Shane Ross

    October 31, 2017 at 6:16 pm

    Ah…point taken

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Jeremy Garchow

    October 31, 2017 at 7:19 pm

    [Erik Lindahl] “De-compose compound clips work sometimes and sometimes not. “

    Decompose usually works if there’s only effect from FCPX (I don’t know why Resolve compounds those clips, must be the way it handles it in FCPXML and therefore processing?) It also happens on repositioned clips (or 4k in 1080 timelines)

    Decompose does not work with time remapped clips. I usually have to rebuild those clips in Resolve. This works great, as Resolve’s time remapping is very similar in functionality to FCPX, but it does take a while to do. The good thing is that once it is rebuilt in FCPX, the send back usually works well in FCPX via FCPXML.

    I was hoping this would be better in Resolve v14, but it’s the same as previous versions.

  • Bill Davis

    October 31, 2017 at 7:58 pm

    [Erik Lindahl] “them even have compounds with-in compounds and you want to send clips to VFX… iiiiish!”

    That just makes me shake my head.
    Reference clips buried within reference clips is a sign to me that an editor doesn’t really understand X very well – and are maybe trying to re-capture “nesting” behaviors they relied on in other software approaches.
    “Let me just compound the compound that holds my Sync clips!” – what could go wrong with that?
    Getting layers and layers away from the actual clip data pool via “over referencing” is a recipe for angst later in on your workflow, IME.
    YMMV.

    Creator of XinTwo – https://www.xintwo.com
    The shortest path to FCP X mastery.

  • Jeremy Garchow

    October 31, 2017 at 8:52 pm

    [Bill Davis] “Reference clips buried within reference clips is a sign to me that an editor doesn’t really understand X very well”

    I believe he’s talking about Resolve.

    Sometimes, like if a clip is retimed, Resolve will put the entire source clip within a compound clip when you import an FCPXML regardless of how the clip is displayed in FCPX. It’s weird.

  • Michael Gissing

    October 31, 2017 at 9:10 pm

    [Jeremy Garchow] “Sometimes, like if a clip is retimed, Resolve will put the entire source clip within a compound clip when you import an FCPXML regardless of how the clip is displayed in FCPX. It’s weird.”

    Yes it is annoying but I have also seen compounds within compounds after importing to Resolve via fcpxml. I think editors might do it to apply a single effect to a bunch of clips. Same reason nesting was sometimes done. It seems strange that Resolve hasn’t fixed this or maybe they are just being 100% compliant to the fcpxml standard. They were, after all, one of the first finishing tools to get this format working otherwise reliably. Hard to know were the blame may be.

  • Andy Field

    October 31, 2017 at 9:48 pm

    it was a joke …. the humor impaired sometimes miss that

    Andy Field
    FieldVision Productions
    N. Bethesda, Maryland 20852

Page 5 of 10

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