Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro In a bit of a muddle with compound clips

  • James Ewart

    September 30, 2013 at 2:03 am

    Okay thanks for that…interesting.

    Any performance issues with keeping a bunch of different versions as a compound clip?

  • Ronny Courtens

    September 30, 2013 at 10:47 am

    Great thread with some great ideas indeed!

    Compound clips used to bug down FCPX in earlier versions. Today I can see no performance issues with using CCs.

    – Ronny

  • Charlie Austin

    September 30, 2013 at 3:11 pm

    [Ronny Courtens] “Great thread with some great ideas indeed!

    Compound clips used to bug down FCPX in earlier versions. Today I can see no performance issues with using CCs.”

    Agreed. 🙂 Although personally I wouldn’t make any drastic workflow changes ’til I see what Apple has cooked up in the next version of X. I make lots of versions as I go along, and duplicating in the Project Library for versioning is what I do now FWIW…

    ————————————————————-

    ~”It is a poor craftsman who blames his tools.”~
    ~”The function you just attempted is not yet implemented”~

  • Oliver Peters

    September 30, 2013 at 5:00 pm

    [Jeff Kirkland] “When you break a compound clip apart, you are copying the clips from its internal timeline onto your current timeline and so are no longer working with the compound clip at all. “

    That’s not completely true, because the project still retains links to the compound even though it is broken apart. For example, if you duplicate the “broken apart” project with the option to create a new (consolidated) event, the compound is also copied as part of this process. Even though it is technically no longer a part of the project. This might be a bug, but it shows that some sort of “under the hood” links are retained.

    – Oliver

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

  • Bill Davis

    September 30, 2013 at 6:51 pm

    [Charlie Austin] ” I make lots of versions as I go along, and duplicating in the Project Library for versioning is what I do now FWIW…”

    I do this as well.

    I keep in my mind always the idea of metadata FLOW in X.

    And as I work from my input material downstream toward my Porject Library – I try to “circle back” as little as possible – which is what making a compound clip functionally does. It expresses something from the Storyline back upstream to the Event Browser.

    I prefer to do my versioning in the Project Library since they represent alternate possible “finished states” rather than shelved assets that I have elected to preserve for later use (which is how I think of Compound Clips)

    FWIW

    Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

  • Dave Jenkins

    September 30, 2013 at 8:41 pm

    I also do my versioning within projects. It seems that’s how the program was designed so I think it’s best to use it the way it was designed in my opinion. FWIW

    Dajen Productions, Santa Barbara, CA
    MacPro 3.2GHz Quad Core – AJA Kona LHe+
    FCS 3 OS X 10.7.4
    FCP X, Logic Pro, Squeeze, Filemaker 10.8.3

  • James Ewart

    October 1, 2013 at 4:34 am

    Perhaps as a way of starting to round off this thread, the CC I was referring to which would not delete was, of course, due to pilot error.

    I had inadvertently created a CC from the timeline without selecting anything. The intention had been to create one in the Event Browser.

    It seems if you do this FCPX will create a CC with the individual clip closest to the playhead. I did not see that this one shot in the timeline had turned into a CC and successfully deleted the contents resulting in a black hole.

    Match Frame (sorry reveal in Event Browser) not possible as nothing to match

    Located the clip it came from and (thanks to PIOP) all is well again.

    It makes sense to me to keep versions within one project although I am in the habit of duplicating the project every day as a backup.

    No Autosave or Autosave Vault still makes me nervous.

  • Gretta wing Miller

    October 1, 2013 at 6:06 pm

    Not quite the end of the discussion, IMHO.
    I have been working on a feature doc with FCPX since March 2012, and developed some ignorant workflows. One of which seemed brilliant at the time, was to cut each ‘scene’ as a CC using the selects, so I did not have to go back hunting thru the Browser.
    Now at the end, cleaning up, I was deleting all those CCs in the Browser (they have been very useful), but some of them gave a warning that they were being used. I didn’t think so, but left those alone. As a test, I deleted one with that warning and sure enough, that scene, broken apart, reedited often, in a project which has been duplicated/versioned multiple times, showed up with missing media. Not every shot, because I think when I put in a new cutaway or VO shot they were clear of the CC. But most of the scene had missing media. I reproduced the cut easily enough, but I don’t know how to finally and fully break the connection between the CC and the project. Certainly Shift-CMD-G doesn’t do it.

    Downtown Dailies Service
    “I may have been born this morning,
    but I’ve been downtown all afternoon.”

  • James Ewart

    October 1, 2013 at 6:15 pm

    Yup…if you are using the CC in the timeline then DO NOT delete from the Event browser. That was EXACTLY what happened to me.

    Wiser minds here will explain why….

  • James Ewart

    March 30, 2014 at 9:21 am

    It’s back to haunt me. Three little compound clips in the browser which I cannot open or delete. No error message nut there is a little yellow triangle with an exclamation mark next to them.

    I have ben through all my sequences/projects and nothing there.

    Weird.

Page 2 of 2

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