Re: FCP X parameterChanged bug?
Re: FCP X parameterChanged bug?
- Subject: Re: FCP X parameterChanged bug?
- From: Darrin Cardani <email@hidden>
- Date: Wed, 25 Apr 2012 09:17:32 -0700
Garrick,
I'll have to investigate more to figure out whether it's a bug or not, but please file a Radar anyway, as clearly it needs to be better documented.
Darrin
On Apr 24, 2012, at 1:34 PM, Garrick Meeker wrote:
> I'm not sure if this is a bug or if I'm using the API incorrectly. This works in Motion but not FCP 10.0.4. In parameterChanged, I call startAction, startUndoGroup, and currentTime. Then I call:
>
> FxKeyframeInfo info;
> FxInitKeyframeInfo(info);
> info.time = t;
> info.style = kFxKeyframeStyle_Linear;
> [_keyframeAPI addKeyframe:info
> toParam:parmId
> andChannel:chan];
>
> for chan in channelCount, followed by setFloatValue. The values and keyframes are changed on the PREVIOUS frame. If I'm at frame 60, the keyframes and value changes happen at 59 (but hasKeyframe will still report that there's a keyframe at 60).
>
> Is currentTime (and renderOutput) starting at 1 but the parameter and keyframe API's expect to start at 0? It seems like that's the case, but I'd like to get confirmation before I file a bug.
>
>
> _______________________________________________
> 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
_______________________________________________
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