June 2011 - Pro-apps-dev - lists.apple.com

Re: Publishing parameters for FCP X
by Darrin Cardani 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jun 30, 2011, at 11:29 AM, Christoph Vonrhein wrote: > Hi Darrin, > > While I have now converted my FxPlug plugins to work perfectly with Motion 5, I was trying to create the FCP X templates. There is a big problem: I can't publish "Image wells" and published custom parameters don't work with FCP X. > > Am I correctly seeing this that I can ONLY publish checkboxes, sliders and popup menus? No Image wells and no custom parameters? No. You can only create rigs that have checkboxes, sliders, and popup menus. You can publish most other parameters (angles, color wells, etc.). For image wells, you con't publish them directly. Instead what you need to do is create a drop zone in your project (I believe it can be disabled and this will still work), and drop the drop zone into the image well. Drop zones are automatically published. It's a little roundabout, but seems to do the job. > Am I seeing this correctly that FCP X has no native plugin interface included at all? No FxPlug, no FX-Script, no AE plugin import and no way to simply drop a Quartz Composer file into the timeline? > > Do we completely rely on Motion templates with published checkboxes, sliders and popup menus to create an effect for FCP X? FCP X's plug-in support right now is entirely through Motion Templates. As mentioned above you can publish angle parameters, drop zones that are image wells, color wells, etc. Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Publishing parameters for FCP X
by Christoph Vonrhein 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)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(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… While I have now converted my FxPlug plugins to work perfectly with Motion 5, I was trying to create the FCP X templates. There is a big problem: I can't publish "Image wells" and published custom parameters don't work with FCP X. Am I correctly seeing this that I can ONLY publish checkboxes, sliders and popup menus? No Image wells and no custom parameters? Am I seeing this correctly that FCP X has no native plugin interface included at all? No FxPlug, no FX-Script, no AE plugin import and no way to simply drop a Quartz Composer file into the timeline? Do we completely rely on Motion templates with published checkboxes, sliders and popup menus to create an effect for FCP X? This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug 2 Parameter IDs
by Paul Miller 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 Are parameter ids 4 bytes now or are they still short ints? Do the ids have to be below a certain value like in the old SDK? Parameter ids are UInt32s, and always have been, with the caveat that Motion restricts them to be less than 10,000. Moving to 64-bits would have changed a lot of method signatures, and it didn't seem worth the hassle since nobody should have more than 4 billion parameters (and you can't currently have even that many). The number 10,000 is a limitation that we should get rid of, but I don't know how easy that would be to do. Please file a bug if this is important to you. I was only joking. :-) _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… On 6/30/2011 11:01 AM, Julian Vasilkoski wrote: Now that it's all 64 bit I would hope they'd be uint64s. I'm working on a couple of plugins with more than 64000 parameters and could really use the expanded id space. If you really have the need for 64,000 parameters, I'm guessing that maybe the new dynamic parameter API would be helpful to you. It allows you to add and remove parameters outside of the -addParameters method. This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug 2 Parameter IDs
by Darrin Cardani 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jun 30, 2011, at 9:11 AM, Paul Miller wrote: > On 6/30/2011 11:01 AM, Julian Vasilkoski wrote: >> Are parameter ids 4 bytes now or are they still short ints? Do the ids >> have to be below a certain value like in the old SDK? > > Now that it's all 64 bit I would hope they'd be uint64s. I'm working on a couple of plugins with more than 64000 parameters and could really use the expanded id space. Parameter ids are UInt32s, and always have been, with the caveat that Motion restricts them to be less than 10,000. Moving to 64-bits would have changed a lot of method signatures, and it didn't seem worth the hassle since nobody should have more than 4 billion parameters (and you can't currently have even that many). The number 10,000 is a limitation that we should get rid of, but I don't know how easy that would be to do. Please file a bug if this is important to you. If you really have the need for 64,000 parameters, I'm guessing that maybe the new dynamic parameter API would be helpful to you. It allows you to add and remove parameters outside of the -addParameters method. Thanks, Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug 2 Parameter IDs
by Paul Schneider 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi all, Parameter ID's have always been UInt32's, and remain UInt32's. Historically, Motion has imposed a range of [1..9998] for plugin parameter ID's. This limitation appears to still be present in Motion 5. - Paul On Jun 30, 2011, at 11:11 AM, Paul Miller wrote: > On 6/30/2011 11:01 AM, Julian Vasilkoski wrote: >> Are parameter ids 4 bytes now or are they still short ints? Do the ids >> have to be below a certain value like in the old SDK? > > Now that it's all 64 bit I would hope they'd be uint64s. I'm working on a couple of plugins with more than 64000 parameters and could really use the expanded id space. > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/pschneider%40apple.com > > This email sent to pschneider(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug 2 Parameter IDs
by Paul Miller 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 Are parameter ids 4 bytes now or are they still short ints? Do the ids have to be below a certain value like in the old SDK? On 6/30/2011 11:01 AM, Julian Vasilkoski wrote: Now that it's all 64 bit I would hope they'd be uint64s. I'm working on a couple of plugins with more than 64000 parameters and could really use the expanded id space. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

FxPlug 2 Parameter IDs
by Julian Vasilkoski 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 64-bit / 32-bit "mixed"
by Darrin Cardani 30 Jun '11

30 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com On Jun 29, 2011, at 4:54 PM, Christoph Vonrhein wrote: > Hi Darrin, > >>> 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. Well, it's even worse in this case because Motion can't load any code in the situation you're talking about - if you have a 64-bit plug-in, Motion 4 won't be able to load any code, and if you have a 32-bit plug-in, Motion 5 won't be able to load any of its code. So you probably need a stub for each case. > >>> 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? There's a "DynRegFxPlug" code example that shows how it works. Plug-ins with dynamic registration should be loaded at startup (or maybe when the user first tries to apply a filter), and the app will call some code to find out how many plug-ins they have and what the plug-ins are. In those methods, you can tell the app that you have no plug-ins if running in 32-bit mode, and just return the appropriate info from your plist in 64-bit mode. (Or the reverse for older host apps.) Darrin -- Darrin Cardani dcardani(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0

Re: 64-bit / 32-bit "mixed"
by Christoph Vonrhein 29 Jun '11

29 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)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(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… 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(a)lists.apple.com

1 0

Re: 64-bit / 32-bit "mixed"
by Garrick Meeker 29 Jun '11

29 Jun '11

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com When you lipo a universal build, the 32-bit and 64-bit sides can link against different frameworks and compile with different headers. The other architectures are not accessed when loading. I think the only reason to separate them is if you need different plists or resources. On Jun 29, 2011, at 2:40 PM, Darrin Cardani wrote: > > On Jun 29, 2011, at 12:02 PM, Christoph Vonrhein wrote: > >> 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. > >> 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. > > Darrin > -- > Darrin Cardani > dcardani(a)apple.com > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digitalanarch… > > This email sent to garrick(a)digitalanarchy.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a… This email sent to site_archiver(a)lists.apple.com

1 0