change name of clip in browser and ripple to project?

[James Cude]

You can edit the clip name by selecting it and then clicking on the Info tab in the Inspector. From there you can edit the name.

[Jason Brown]

this doesn’t ripple between the timeline and the browser…

[Jeremy Garchow]

I think this would be great, but not all the time. A right click behavior would be nice.

[Jason Brown]

so I’m guessing this is a no? 🙂

Feature request?

[Jeremy Garchow]

If its possible, I haven’t found it.

There’s good reasons to have it the way it is now, and good reasons to to have the option to ripple.

Now, you can match frame back to the Event, then replace in timeline. It’s a pain.

If anyone knows something different, please enlighten us, but the “name ripple” doesn’t seem possible at the moment.

Jeremy

[Tony Sarafoski]

Jeremy I recently experienced this same problem where after adding all the needed shots on my primary storyline, I realized I needed to change a few of the clips names.

Unfortunately I too was unpleasantly surprised this couldn’t be done, so now I try make sure I pre-plan and batch change the media names prior importing.

If its not a large batch, you can always change the clips name in the event browser, then highlighting the clip in your timeline, choose show in event browser, and do a replace insert.. I know it’s tedious, but unfortunately there arnt many choices right now.

[Bill Davis]

[Tony Sarafoski] ” I know it’s tedious, but unfortunately there arnt many choices right now.
“

For kinda good reasons.

X is built around a cascading metadata flow. Metadata attached to camera clips flow into the event browser, where it’s added to or amended by the user, then the metadata from this state flows into the Timeline clips.

It’s “one direction” by design.

That’s why changes you make in the event browser “stick” are become available for use in unlimited subsequent project – and when they hit THOSE timelines – you don’t want a change made at the end of the chain to “flow” back up to the event browser – and therefore to constantly change the default state of your EB clip.

If you allow every change in a clip on the timeline to reflect back to the source clip in the EB, then every time you go back to the EB, you couldn’t depend on the clip to be in a reliable state. It would instead be in the “last state” anyone applied in the timeline.

Imagine that in a world where multiple editors want to use a centrally stored clip… the clip is tinted blue now, but when you go to grab it three seconds later, it’s pink – because someone down stream changed the tint and it reflected back to the base clip in the EB.

That’s a nightmare.

X is metadata, metadata needs a clear flow – particularly in a relational database where everything remains virtually linked to everything else.

Same old story. If you try to approach how X works exclusively by how thinking has been conditioned by how other NLES used to work – you’re going to be fighting things a LOT more than you need to.

FWIW.

“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

[Tony Sarafoski]

Bill I totally understand and respect what Apple have done, and I’m not trying to change the intended workflow for FCPX.

It was a very unusual circumstance needing to change the clips in my timeline, and easily did so by manually renaming. My problem was in a perfect scenario (and it’s not always perfect), I’d just rename my clips (with Adobe Bridge) prior importing into FCPX. But what if an edit changes course and filenames need changing, and the timeline has already been built…! one would hate to be in FCPX 🙁

Anyway I’m not arguing my point, just saying what if….?

[Bill Davis]

[Tony Sarafoski] “the timeline has already been built…! one would hate to be in FCPX 🙁

Anyway I’m not arguing my point, just saying what if….?

“

I think as we all develop our chops, we’re going to see that the kind of thing you’re looking for is pretty easy via XML implementation.

In the same way Phil Hodgets Event Manager used XML to “hide or show” events within X, I’d almost bet that useful “clip name management” tools will eventually come out that have the same friendly front-end applied to the process.

I am a bit concerned that in a relational database where everything is interconnected, even something as seemingly trivial as re-naming a clip can have reasonably complex consequences. ID info has to be updated not only at the clip level, but across all instanced where that clip might be referenced inside the database.

If, for example, you’re using a company logo that you’ve used across a dozen projects – a change to the name of that asset might have to be “managed” across a wide range of projects, shared files, and links.

I’m just not informed enough about the underpinnings of the X database to know if that’s pretty simple, or numbingly complex.

Always more to learn here…. ; )

“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

[Jeremy Garchow]

[Bill Davis] “I am a bit concerned that in a relational database where everything is interconnected, even something as seemingly trivial as re-naming a clip can have reasonably complex consequences. ID info has to be updated not only at the clip level, but across all instanced where that clip might be referenced inside the database.”

it would be really easy. You could right click on clips in a timeline and choose “Match name in Event” or vice versa. It wouldn’t have to ripple through the whole entire database (like it does now in FCP7 for the most part), just what you select, just like you can rename any clip at any time anywhere, and it won’t lose the relationship in FCPX. Basically, it’s a metadata sync you just need to tell what data to use. “No big deal”!

Remember when you didn’t think relink was possible?

Jeremy