Auditions and Compound Clips

[James Ewart]

Which still begs the question what is the thinking of the software designers behind creating empty CCs in the browser and creating CCs in the Browser?

[Bill Davis]

The singular feature of Compound Clips is that they bundle assets together AND they reflect the new compound back upstream into the Event Browser.

It’s the perfect container for RE-USABLE elements such as title sequences and design items that you’ll want to change globally across multiple projects.

Combined with the Reference New Parent Clip capability, it allows you to either maintain or interrupt metadata flow (primarily text changes) into the compounds across projects or inside individual projects.

Does that help?

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.

[Bret Williams]

Why? It’s an option. I’m guessing you don’t do a lot of AE work, where you’re composing complicated effects. If you know a stack of 8 layers is going to be cc’d, why not build it as a clean slate instead of in the timeline where your other 10 layers are just getting in the way and bogging things down? You’ll certainly get more rt working in the cc vs the full project.

But I’m just thinking these things up as I go along. It certainly shouldn’t boggle anyone’s mind why it’s a nice option to have. Use it if you want or need it. Don’t if you don’t. I for one can’t stand auditions and rarely use them. I prefer to see my choices laid out in the timeline and I just turn clips on/off. I certainly can’t see why anyone would want to create them in the browser. But I accept the fact that they’re useful to someone’s workflow.

Check out auditions in resolve. They open up like a stack. A little sequence in the sequence. That app has all the right things going for it when they eventually marry it with some generators/transitions/effects and an effects app.

[Robin S. kurz]

[Bret Williams] “I for one can’t stand auditions and rarely use them. I prefer to see my choices laid out in the timeline and I just turn clips on/off.”

I’m guessing you don’t do a lot (or any) narrative work? Where you have-as I described-endless takes of the same thing where you’re looking for the right nuance in context. Using the REPLACE feature instead is what would be absolutely mind bogglingly tedious.

But yes, they’re both great options to have, when and if you need them. Which is why I’ll go out a limb and say is why they’re even there. 😉

[Bret Williams] “Check out auditions in resolve.”

It’s actually called “Take Selector” and I don’t see how it’s any better than in FCP. Have you actually *used* it? And something tells me they didn’t exactly come up with that all on their own, so I guess they must actually be useful after all. 😀 (actually I think the only exist in Resolve to heighten its compatibility with FCP X)

[James Ewart]

“it certainly shouldn’t boggle anyone’s mind why it’s a nice option to have.”

Yes sometimes I do get a bit boggled/curious really though. Wonder if I’m missing out on something because I always build CCs in a project/timeline.

[Craig Alan]

Robin, I thought that if you made a compound in the timeline that a copy is saved in the browser.

Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.

[James Ewart]

I thought that if you made a compound in the timeline that a copy is saved in the browser.

It is.

[Andy Neil]

[James Ewart] “Yes sometimes I do get a bit boggled/curious really though. Wonder if I’m missing out on something because I always build CCs in a project/timeline.”

It’s fine to do that and if that’s all you need compounds for, then great. The additional functionality might not ever be necessary for you. Personally, I rarely use compounds, but I’ll give you a couple reasons why you might like to have them in the browser as opposed to only in the project.

1) Combining broll. These days, tapeless cameras split clips whenever the camera is turned off. This can lead to having tons of short clips. Sometimes I’ll grab all the related broll and throw it into a single connected clip and then I can scrub one clip for all the footage I need rather than have to sift through dozens of clips looking for a shot.

2) Browser compounds can be moved to other events, and even other libraries.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[James Ewart]

1) Combining broll. These days, tapeless cameras split clips whenever the camera is turned off. This can lead to having tons of short clips. Sometimes I’ll grab all the related broll and throw it into a single connected clip and then I can scrub one clip for all the footage I need rather than have to sift through dozens of clips looking for a shot.

Thanks for that. That seems a very sensible workflow I like it.

[Robin S. kurz]

[Andy Neil] “Browser compounds can be moved to other events, and even other libraries.”

I don’t actually know of NON-browser (i.e. event) compounds.