May 2014 - Pro-apps-dev - lists.apple.com

Re: FCP X: Problems with FxKeyframeAPI & FxParameterSettingAPI
by Darrin Cardani 13 May '14

13 May '14

It is definitely expected that parameters will change during OSC events. (That’s the point of an OSC!) And you should be able to manipulate keyframes then, too. If you could file a Radar on what you were doing that failed, that would be extremely helpful. Darrin On May 13, 2014, at 11:57 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: > > The problem appeared when changing keyframes and parameter values during OSC mouse event processing. > It's ok for us to move this code to the -parameterChanged: method, but we need to be able to save some plugin configuration data to a custom parameter during OSC event processing in future versions. > > Eberhard > > >> Eberhard, >> >> Yes. Anything that changes the data model of the application (like the values of your parameters) will only work in either -parameterChanged: or in OSC code. It definitely won’t work during a render (including set up and teardown of the render). This is something that we have been lenient about in the past, but now with multi-GPU rendering, we have to be much more strict about. >> >> Darrin >> >> On May 13, 2014, at 11:42 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: >> >>> >>> Hello Darrin, >>> >>> yes, I'm using the keyframe api and the parameter setting api for setting parameter values. >>> After some more testing I found that the problems are related to the context where this code is called. >>> I've moved this code into the effect's "parameterChanged:" method, and this seems to fix both problems. >>> Is it expected to work only in the "parameterChanged:" method? >>> >>> Eberhard >>> >>>> Eberhard, >>>> >>>> Are you trying to do this with the Keyframe API? Can you file a Radar and attach a simple example that shows the problem? >>>> >>>> Darrin >>>> >>>> On May 9, 2014, at 10:57 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: >>>> >>>>> >>>>> Hello, >>>>> >>>>> I'm trying to add some parameter keyframes and change some parameter values in the course of an on screen event, latest version of FCP X. >>>>> This doesn't work reliably, sometimes keyframes are missing, or it fails to adjust a parameter value. >>>>> >>>>> I noticed that each time when a parameter value is changed the on screen controls are redrawn and the effect renders immediately - multiple times within a single on screen event call. >>>>> Is there a way to suppress on screen updating and rendering when changing multiple parameter values? >>>>> >>>>> Thanks, Eberhard >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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: FCP X: Problems with FxKeyframeAPI & FxParameterSettingAPI
by Eberhard Ammelt 13 May '14

13 May '14

The problem appeared when changing keyframes and parameter values during OSC mouse event processing. It's ok for us to move this code to the -parameterChanged: method, but we need to be able to save some plugin configuration data to a custom parameter during OSC event processing in future versions. Eberhard > Eberhard, > > Yes. Anything that changes the data model of the application (like the values of your parameters) will only work in either -parameterChanged: or in OSC code. It definitely won’t work during a render (including set up and teardown of the render). This is something that we have been lenient about in the past, but now with multi-GPU rendering, we have to be much more strict about. > > Darrin > > On May 13, 2014, at 11:42 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: > >> >> Hello Darrin, >> >> yes, I'm using the keyframe api and the parameter setting api for setting parameter values. >> After some more testing I found that the problems are related to the context where this code is called. >> I've moved this code into the effect's "parameterChanged:" method, and this seems to fix both problems. >> Is it expected to work only in the "parameterChanged:" method? >> >> Eberhard >> >>> Eberhard, >>> >>> Are you trying to do this with the Keyframe API? Can you file a Radar and attach a simple example that shows the problem? >>> >>> Darrin >>> >>> On May 9, 2014, at 10:57 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: >>> >>>> >>>> Hello, >>>> >>>> I'm trying to add some parameter keyframes and change some parameter values in the course of an on screen event, latest version of FCP X. >>>> This doesn't work reliably, sometimes keyframes are missing, or it fails to adjust a parameter value. >>>> >>>> I noticed that each time when a parameter value is changed the on screen controls are redrawn and the effect renders immediately - multiple times within a single on screen event call. >>>> Is there a way to suppress on screen updating and rendering when changing multiple parameter values? >>>> >>>> Thanks, Eberhard >>>> >>>> >>>> _______________________________________________ >>>> 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: FCP X: Problems with FxKeyframeAPI & FxParameterSettingAPI
by Darrin Cardani 13 May '14

13 May '14

