Re: FxPlug versioning
Re: FxPlug versioning
- Subject: Re: FxPlug versioning
- From: Darrin Cardani <email@hidden>
- Date: Thu, 28 Mar 2013 09:56:44 -0700
On Mar 28, 2013, at 8:11 AM, Christoph Vonrhein < email@hidden> wrote: Hello Martin,
I've also ran into this issue you are experiencing.
- Changed ProPlugPluginList version to "2"
This approach works for me with Motion and FCP 7 ( and older ). It also does not work for me with FCP X.
We use it extensively for our internal plug-ins with FCPX and it works well for us. Maybe you can tell us what you're having problems with and we can suggest ways to make it work? - Added a hidden "Upgraded1to2" bool parameter
The problem is that the new version of the plugin adds the Bool parameter to the V1 project and so you will always wind up with V2. It might have worked if you've added a hidden INT to the project declaring the version of the plugin used in the project. Then the parameter will not be overwritten be the new version of the plugin.
This could also work (though it's not a great solution) if you set the default value of the parameter based on whether you updated the project or not, I would think. Or am I misunderstanding the problem? The (current) necessity to create a template for FCP X adds a whole new layer of problems in terms of the things you try to do. Nothing is really transparent when the plugin runs inside a template under FCP X.
THE solution to all of this is (in my opinion) to make FCP X able to read FxPlugins natively without going through templates. Then we will be able to create parameters dynamically, have custom parameters, we could create labels (which I so badly need(!!!) for me newest plugins)... and much more.
Motion templates and native FxPlugs solve 2 different problems. We (and our users) want all FxPlugs to be able to work properly with Motion Templates. Some of the pieces that you mention above are missing at the moment, and that's unfortunate.
Also, the idea with templates is that they will not just contain a copy of every parameter in every plug-in, but that developers will think through specific tasks that users need to perform and will provide templates for those tasks rather than raw plug-ins with dozens of parameters that most users won't understand. @Darrin: Will FCP X ever get a native FxPlug interface?
I'm not able to comment on future functionality.
Darrin
|
_______________________________________________
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