Apple

Here's from in-house tester:

"

So bizarre ...

I set keyframes at 0, 50, 100.

I use <> to move to the last keyframe. It says frame 99 with a refFrame value of 100.

I use the keyboard -> to move to the next frame. It says frame 100 with a refFrame value of 100.

I use the keyboard <- to move back to frame 99. It now says frame 99 with a refFrame value of 50 !

Works fine in Motion.

"

Pierre

On 4/3/2015 1:07 PM, Eberhard Ammelt wrote:

Hello Pete,

I can confirm this problem for FCP X 10.1.4 as well but didn’t find a workaround. It seems that keyframes times and keyframe values may be changed. I have filed a bug report.

Regards, Eberhard

Hey all,

I'm working with FCP 10.1.4, and we are trying to internally set keyframes for our effect.

We notice that keyframe times might be one (or more) frames off. For example, on a 300 frame clip, we try to set a keyframe at time 50, and it shows up at time 49. When going through the keyframes (either via API or with UI in FCP), we get keyframe times can be off a frame or two.

I see this post from Eberhard Ammel from 2 years ago:

I'm trying to set and retrieve keyframes for a floating point slider parameter but experience some problems in FCP X 10.0.5-7

The other issue: When trying to navigate to these keyframes by pressing the previous/next keyframe buttons in the parameter panel, the play head does not always jump to the correct time but may be off by up to 4 frames.

Eberhard, did you every figure out a resolution to this problem?

Darrin, help?

Pete
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References:
	>FW: FCP X: Problems with FxKeyframeAPI (From: Peter Litwinowicz <email@hidden>)
	>Re: FCP X: Problems with FxKeyframeAPI (From: Eberhard Ammelt <email@hidden>)