site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Darrin, Christoph _______________________________________________ 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... Is there a way to compile a 32-bit FxPlug that does not to appear in Motion 5? Interesting question. They shouldn't be showing up already, but it appears they are. Please file a bug on that. Motion does not call any methods of a FxPlug plugins when it starts up. If it would, then it would be very easy. And also: Is there a way to compile a 64-bit FxPlug that does not appear in Motion 2-4? I don't want to create 32/64 mixed plugins, because I want to take advantage of the new 2.0 features and because of the complications that there are if I want to compile two different FxPlug frameworks into one plugin. One solution would be to use dynamic registration. When being loaded, you can check the host version number and not return any plug-ins if you're in the wrong host. I did not use dynamic registration at all so far. Is there a example code or a some kind of a description somewhere of this feature? My current plan is to compile a separate 32-bit and 64-bit version of my plugins. The 32-bit version should only show up in Motion 2-4 and the 64-bit version only in Motion 5. I don't want to create "universal" 32/64-bit plugin, because I want to use the new features of the 2.0 SDK (like the dynamic creation of parameters and such) in the new plugins. I already compiled the two versions, but so far both show up in all versions of Motion's effects list, regardless of the architecture. This email sent to site_archiver@lists.apple.com