Retiming bug - results in freeze frame

For a while now, whenever I try to retime a range in a clip, instead of retiming it just gives me a freeze frame. Has anyone else experienced this?

Demonstration of the problem: vimeo.com/73013659

You need to give complete specifications of your media and your project properties.

So, I go to lookup that information (which I should have included in the first place, my apologies) and it dawned on me... The footage was shot at 23.98fps AVCHD (optimized to ProRes by FCP) and I am editing in a 29.97fps project. Apparently, FCP X does not like retiming ranges in footage that has a different frame rate from the project. What I've been doing is conforming the footage to the 29.97 fps and then attempting to do my range retiming from there. Unfortunately, that appears not to be doable currently in FCP X.

I just did a test with the footage in a 23.98 project and it works fine. This is actually kind of frustrating.

Thank you, Tom, for responding, even though I hadn't given you enough information. Your reminder got me thinking more about a potential media/project settings mismatch.

brazzam: What I've been doing is conforming the footage to the 29.97 fps and then attempting to do my range retiming from there. Unfortunately, that appears not to be doable currently in FCP X.

Hi Alan,

FCPX does not have any issue with this. Same as you I have dropped some 23.98 fps footage into a 29.97 fps timeline and I can perfectly retime any range inside this footage. Even after conforming the speed of the footage the retiming still works as it should. I have made a little video of this test, if you want you can download it here: we.tl/9InVSnRfoK

- Ronny

I've had this problem too. Very frustrating. It only seemed to do it on certain types of formats, mainly AVCHD. What seemed to do the trick for me was changing my timeline to 29.97i instead of 29.97p. Haven't had the problem since. Weird bug though.

Hi Adam,

Thank you for reporting this. I'm going to look into it, but it would not really surprise me as native AVCHD is a very lousy format for editing.

In case of the OP however, the footage had been converted to ProRes. So that cannot have been the issue.

- Ronny