Re: FCPX parameterChanged crash
Re: FCPX parameterChanged crash
- Subject: Re: FCPX parameterChanged crash
- From: Paul Schneider <email@hidden>
- Date: Sat, 7 Jan 2012 11:55:26 -0800
Hi Paul,
There's a bug in FCPX which will cause this crash when an FxPlug changes parameter 63, and only parameter 63. It should be fixed in an upcoming update. If you need to work around it, avoiding ID 63 should do the trick. This is radar 10504317 if you need to check on the status in the future.
- Paul
On Jan 7, 2012, at 9:51 AM, Paul Miller wrote:
> I have an effect with about a hundred parameters (works fine in Motion), but only two of them are published in my .moef. One of the parameters is a checkbox, that when clicked, causes parameterChanged: to get called.
>
> The first thing I do is turn the checkbox back off (it acts as a button). Then I launch a separate application with my custom UI and wait for it to exit. Then I call CustomParamAPI->startAction:self and start setting all the parameter values from values returned by my external application, using the FxParameterSettingAPI_v2.
>
> It gets to paramID 63 and then crashes way down in setFloatValue, in a bunch of notification code which ends up calling "FFMotionEffect channelParameterChanged:".
>
> I've been able to successfully update a single parameter this way, but not for this effect.
>
> Is there a limit on the number of parameter ids (mine start at 1 and go up from there)? Anything else that would prevent this from working?
>
> Darrin - can I send you the plugin to try?
> _______________________________________________
> 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