Re: FxPlug versioning
Re: FxPlug versioning
- Subject: Re: FxPlug versioning
- From: Alex Gollner <email@hidden>
- Date: Wed, 27 Mar 2013 17:55:26 +0000
- Thread-topic: FxPlug versioning
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.
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.
Alex
..........................................................................
Film Editor, Zone 2-North West, London
@alex4d . alex4d.wordpress.com . alex4d.com . +44 775 367 7918
_______________________________________________
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