Eberhard, Yes. Anything that changes the data model of the application (like the values of your parameters) will only work in either -parameterChanged: or in OSC code. It definitely won’t work during a render (including set up and teardown of the render). This is something that we have been lenient about in the past, but now with multi-GPU rendering, we have to be much more strict about. Darrin On May 13, 2014, at 11:42 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: > > Hello Darrin, > > yes, I'm using the keyframe api and the parameter setting api for setting parameter values. > After some more testing I found that the problems are related to the context where this code is called. > I've moved this code into the effect's "parameterChanged:" method, and this seems to fix both problems. > Is it expected to work only in the "parameterChanged:" method? > > Eberhard > >> Eberhard, >> >> Are you trying to do this with the Keyframe API? Can you file a Radar and attach a simple example that shows the problem? >> >> Darrin >> >> On May 9, 2014, at 10:57 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: >> >>> >>> Hello, >>> >>> I'm trying to add some parameter keyframes and change some parameter values in the course of an on screen event, latest version of FCP X. >>> This doesn't work reliably, sometimes keyframes are missing, or it fails to adjust a parameter value. >>> >>> I noticed that each time when a parameter value is changed the on screen controls are redrawn and the effect renders immediately - multiple times within a single on screen event call. >>> Is there a way to suppress on screen updating and rendering when changing multiple parameter values? >>> >>> Thanks, Eberhard >>> >>> >>> _______________________________________________ >>> 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: FCP X: Problems with FxKeyframeAPI & FxParameterSettingAPI
by Eberhard Ammelt 13 May '14

13 May '14

Hello Darrin, yes, I'm using the keyframe api and the parameter setting api for setting parameter values. After some more testing I found that the problems are related to the context where this code is called. I've moved this code into the effect's "parameterChanged:" method, and this seems to fix both problems. Is it expected to work only in the "parameterChanged:" method? Eberhard > Eberhard, > > Are you trying to do this with the Keyframe API? Can you file a Radar and attach a simple example that shows the problem? > > Darrin > > On May 9, 2014, at 10:57 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: > >> >> Hello, >> >> I'm trying to add some parameter keyframes and change some parameter values in the course of an on screen event, latest version of FCP X. >> This doesn't work reliably, sometimes keyframes are missing, or it fails to adjust a parameter value. >> >> I noticed that each time when a parameter value is changed the on screen controls are redrawn and the effect renders immediately - multiple times within a single on screen event call. >> Is there a way to suppress on screen updating and rendering when changing multiple parameter values? >> >> Thanks, Eberhard >> >> >> _______________________________________________ >> 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: FCP X: Problems with FxKeyframeAPI & FxParameterSettingAPI
by Darrin Cardani 13 May '14

13 May '14

Eberhard, Are you trying to do this with the Keyframe API? Can you file a Radar and attach a simple example that shows the problem? Darrin On May 9, 2014, at 10:57 AM, Eberhard Ammelt <EAmmelt(a)pixlock.com> wrote: > > Hello, > > I'm trying to add some parameter keyframes and change some parameter values in the course of an on screen event, latest version of FCP X. > This doesn't work reliably, sometimes keyframes are missing, or it fails to adjust a parameter value. > > I noticed that each time when a parameter value is changed the on screen controls are redrawn and the effect renders immediately - multiple times within a single on screen event call. > Is there a way to suppress on screen updating and rendering when changing multiple parameter values? > > Thanks, Eberhard > > > _______________________________________________ > 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: 4K templates
by Paul Miller 13 May '14

13 May '14

