March 2013 - Pro-apps-dev - lists.apple.com

Re: FxPlug versioning
by Darrin Cardani 28 Mar '13

28 Mar '13

_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Jon Chappell 28 Mar '13

28 Mar '13

_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Christoph Vonrhein 28 Mar '13

28 Mar '13

_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Martin Baker 28 Mar '13

28 Mar '13

_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Martin Baker 27 Mar '13

27 Mar '13

I'll give it a whirl and report back. Martin www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 On 27 Mar 2013, at 20:06, Darrin Cardani wrote: > It should work fine in Motion. I haven't tried that inside a Motion Template running in FCP, so I'm not sure what the already-published menu will look like. I think it should work, but off the top of my head, I'm not positive. > > Darrin > > On Mar 27, 2013, at 1:01 PM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: > >> Thanks Darrin >> >> That's useful. I think what I'm seeing is that there isn't really an easy way to migrate from one major version to another. I could see a possible way with a hidden BOOL "upgraded" flag but this seems to open a whole can of other worms (nightmares of dynamic adding of parameters etc) and it probably isn't worth the effort. The user will just have to live with the fact that the new menu options are only possible with a brand new instance of the plug-in, which in reality isn't that much of a hardship :-). >> >> It does make complete sense that adding a new parameter and choosing which one will be hidden/shown would require a new Motion Template. But now I'm wondering if I could just leave the parameter ID unchanged and check the versionAtCreation in addParameters to set the required number of menus, and also in renderOutput, to remap the popup values if necessary from a v1 instance... >> >> Martin >> www.digital-heaven.co.uk >> www.twitter.com/digitalheaven >> www.videospaceonline.com >> www.finalcutters.com >> ------------------------------------------------------ >> Digital Heaven Ltd is registered in England and Wales >> Company registration number: 3628396 >> Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE >> VAT registration number: GB 736 0989 03 >> >> On 27 Mar 2013, at 16:56, Darrin Cardani wrote: >> >>> Oh, I should add - if you go with my suggestion of hiding either the old or new popup menu based on the version, then I think question 3 is irrelevant because the popup menu you don't want the user to see should always be hidden. >>> >>> Another option is to put the new items at the end of the menu. In this case, that's not very user-friendly because of the meaning of the menu items, but it's probably the easiest option. >>> >>> Darrin >>> >>> On Mar 27, 2013, at 7:34 AM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: >>> >>>> I have a popup menu parameter which currently has the following options >>>> SS >>>> MM:SS >>>> HH:MM:SS >>>> >>>> and I want to add 2 new menus so it is like this: >>>> SS >>>> M:SS >>>> MM:SS >>>> H:MM:SS >>>> HH:MM:SS >>>> >>>> Q1: I'm fairly positive that Motion/FCP just stores the selected index of the popup, so a user opening a v1 project with the v2 plug-in would have their HH:MM:SS choice now showing up as MM:SS? >>>> >>>> Q2: So looking at the versioningAPI, I can check for versionAtCreation == 1, but then what? I could internally remap old index 1 to new 3, and old index 2 to new 4 but the parameter value should really be updated programmatically so the UI shows the correct choice. So that's doable, but then for the future how do I tell Motion/FCP that this has been updated since versionAtCreation is read only? >>>> >>>> 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? >>>> >>>> >>>> thanks >>>> >>>> Martin Baker >>>> www.digital-heaven.co.uk >>>> www.twitter.com/digitalheaven >>>> www.videospaceonline.com >>>> www.finalcutters.com >>>> ------------------------------------------------------ >>>> Digital Heaven Ltd is registered in England and Wales >>>> Company registration number: 3628396 >>>> Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE >>>> VAT registration number: GB 736 0989 03 >>>> >>>> >>>> _______________________________________________ >>>> 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: >>>> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >>>> >>>> This email sent to 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Darrin Cardani 27 Mar '13

27 Mar '13

