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

Are new Motion templates working with older version of FCP X?
by Christoph Vonrhein 24 Apr '13

24 Apr '13

Hello, I have the case right now that a beta tester can't get a new plugin package to work. I've created the templates (Video Generators) with Motion 5.0.7 and they work on my Macs perfectly with Motion 5.0.7 and FCP X 10.0.8. My beta tester uses FCP X 10.0.5 and he gets in the Console this error message: "4/23/13 10:47:47 PM [0x0-0x1c51c5].com.apple.FinalCut[3947] Credits.motn : parsing error" ...and and error message in the canvas of FCP X. When he opens FCP X 10.0.8, then everything works. I am also able to verify the same behavior on my MacBook Pro. Templates that were created with Motion 5.0.7 don't work with FCP X 10.0.6. Shouldn't templates that were created with Motion 5.0.7 also work with older FCP X versions, like FCP X 10.0.5 and 10.0.6? Christoph Vonrhein _______________________________________________ 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 05 Apr '13

05 Apr '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 05 Apr '13

05 Apr '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 and Template folders
by Darrin Cardani 04 Apr '13

04 Apr '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

FxPlug and Template folders
by Christoph Vonrhein 04 Apr '13

04 Apr '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 Darrin Cardani 04 Apr '13

04 Apr '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: Lion Finder bugs
by Darrin Cardani 04 Apr '13

04 Apr '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: Lion Finder bugs
by Christoph Vonrhein 04 Apr '13

04 Apr '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 03 Apr '13

03 Apr '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 02 Apr '13

02 Apr '13

Hi Darrin, please excuse that I am also on top of this topic. I have the same problem (like Martin) with some of my plugins which I want to update and also have different parameters in the new version. Number 1 would work, but it is kinda lame and it will create some confusion. I am sure we would get customer questions like "I updated the plugins... and I still have the old one in the menu... Why?" Number 2 might work. I'll give it a try. But I think that it will create internally some confusion (breeding ground for errors), because we might want to update the plugins again and again. In the end we will have 6 versions of a certain plugin and each customer has a different version installed. I foresee a lot of chaos. It would be great if the versionAtCreation value would be working. Christoph On Apr 2, 2013, at 1:48 PM, Darrin Cardani wrote: > OK, I've been thinking about this, and I'm coming to the conclusion that you might be right that we need some sort of template versioning, too. I think there are a couple of solutions that would be possible: > > 1) Make a new template that has the new functionality and ship 2 templates: Legacy template and New template. Old projects will use the legacy one and won't get the new menu items, and new projects will use the new template and get the new menu items. > > Pros: Fairly easy to implement, doesn't break rendering of old projects > Cons: Kind of lame. Users have to know to apply the new one from now on > > 2) I'm not positive if this will work, but I think it will: During development, build a version of your plugin that reports itself as version 1, but contains 2 menus, both visible. Make a template with this version of your plug-in. Once the template is made, update the plug-in version to 2, but don't update the template. In the plug-in, in -addParameters, if it is still version 1 (which it always will be the first time the user applies it), update it to version 2 and show the new menu from now on. > > Pros: One template, works seamlessly for the user (hopefully?) > Cons: Development takes longer, requires steps executed in particular order > > Does that seem like it could work? > > Darrin > > On Mar 29, 2013, at 9:23 AM, Darrin Cardani <dcardani(a)apple.com> wrote: > >> Martin, >> >> I think I see what's happening now, and I need to apologize for being so dense! Our workflow for our Motion Templates is different from what you're describing, and I see now why you're seeing what you're seeing, and we're seeing what we're seeing. I'm going to give it some thought and see if I can come up with a reasonable solution for you. >> >> Darrin >> >> On Mar 29, 2013, at 4:51 AM, Martin Baker <martin(a)digital-heaven.co.uk> wrote: >> >>> Hi Darrin >>> >>> I'm not sure what I'm doing wrong here because I've just run another test this morning with the simplest changes possible and I'm definitely still seeing the same incorrect versionAtCreation value. >>> >>> This was with FCP 10.0.8 and Motion 5.0.7 on OS10.8.3 >>> >>> • In FCP, added the current version of the generator to a new timeline. >>> • Started with the FxPlug code for current v1.0 release. >>> • Changed the ProPlugPluginList > version = 2 in Info.plist. >>> • Added NSLog for value of versionAtCreation inside finishInitialSetup. >>> • Uninstalled v1 FxPlug and installed v2 FxPlug >>> • Removed v1 Motion template. >>> • Created a new Motion template using the v2 FxPlug. >>> • Launched FCP and opened the timeline with the v1 instance of generator template. >>> • As seen yesterday, the versionAtCreation is reported as "2" not the expected "1" value. >>> >>> Happy to send you all v1 and v2 FxPlugs and templates if you like. >>> >>> Has anyone on the list got the expected versionAtCreation value when running in FCP? >>> >>> 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 28 Mar 2013, at 17:22, Darrin Cardani wrote: >>> >>>> As I mentioned, we do this with our shipping plug-ins now and haven't had problems with it. If the user creates an FCP project using the old Motion Template, then when they open it with the new template, you'll be told that the instance of your FxPlug was created with version 1. >>> >> >> >> _______________________________________________ >> 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/chv%40chv-electronics.… > > This email sent to chv(a)chv-electronics.de _______________________________________________ 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