On 5/12/2014 7:18 PM, Martin Baker wrote: Yes that makes sense. I’d misread the article as being aimed at developers rather than end users making custom templates. +1 insightful. Martin Baker www.digital-heaven.co.uk <http://www.digital-heaven.co.uk> www.twitter.com/digitalheaven <http://www.twitter.com/digitalheaven> ------------------------------------------------------ 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 13 May 2014, at 08:56, Darrin Cardani <dcardani(a)apple.com <mailto:dcardani@apple.com>> wrote: I think it’s one of those things where it may work perfectly fine in a specific case (particularly if you’re just making a template for your FxPlug), but in general it won’t. For example, if you include any assets in your template that will be scaled, you probably want them at the highest resolution so they’re only ever scaled down, and not up. Darrin On May 12, 2014, at 3:50 PM, Martin Baker <mjb(a)digital-heaven.co.uk <mailto:mjb@digital-heaven.co.uk>> wrote: The article is confusing. /Although the template scales to fit the resolution of the Final Cut Pro X project it is applied to, you should create the template at the highest resolution you will use./ Why? I was under the impression that the actual resolution of the template doesn’t matter in FCP. I can take apply one of our FxPlugs (that uses a 1920x1080 Motion template) and it is perfectly sharp in a 4K timeline. Martin Baker www.digital-heaven.co.uk <http://www.digital-heaven.co.uk/> www.twitter.com/digitalheaven <http://www.twitter.com/digitalheaven> ------------------------------------------------------ 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 13 May 2014, at 08:37, Jim Tierney <jim(a)digitalanarchy.com <mailto:jim@digitalanarchy.com>> wrote: They'll work, but if you're in a 4K project, there's a checkbox called '4K Content Only'. If that property isn't set correctly in your template, your effect won't be listed if the user turns the checkbox on (even if your effect works fine with 4K). It's cosmetic, but confusing to users, IMO. See this: http://support.apple.com/kb/PH16062 Cheers, Jim --------------- Jim Tierney President Digital Anarchy -----Original Message----- From: pro-apps-dev-bounces+jim=digitalanarchy.com(a)lists.apple.com <mailto:pro-apps-dev-bounces+jim=digitalanarchy.com@lists.apple.com> [mailto:pro-apps-dev-bounces+jim=digitalanarchy.com@lists.apple.com] On Behalf Of Paul Miller Sent: Monday, May 12, 2014 11:01 AM To: pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com> Subject: Re: Pro-apps-dev Digest, Vol 11, Issue 20 On 5/12/2014 11:52 AM, Garrick Meeker wrote: Given all the garbage frame bugs that lasted until maybe FCP 10.0.7, I don’t think it’s realistic to support versions of FCP older than that anyway. But we just discovered that older templates don’t show up as “4K Ready”, so now we need to create one template for FCP 10.0.9 with Motion 5.0.x and one template with 4K project settings and 4K Ready checked for FCP 10.1.x with Motion 5.1.x. I could see this getting difficult to manage in a few years if we’re still required to create templates. You mean the 106 templates I just did with the default HD template won't work in a 4k project? Paul SMASH! On May 9, 2014, at 1:28 PM, Peter Litwinowicz <pete(a)revisionfx.com <mailto:pete@revisionfx.com> <mailto:pete@revisionfx.com>> wrote: What we are mostly talking about is creating previous Motion templates for use in previous versions of FCP. That said, most of our users will ONLY have FCP and not Motion. So what to do then? There's no way for them to create templates. We are mostly talking about old versions of FCP that can only load older Motion template versions… so we want an older version of Motion to create templates for those older versions of FCP. Pete From:Dieter Becker <dieterdavebecker(a)gmail.com <mailto:dieterdavebecker@gmail.com> <mailto:dieterdavebecker@gmail.com>> Date:Friday, May 9, 2014 1:14 PM To:<pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com> <mailto:pro-apps-dev@lists.apple.com>> Subject:Re: Pro-apps-dev Digest, Vol 11, Issue 20 Hi, if the user/client can’t/won’t update and still has the Motion version that you don’t. Then just ask him to create the template himself. Creating a template is easier than getting email Mail. I take that the cases where one cannot update for some reason, are few. So - perhaps in those cases, take 2 minutes to describe to the user how to create the template himself with your plug-in. My 2 Cents anyway — Best Morten _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com <mailto:Pro-apps-dev@lists.apple.com> <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/pete%40revisionf x.com <http://x.com> This email sent topete(a)revisionfx.com <mailto:pete@revisionfx.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 <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/garrick%40digita lanarchy.com This email sent togarrick(a)digitalanarchy.com <mailto:garrick@digitalanarchy.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 <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/paul%40fxtech.com This email sent to paul(a)fxtech.com <mailto:paul@fxtech.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 <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/jim%40digitalanarchy.c… This email sent to jim(a)digitalanarchy.com <mailto:jim@digitalanarchy.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 <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/mjb%40digital-heaven.c… This email sent tomjb(a)digital-heaven.co.uk <mailto:mjb@digital-heaven.co.uk> _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com <mailto:Pro-apps-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com This email sent todcardani(a)apple.com <mailto:dcardani@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/paul%40fxtech.com This email sent to paul(a)fxtech.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 Developers who just want to get their products out the door don't always think the way end-users do (and I don't have a team of "artists" on staff). Still, considering all the settings in templates are resolution independent, why the need for the "4K" button anyway? Seems like a needless source of confusion and frustration.

1 0

Re: 4K templates
by Martin Baker 13 May '14

13 May '14

_______________________________________________ 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: 4K templates
by Garrick Meeker 13 May '14

13 May '14

_______________________________________________ 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: 4K templates
by Darrin Cardani 12 May '14

12 May '14

_______________________________________________ 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: 4K templates
by Peter Litwinowicz 12 May '14

12 May '14

_______________________________________________ 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