site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi, Steve, that sounds like something that a lot of people do. It should work. Thanks, - Paul On Feb 27, 2008, at 8:08 PM, Steve Christensen wrote: steve _______________________________________________ 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/pschneider%40apple.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: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... When the user changes the value, the plugin sets the values of a number of other parameters based on a set of values associated with the particular preset. We had some issues with setting point control values in earlier versions of Final Cut, but they should be fixed now. And I haven't seen anything where setting the value works in -parameterChanged, but then gets undone before -renderOutput. Can you send me the source for your small test generator? I'll see if I can figure out what's going on. I have a plugin that has a popup parameter to specify presets. When the user changes the value, the plugin sets the values of a number of other parameters based on a set of values associated with the particular preset. What I'm finding is that with a point parameter, the x- and y-value are not always updated correctly, but only in FCP/ FCE, not Motion. Also, other types of parameters seem to behave correctly in all three applications. All of the parameters are added with flags set to kFxParameterFlag_NOT_ANIMATABLE, so the values should be constant across an entire timeframe of the effect. Hoping to narrow down the problem, I wrote a small test generator plugin that just has a popup parameter and a point parameter. I dumped out the values in -parameterChanged: and -renderOutput: and found that the values had changed along the way. I also noticed that the UI was not reflecting the updated values either, in this case. Final Cut Express[6339] ### parameterChanged @ 0.000000: x was 0.500000, should be 1.000000, is 1.000000 Final Cut Express[6339] ### parameterChanged @ 0.000000: y was 0.500000, should be 0.500000, is 0.500000 Final Cut Express[6339] ----------------- Final Cut Express[6339] ### renderOutput @ 0.000000: x should be 1.000000, is 0.000000 Final Cut Express[6339] ### renderOutput @ 0.000000: y should be 0.500000, is 0.500000 I can accept that I'm doing something weird, but I don't know where to look. Does anybody have some ideas? This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com