Forum Replies Created

Page 4 of 4
  • This issue came up a few weeks ago. See this thread: https://forums.creativecow.net/thread/344/15302
    When duplicating any project which has compound clips, you must remember to choose “duplicate project and used clips” and under that “multicam and compound clips only”.

  • Great to hear that!

  • Yes, this is a quite ridiculous new behavior of 10.0.6. When duplicating any project which has compound clips, if one selects “duplicate project only” (the normal option) then only the “upper layer” of the project is duplicated, since anything within a compound clip is not. Why one would want to duplicate only the “upper layer” of a project is beyond me. Instead, you will almost always want to choose “duplicate project and used clips” and under that “multicam and compound clips only”. FCPX will then create a new event with new unique compound clips and will copy no media, as you would normally expect. But there is a bug: if there is not enough space on the drive to physically duplicate all of the used media (even thought that is not at all what you want to do) then final cut simply refuses to duplicate! And another bug: if after duplicating a project as shown above, you try duplicating the resulting event (which is composed of just compound clips and contains no media iself since it only references media on other events), then final cut insist in physically duplicating all referenced media to the new event. This all makes collaborating with another editor extremely difficult. You are forced to keep sharing both a project and an event each time you want to echange versions of a project and even doing that takes a lot of work!

    On the other hand, I you are duplicating project to try out differend edits, then I recommend a different workflow: If, say, you want to try out a diffenrent edit of a scene, then make a compound clip out of the scene, then duplicate the compound clip by making it “reference a new parent clip” and use auditions to group the different versions where they “belong” in the project. That way when you revisit the project in the future you will not have to go through different versions of the entire project comparing them and wondering what you changed and where. You can just cycle through different versions of different scenes where they belong and the entire timeline ripples accordingly. Even the render files of different rendered versions are retained! This is one of the best and least documented features of FCPX in my opinion.

Page 4 of 4

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