site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 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 (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... 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? This email sent to site_archiver@lists.apple.com