Applying a speed change to a clip after online...HELP!

[Nick Gallegos]

So, I have a large project where the editor decided to go speed change happy with a few clips. After a LOT of trial and error leading to total frustration, I'm completely stumped.

I onlined a reel of footage that ran through Crimson Workflow and Redcine for one-light. Since this reel contains a few speed change clips AND I've come to find out that this (nor keyframing, which there's also a lot of) doesn't play nice with Crimson, I removed the speed changes and keyframing from all the clips on a separate sequence before exporting out the XML from FCP.

Okay, so everything goes fine through the workflow and round trips to FCP with pretty color corrected footage. Score! The clips that had speed change (in this case, constant rate fast motion) naturally got extended because the effect is no longer present. However, when I try to manually apply the proper speed changes, FCP spits out the following error:

"Unable to complete command. A conflict occurred during a trim operation." Sure, whatever the heck that means...

So, then I tried something a bit different. Totally bypassing Crimson, I grabbed the source clip in its entirety and ran it through Redcine to apply the same color settings and rendered the clip (1 hour, 30 minutes to do this render...sigh.). When it was finished, I dragged it into the timeline, trimmed it to match the original edit and tried manually applying a speed change again. Exact same error!

Everything renders out from Redcine in ProRes 422 HQ at 2K 2:1, BTW.

It almost seems as though Redcine is doing something somewhere before I render because if I drag a 2K proxy of that same clip to the timeline, I can apply speed changes just fine. What gives? :ranting2:

Am I doing anything wrong? Onlining this project has become a huge, unprofitable nightmare.

Thanks in advance for any help!

 

[Scott Simmons]

This error is occurring because when you are applying the speed change back in the online FCP is having to shift the edit to apply the speed change. It has nothing to do with RED or REDcine. Move the clip to the end of the timeline and apply the speed change and then move it back into its hole and adjust accordingly.

 

[Snow R. Shai]

More options for speed changes

More options for speed changes

I believe editblog is right.
This should be an FCP issue only.
Did his suggestion work for ya?
if so, a few more options for speed changes in a sequence:
1. move your shot to a new layer, and lock all video and audio channels.
make your speed change, then trim the shot to fit it's original position and move it back.
2. Move your playhead to your shot in the sequence. press F to load the master file into the viewer. Make your speed change. Mark I/O points in the timeline [x] for your shot position, then overwrite.
Important: when using this method, you are changing the master clip's speed.

 

[Craig Swanson]

I'm doing a project now that has lots of speed changes. knowing this ahead of time I exported a timeline to redcine with my shots having lots of pad. Once back in FCP I exported my shots I needed to change speed to motion. Did the variable change with behaviors and it was embedded fine in fcp.

The reason I didn't use the fcp editor for variable speed changes is I just can't figure the darn thing out. coming from Avid's timewarp function, time remap in fcp is not friendly to me.

Speaking of not being friendly is the fact that any projects with speed changes will screw up your online.

Craig

 

[Nick Gallegos]

Thanks a million for the help, guys!

I finally got it to work by moving the clip to the tail-end of the timeline. What's really bizarre though is that FCP doesn't care if I apply this time change on the offline timeline when the clip is where it's supposed to be. Really strange. It even complains if the clip is on a completely different track.

I really thought I was going crazy and it ended being relatively simple. Thanks again!