Workflow issues with Compound Clips in 10.0.6

Hi!

I used to use Compound Clips to make versions of my edits:

1) Select All in the timeline
2) create a Compound Clip by OPT-G
3) Duplicate that clip as Audition.

Prior to 10.0.6, if I made changes in one Audition Pick (version of the clip), the original Audition Pick would stay the same, not changing - perfect for trying out various versions of the edit, or, say, making different cuts for different languages/networks.

In 10.0.6, whenever I make a change in one Pick, all other Picks do reflect this change, effectively nullifying any reason to use Audition for versioning of edits.

I guess I can Duplicate Compound Clips in Event browser, but it's much more cumbersome. I'm sure the new approach in 10.0.6 has tremendous advantages, but this workflow was very efficient and now it doesn't work.

Any tips to make this work as it used to do? Thanks!

It is a different workflow, but just as easy. Here's what you're missing.

Make your first CC an Audition just like you have been doing. The thing is, drop a new copy of that CC from the Browser into the Timeline, then go to Clip menu, and chose "Reference New Parent Clip". This creates a new independent "parent" in the Browser which the new clip will reference.

Yes, new mechanics under the hood in 10.0.6.

There should have been a big honking warning concerning this, as I'm sure I have unintentionally changed Auditioned CCs that shouldn't have been changed (when doing different cuts for different language versions of my projects).

There was, Apple mentioned all of the new features when the upgrade came on line.

But I also think auditions is not the workflow you should be using. For different languages, use Roles.
www.macprovideo.com/hub/final-cut/introducing-roles-in-fcp-x

I too have been using CC's to create different versions of a "sequence." But I don't duplicate to audition. I noticed that if you do it that way, the dupe doesn't appear in the event browser. I select the CC in the timeline, then go to Clip -> Reference New Parent Clip. This creates a dupe in the timeline and the event browser. I can then add the new clip to an audition if I want to cycle through them.

Ben, why don't you think this is a good strategy? I don't see how roles can be used to create various versions of a timeline.

You said "different languages, and when I do this I use roles. All I'm doing is assigning custom roles as languages to various overdub, music, and title clips. Then in the Timeline index I can turn off or on any specific language group. I can also export only what groups I want.

But if you're doing whole different edits, that goes beyond Roles. You may want to work with Project timelines, and duplicate them for each language.

Again, I'm guessing as to what your specific needs are. If you give some details about what you're doing and your goal?

BenB, I know and use Roles. The thing is, these edits varied slightly in lenght and content. Instead of having X separate projects, I used Auditions and Compound Clips to have several versions within one Project. That is not possible, or is very cumbersome now.

See this video for clarification on ways to use the new compound clip features in 10.0.6.

www.fcp.co/final-cut-pro/tutorials/984-i...nal-cut-pro-x-10-0-6

Stooovie wrote: BenB, I know and use Roles. The thing is, these edits varied slightly in lenght and content. Instead of having X separate projects, I used Auditions and Compound Clips to have several versions within one Project. That is not possible, or is very cumbersome now.

I'd just do the reference new parent thing with the copy in the audition... seems fairly simple unless I'm missing something...

Why not just duplicate the project to make a different version? That's all I do.
Make a folder in the projects directory and put your projects for that job in there.

Edit 1 v1, v2 etc. works perfectly.

The problem with this method is that if you duplicate a project with compound clips, then change those compound clips, it changes the clips in the original projects too. That's how CC's work in 10.0.6 now. You have to dupe the CCs if you want to make changes to them in subsequent versions w/o changing them in the original projects.

I understand that, but the original idea was to create compound clips to make different versions of edits. I was just asking why not just duplicate the project instead?

But yes if there are compound clips in there then you will need to either break them apart or use the clip menu to isolate it.

I have mixed feelings about this new way of treating compound clips. In some cases it could be brilliant but MOST of the time I think I'd prefer compound clips to become independent once they are edited into a project.

Duplicating projects gets unwieldy pretty quickly. For this particular project, I have 22 timelines with 5 language versions each. Even with SSD, FCPX goes nuts with this many projects online. It just loads too slowly (main Event with 11000 clips doesn't help either - unfortunately, I need to be able to access all of them all the time, so splitting to several Events is not an option).

Using Auditions and CCs was a useful way to keep things neat and tidy. I will try the Reference New Parent thing.

Seanus wrote: I have mixed feelings about this new way of treating compound clips. In some cases it could be brilliant but MOST of the time I think I'd prefer compound clips to become independent once they are edited into a project.

I agree with you. Intuitively you expect CCs to behave independently once you duplicate a project. On the other hand, I could see it being helpful if you had a CC you wanted to use across multiple projects, keeping each project updated as you updated a CC. So I can see where the Apple designers are going with it.

What they really need is to create some kind of versioning tool. Since they have done away with the old FCP's sequences, it would be nice if they created some way to create different versions without having to create new projects, which all have to load separately. Maybe that was one of their thoughts behind audition clips.

plysat wrote: I'd just do the reference new parent thing with the copy in the audition... seems fairly simple unless I'm missing something...

Yep, quick, easy, simple, what more could you want? Best of both worlds.

Yep, I will do that. Kinda cumbersome, but never mind. Tx!