has anyone encountered assigning range keywords to compound clips?

[Bill Davis]

Shane,

I’m not sure I’m following, and this could easily just be my work-deadened brain mis-interpreting things… but… in some of my working with others to try to help them understand the shift in the way FCP-X works compared to legacy software – one critical factor is the new way X divides up the editing interface and how working in one area relates to results in another.

Let me be clearer. In Legacy, you had a capture scratch where your basic digital data was stored – a bin where a “pointer copy” was placed to let you work with it – and a timeline where you were expected to arrange and edit your clips. It was a simple, “one directional” flow. Decisions you made in your timeline, were persistent, but nothing you did in the timeline really CHANGED anything in the Bins or in the Capture Scratch. So the edits “happened” in the timeline. Period.

X works differently. There’s a thing kinda sorta like the capture scratch buried in your Movies folder – that’s similar to in Legacy – clips there are never changed by editing operations. But the BIG difference in X is that instead of a single, passive set of BINS to import files into – there are TWO constructs that work very differently.

The first is the Event Library. All clips you “ingest” into X have to be linked to at least one Event Library. Clips can also be linked to multiple event libraries without penalty – since just as clips in the Capture Scratch in Legacy weren’t actually duplicated, but just referenced in your bins – clips in your Event Libraries are references to the originals.

Unlike legacy, meta-data (in this example anything from edit points to filter settings) can be attached to clips not just in the timeline, but in the Event Library as well. And one big difference is that decisions you make in the Event Library are persistent. If you make an editing decision designate and IN and OUT point for a clip in the EB – that attached meta-data (the edit decisions) will STAY attached to that clip no matter which project or event now – or in the future – it’s used by – or referenced from.

One thing you can do with Event Library clips is to put them in timelines. These timelines are reflected in a new X construct called the Project Library.

But while we often “shorthand” this as the “timeline” – it’s actually a quite a bit different than the “timeline” in Legacy. and one way it’s different is that it SHARES data with the clips in the Event Libraries that are linked to it. Legacy was a ONE WAY street. In X there’s a TWO WAY street. with decisions are always dynamically flowing from the Event Browser to the Timeline and back again. So it’s important WHERE you’re working when you make edit decisions. It determines whether that meta-data represented by your decisions is attached to the clip in the TIMELINE and therefore just exist for that timeline – or in the EVENT BROWSER where it persists for all timelines.

When you’re working with a COMPOUND CLIP – the workflow gets even more complex. Compounds can be formed in the Event Browser – but they can also be formed in the Timeline. And so decisions you make on a compound will have different “persistence” characteristics depending on where it lives.

Overall, stuff that happens in the Event Browser is “global” in that it is data that is maintained there to be used by all timelines and across all projects as needed.

But stuff that happens in the “timeline” is stuff that’s applied for that particular timeline only.

That’s fundamental new thinking in X. And *might* be part of the issue you’re having.

I would be suspect about editing decisions made to compound clip while it’s in a timeline. I’d be more comfortable about editing decisions made to a compound clip when it’s in the Event Browser – since my expectation is that EB decisions are persistent – while TL decisions are typically less so.

Or might be totally off-target if I’m simply misunderstanding the problems you’re having.

I’ll check back on Monday after I get some rest and see if this has clarified (or needlessly obscured) the answers you are seeking.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

[Shane Trowbridge]

Bill I REALLY appreciate you taking the time to break this down. I’ve actually read this through a few times and plan to read it a few times more to make sure I’m digesting it all.

Your comments about compound clips on the EB vs the “Timeline” make a lot of sense. oddly enoough, I created the compound clip in the EB so based on what you are saying I shouldn’t have had this issue.

The reality is I am still in the learning stage with X so it’s possible I made some small mistake that I overlooked though I’m not sure what that would be.

I’m on a deadline with this project that I have the issue on so I think I’m just going to McGyver it to get it done but I think I need to try and go back to see if I can recreate the problem.

Any other insight you have would be welcome. Thanks again!

Shane

[Bill Davis]

[Shane Trowbridge] “The reality is I am still in the learning stage with X so it’s possible I made some small mistake that I overlooked though I’m not sure what that would be.”

You and me both, brother. Even after six months and quite a bit of use, I’m still fuzzy on many concepts regarding X.

I fully expect to write stuff here and have others tell me I’m either partially or fully wrong. The hope is that if I keep the discussion going with my thinking, the “hive mind” will help us all figure out which are the solid ones and which are off base.

This is how I “see” X at this point.

I want to know how others see it as well – and may the most accurate understandings rise to the top and be the real influencers of the readers here.

Peace.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor