Re: FxPlug versioning
Re: FxPlug versioning
- Subject: Re: FxPlug versioning
- From: Darrin Cardani <email@hidden>
- Date: Wed, 27 Mar 2013 11:02:43 -0700
On Mar 27, 2013, at 10:55 AM, Alex Gollner <email@hidden> wrote:
> On 27/03/2013 5:35 pm, Pro-Apps-Dev sent a message to me that included:
>
>>
>> On Mar 27, 2013, at 9:53 AM, Darrin Cardani <email@hidden> wrote:
>>
>>>> Q3: Is it necessary to remake the Motion Template when adding menus to a
>>>> popup, or is that parameter just published by ID, so will update in FCP
>>>> automatically?
>>>
>>> I will have to look into that.
>>
>> My suspicion was correct - you'll have to remake the Motion Template if you
>> change the menu item. It looks like there may be a way to avoid this in the
>> future if we expand the API to support it. I'll look into what it will take to
>> make that happen.
>>
>> Darrin
>
> Given that Motion is used to create the effect template that is used in
> Final Cut Pro, it is a matter of changing the way Motion works. At the
> moment it is not the FxPlug's controls that are published and made available
> in Final Cut. It is a series of snapshots of FxPlug control values that are
> associated with the three kinds of controls that Motion can publish.
>
What I was attempting to say was that Motion supports a mechanism to avoid this problem already, but there is no FxPlug API to allow plug-ins to make use of it. So popup menus for controls that are native to Motion don't suffer from this problem. Everything's in place, but we need to add some API so that FxPlugs can give Motion the appropriate information it needs to work with popup menus in FxPlugs. Does that make sense?
> It practice this means that Final Cut timelines that refer to the old
> version of the plug-in (via the older version of it's associated Motion
> template) will not recognise the new Motion template you'll need to create
> for the new version of the plug-in.
Is this a problem you've run into? I believe that you should be able to update existing templates when you release a new version of your FxPlug, and older FCP projects should recognize them. Are you finding that's not the case?
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