It should work fine in Motion. I haven't tried that inside a Motion Template running in FCP, so I'm not sure what the already-published menu will look like. I think it should work, but off the top of my head, I'm not positive. Darrin On Mar 27, 2013, at 1:01 PM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: > Thanks Darrin > > That's useful. I think what I'm seeing is that there isn't really an easy way to migrate from one major version to another. I could see a possible way with a hidden BOOL "upgraded" flag but this seems to open a whole can of other worms (nightmares of dynamic adding of parameters etc) and it probably isn't worth the effort. The user will just have to live with the fact that the new menu options are only possible with a brand new instance of the plug-in, which in reality isn't that much of a hardship :-). > > It does make complete sense that adding a new parameter and choosing which one will be hidden/shown would require a new Motion Template. But now I'm wondering if I could just leave the parameter ID unchanged and check the versionAtCreation in addParameters to set the required number of menus, and also in renderOutput, to remap the popup values if necessary from a v1 instance... > > Martin > www.digital-heaven.co.uk > www.twitter.com/digitalheaven > www.videospaceonline.com > www.finalcutters.com > ------------------------------------------------------ > Digital Heaven Ltd is registered in England and Wales > Company registration number: 3628396 > Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE > VAT registration number: GB 736 0989 03 > > On 27 Mar 2013, at 16:56, Darrin Cardani wrote: > >> Oh, I should add - if you go with my suggestion of hiding either the old or new popup menu based on the version, then I think question 3 is irrelevant because the popup menu you don't want the user to see should always be hidden. >> >> Another option is to put the new items at the end of the menu. In this case, that's not very user-friendly because of the meaning of the menu items, but it's probably the easiest option. >> >> Darrin >> >> On Mar 27, 2013, at 7:34 AM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: >> >>> I have a popup menu parameter which currently has the following options >>> SS >>> MM:SS >>> HH:MM:SS >>> >>> and I want to add 2 new menus so it is like this: >>> SS >>> M:SS >>> MM:SS >>> H:MM:SS >>> HH:MM:SS >>> >>> Q1: I'm fairly positive that Motion/FCP just stores the selected index of the popup, so a user opening a v1 project with the v2 plug-in would have their HH:MM:SS choice now showing up as MM:SS? >>> >>> Q2: So looking at the versioningAPI, I can check for versionAtCreation == 1, but then what? I could internally remap old index 1 to new 3, and old index 2 to new 4 but the parameter value should really be updated programmatically so the UI shows the correct choice. So that's doable, but then for the future how do I tell Motion/FCP that this has been updated since versionAtCreation is read only? >>> >>> 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? >>> >>> >>> thanks >>> >>> Martin Baker >>> www.digital-heaven.co.uk >>> www.twitter.com/digitalheaven >>> www.videospaceonline.com >>> www.finalcutters.com >>> ------------------------------------------------------ >>> Digital Heaven Ltd is registered in England and Wales >>> Company registration number: 3628396 >>> Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE >>> VAT registration number: GB 736 0989 03 >>> >>> >>> _______________________________________________ >>> 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: >>> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >>> >>> This email sent to 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Martin Baker 27 Mar '13

27 Mar '13

Thanks Darrin That's useful. I think what I'm seeing is that there isn't really an easy way to migrate from one major version to another. I could see a possible way with a hidden BOOL "upgraded" flag but this seems to open a whole can of other worms (nightmares of dynamic adding of parameters etc) and it probably isn't worth the effort. The user will just have to live with the fact that the new menu options are only possible with a brand new instance of the plug-in, which in reality isn't that much of a hardship :-). It does make complete sense that adding a new parameter and choosing which one will be hidden/shown would require a new Motion Template. But now I'm wondering if I could just leave the parameter ID unchanged and check the versionAtCreation in addParameters to set the required number of menus, and also in renderOutput, to remap the popup values if necessary from a v1 instance... Martin www.digital-heaven.co.uk www.twitter.com/digitalheaven www.videospaceonline.com www.finalcutters.com ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03 On 27 Mar 2013, at 16:56, Darrin Cardani wrote: > Oh, I should add - if you go with my suggestion of hiding either the old or new popup menu based on the version, then I think question 3 is irrelevant because the popup menu you don't want the user to see should always be hidden. > > Another option is to put the new items at the end of the menu. In this case, that's not very user-friendly because of the meaning of the menu items, but it's probably the easiest option. > > Darrin > > On Mar 27, 2013, at 7:34 AM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: > >> I have a popup menu parameter which currently has the following options >> SS >> MM:SS >> HH:MM:SS >> >> and I want to add 2 new menus so it is like this: >> SS >> M:SS >> MM:SS >> H:MM:SS >> HH:MM:SS >> >> Q1: I'm fairly positive that Motion/FCP just stores the selected index of the popup, so a user opening a v1 project with the v2 plug-in would have their HH:MM:SS choice now showing up as MM:SS? >> >> Q2: So looking at the versioningAPI, I can check for versionAtCreation == 1, but then what? I could internally remap old index 1 to new 3, and old index 2 to new 4 but the parameter value should really be updated programmatically so the UI shows the correct choice. So that's doable, but then for the future how do I tell Motion/FCP that this has been updated since versionAtCreation is read only? >> >> 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? >> >> >> thanks >> >> Martin Baker >> www.digital-heaven.co.uk >> www.twitter.com/digitalheaven >> www.videospaceonline.com >> www.finalcutters.com >> ------------------------------------------------------ >> Digital Heaven Ltd is registered in England and Wales >> Company registration number: 3628396 >> Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE >> VAT registration number: GB 736 0989 03 >> >> >> _______________________________________________ >> 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: >> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >> >> This email sent to 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Darrin Cardani 27 Mar '13

27 Mar '13

On Mar 27, 2013, at 10:55 AM, Alex Gollner <alex(a)alex4d.com> 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 <dcardani(a)apple.com> 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 (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Alex Gollner 27 Mar '13

27 Mar '13

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 <dcardani(a)apple.com> 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 (Pro-apps-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: FxPlug versioning
by Darrin Cardani 27 Mar '13

27 Mar '13

On Mar 27, 2013, at 9:53 AM, Darrin Cardani <dcardani(a)apple.com> 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 _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0