[Randall Wurster]

Thanks Andrew – that’s helpful. Good point about fair use not preventing legal action, justified or not.

[Randall Wurster]

FOLLOW UP: So, it actually has to do with the “optimize stills” checkbox it seems. I checked that when I was getting glitchy frames rendering out stills in the sequences.

Unfortunately, I need that box checked as I have many stills in the project. But at least now I know what the problem is and get what that checkbox is doing.

[Randall Wurster]

Thanks for the pointer on the compound clip.

I’m not sure why I had the inconsistent behavior before, but if I replicate it, I will hopefully have learned something and update my post.

[Randall Wurster]

I must’ve been doing something wrong…it is working now as I test it out with a different file.

Not sure what was going on before, but relieved to see that is not the behavior.

[Randall Wurster]

I have tried relinking in the event, and it hasn’t been updating in the sequence…that behavior is not expected, then I take it…

[Randall Wurster]

[Darren Roark] “The one advantage I have found is that I no longer accidentally relink to the wrong version of a GFX element. When the client keeps changing things fast and furious, it a good safeguard. “

We’ll have to agree to disagree there. This is far more dangerous to me. In FCP7, if a client wanted to change a lower third that was in a given show twelve times, I would just replace the file being used in FCP7. Done. Nothing dangerous about it. Updated in all twelve places.

Now, would I really have to go in and replace all instances of that lower third? That seems far more likely to yield mistakes. Not to mention it’s a time-killer.

It’s nice this isn’t an issue with AfterFX (have not taken advantage of the roundtripping there, so can’t speak to it, but thanks for the heads up on the potential issue there) but there are plenty of other programs we all use for GFX for FCP. So this will be a huge pain in the rear.

Agree they badly need a “replace footage” feature. Granted, the larger issue is that the entire folder structure and media management they’ve implemented for FCPX is completely asinine. It’s maddening that they assume we can’t keep track of our own media and assets.

[Randall Wurster]

This happens to me, and it also drives me nuts. Glad to know it’s actually a bug – that has to be fixed in the next release.

[Randall Wurster]

I just got burnt doing this myself.

Either I’m not getting something (I hope) or “Open in timeline” is really potentially a nightmare.

Am I understanding this right…

I’ve been editing exclusively in multiclip in X to this point, and when I would open a clip in the Multicam editor, I was able to make changes at that level that affected all instances of that clip at the higher “Project” [I think of it as sequence] level. I thought this was extremely powerful and a huge timesaver. It let me make a rough color correction and audio EQ at the start of editing which allowed me to make more informed edits before doing final fine tuning once it was cut.

I figured Open in timeline worked in a similar manner. Clearly, I was mistaken. Let’s say you put a clip on a track, open in timeline once, add a filter, cut that track into 100 clips – you now have 100 separate instances of that clip with an associated filter and you have no way of batch removing or pasting that effect should you want to change it, as they are all one layer deep. Is this correct?

I’ve spent all day fixing one such mess – the good news is I’ll never make that mistake again. The bad news is what could’ve been a powerful feature (open in timeline) is leaving me scratching my head as to why on earth I would ever find it useful.

FCPX continues to drive me nuts. The performance of it is generally so fast I can’t stop using it, yet at least once per project I hit something in the program that I find infuriating. If only Apple could release an NLE with this performance that was designed for video editors, not the generic Apple user.

[Randall Wurster]

Thanks for the reply – multicam is the issue, as far as I can see, you cannot “detach audio” – its always greyed out for me (if anyone has experienced otherwise, please let me know!)

I’ll continue to give X the benefit of the doubt as I work with it more. It’s too fast not to use when applicable. Especially at the start (import, log, sync, multi cam) and end (render, compress) of a project. Plus, a bulk of the things that drove me crazy before have either been addressed with recent updates, or have some sort of workaround.

[Randall Wurster]

And as an FYI, the workaround I settled on for the above problem was placing a gap into the timeline, dragging the character B clip up as a “connected clip” to that gap, then dragging it back over the footage.

Not only is this one of the silliest things I’ve had to do in the program yet, it’s also ugly looking, and ironically probably much more likely to lead to mistakes than all the goddamn safety features X has in there to prevent you from breaking sync or doing something bad.