It looks like all the parameter get/set calls as well as the keyframe calls are mismatched (at least from parameterChanged). Image checkouts use the current frame. I put together a sample that makes this easy to reproduce, as well as the image checkout issues (8-bit only in parameterChanged, upside down in FCP X). I've filed two bugs, but it's the same sample. Click on the checkbox and you'll get a bunch of NSLog calls, and the behavior is different in FCP X from Motion. If the image is 8-bit, you'll get a message. You can compare the pixel values at (0,0) against the logged value from renderOutput. To make sure the correct image is retrieved, use a clip with a cut or obvious change at (0,0) and move to the first frame of the cut. Image checkout during parameterChanged: Bug ID# 11322252 Parameter and keyframe mismatch: Bug ID# 11322373 Let me know if you need more information. On Apr 25, 2012, at 9:17 AM, Darrin Cardani wrote:
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 (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com
This email sent to dcardani@apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com