September 2017 - Pro-apps-dev

Re: Question about growing memory problem with our plug-in
by Darrin Cardani 16 Sep '17

16 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Glad to hear it! Darrin > On Sep 15, 2017, at 12:54 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > Argh, I finally figured it out. > > Turns out that in my worker thread I didn't turn off GPU processing for our > code. In fact, I didn't set it up at all. In that case, our internal code > will use the last GPU device setup used… which in this case is an OpenCL > context attached to an OpenGL context. And that OpenGL context is one that > FCP has provided for retrieving its images. > > So, basically, I was indirectly using an OpenGL context in two threads > concurrently. Now, why OpenGL didn't spit out some error messages in the > system error log or the console, I don't know. But the problem wasn't memory > related per se. > > I just happened upon this conflict by chance. Whew! Anyhow, it's fixed now. > > Pete > > > From: Pro-apps-dev <pro-apps-dev-bounces+pete=revisionfx.com(a)lists.apple.com > <mailto:pro-apps-dev-bounces+pete=revisionfx.com@lists.apple.com>> on behalf > of Peter Litwinowicz <pete(a)revisionfx.com <mailto:pete@revisionfx.com>> > Date: Thursday, September 14, 2017 at 4:36 PM > To: Darrin Cardani <dcardani(a)apple.com <mailto:dcardani@apple.com>>, > <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> > Subject: Question about growing memory problem with our plug-in > > I'm having one heck of a time with my analysis pass plug-in that we're > creating. > > If I get an FxImage, copy the image to my own memory, dealloc the FxImage, > then process, then get another FxImage, copy, deallocate, then process, in > the same thread… then all goes fine. > > Well our analysis works about as fast as a CPU memory fetch of an FxImage, so > I figured I would get images on the main thread, and process on another > thread. So now I get an FxImage then copy, then "throw" over to another > thread for processing, then concurrently (on the main thread) get another > FxImage. Repeat. Goes about 2x as fast, as you might expect. > > EXCEPT > > All goes fine for about 500 frames. Then all of a sudden kernel_task starts > to grow memory by leaps and bounds. Before 500 frames, kernel_task is at 3Gb > of memory usage, FCP is at about 1.2Gb. Both remain approximately constant > Then memory continues to grow for kernel_task, while FCP stays constant (at > about 1.2Gb). Over the course of 80 frames or so, kernel_task grows from 3Gb > of usage to over 35Gb. Then I get a system error message (not a crash in my > plug-in or FCP), that "System has run out of Application Memory". Oy. I > read this is related to virtual memory become scarce. Crap. > > I KNOW I don't have a memory leak in my code (it's code we've used for YEARS > and have analyzed it's memory usage quite rigorously). And the code works if > the frame retrieval and processing is in the same thread. Of course we > allocate and release memory in our plug-in using malloc, but the memory > allocations and deallocations are all balanced. > > I thought maybe there's some issue with concurrent memory allocations by FCP > and our plug-in, but malloc and other memory routines are supposed to be > thread safe. So perhaps some memory fragmentation? But wouldn't that > probably happen even if our processing is happening in line (and in the same > thread) as the frame retrieval? > > Anyone have any ideas? Bueller? > > Pete > > _______________________________________________ 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/pete%40revisionfx.com > <https://lists.apple.com/mailman/options/pro-apps-dev/pete%40revisionfx.com>This > email sent to pete(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) > 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: Accessing parameter widgets
by Darrin Cardani 16 Sep '17

16 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Actually, one thing I haven’t tried is using the FxDynamicParameterAPI to change the name of the parameter. I’m not sure off the top of my head whether it changes both the name in the inspector and inside the button or just one of those. You might want to give that a try and see what happens. Darrin > On Sep 16, 2017, at 10:19 AM, Darrin Cardani <dcardani(a)apple.com> wrote: > > I’m not aware of a way to do this from within your FxPlug. If you are > creating a Final Cut Effect, you can rename published parameters when > creating the template in Motion. Once you’ve published the parameter, select > the project in the layer list, then click on the Inspector tab and choose the > “Project” tab. It will have the names of all your published parameters. You > can double click one to change it. > > Darrin > >> On Sep 13, 2017, at 1:54 PM, Lyndon Hill <lyndon(a)tiliam.com> wrote: >> >> Hi, >> >> When I use [FxParameterCreationAPI_v4 addPushButtonWithName:@“Generate” …] >> the push button gets placed on a line in the filter parameters with a label >> as depicted below: >> >> Generate [Generate] >> >> How can I change the first label to something else ? e.g. >> >> Important Initialisation [Generate] >> >> >> Also, I was wondering if it is possible to access menu entries from >> [FxParameterCreationAPI addPopupMenuWithName:…] in order to enable/disable >> certain options ? >> >> >> Or are these things only possible through custom UI ? >> >> >> Many thanks in advance, >> >> Lyndon Hill >> _______________________________________________ >> 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/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: Multicam processing
by Darrin Cardani 16 Sep '17

16 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I’ll have to ask what the expected workflow is here, as I’m not entirely sure. Darrin > On Sep 15, 2017, at 6:53 AM, Lyndon Hill <lyndon(a)tiliam.com> wrote: > > Hi, > > I’m not an expert in multicam (or FCPX either), but I heard that it’s > possible for a plugin to be applied to a multicam clip. From what they were > saying, create a multicam clip, drop it on the timeline, drop the filter on > the multicam clip and the plugin works on each clip. > > When I tried this with my plugin it worked on the current angle only. If I > cut the multicam clip, then I have to drop the plugin on each section. This > is actually what I would expect to happen. > > I don’t see anything in the FxPlug API that supports the action as described > to me. > > thanks in advance > > Lyndon > > _______________________________________________ > 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: Accessing parameter widgets
by Darrin Cardani 16 Sep '17

16 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I’m not aware of a way to do this from within your FxPlug. If you are creating a Final Cut Effect, you can rename published parameters when creating the template in Motion. Once you’ve published the parameter, select the project in the layer list, then click on the Inspector tab and choose the “Project” tab. It will have the names of all your published parameters. You can double click one to change it. Darrin > On Sep 13, 2017, at 1:54 PM, Lyndon Hill <lyndon(a)tiliam.com> wrote: > > Hi, > > When I use [FxParameterCreationAPI_v4 addPushButtonWithName:@“Generate” …] > the push button gets placed on a line in the filter parameters with a label > as depicted below: > > Generate [Generate] > > How can I change the first label to something else ? e.g. > > Important Initialisation [Generate] > > > Also, I was wondering if it is possible to access menu entries from > [FxParameterCreationAPI addPopupMenuWithName:…] in order to enable/disable > certain options ? > > > Or are these things only possible through custom UI ? > > > Many thanks in advance, > > Lyndon Hill > _______________________________________________ > 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: Question about growing memory problem with our plug-in
by Peter Litwinowicz 15 Sep '17

15 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: Question about growing memory problem with our plug-in User-agent: Microsoft-MacOutlook/14.7.7.170905 Argh, I finally figured it out. Turns out that in my worker thread I didn't turn off GPU processing for our code. In fact, I didn't set it up at all. In that case, our internal code will use the last GPU device setup used… which in this case is an OpenCL context attached to an OpenGL context. And that OpenGL context is one that FCP has provided for retrieving its images. So, basically, I was indirectly using an OpenGL context in two threads concurrently. Now, why OpenGL didn't spit out some error messages in the system error log or the console, I don't know. But the problem wasn't memory related per se. I just happened upon this conflict by chance. Whew! Anyhow, it's fixed now. Pete From: Pro-apps-dev <pro-apps-dev-bounces+pete=revisionfx.com(a)lists.apple.com> on behalf of Peter Litwinowicz <pete(a)revisionfx.com> Date: Thursday, September 14, 2017 at 4:36 PM To: Darrin Cardani <dcardani(a)apple.com>, <pro-apps-dev(a)lists.apple.com> Subject: Question about growing memory problem with our plug-in I'm having one heck of a time with my analysis pass plug-in that we're creating. If I get an FxImage, copy the image to my own memory, dealloc the FxImage, then process, then get another FxImage, copy, deallocate, then process, in the same thread… then all goes fine. Well our analysis works about as fast as a CPU memory fetch of an FxImage, so I figured I would get images on the main thread, and process on another thread. So now I get an FxImage then copy, then "throw" over to another thread for processing, then concurrently (on the main thread) get another FxImage. Repeat. Goes about 2x as fast, as you might expect. EXCEPT All goes fine for about 500 frames. Then all of a sudden kernel_task starts to grow memory by leaps and bounds. Before 500 frames, kernel_task is at 3Gb of memory usage, FCP is at about 1.2Gb. Both remain approximately constant Then memory continues to grow for kernel_task, while FCP stays constant (at about 1.2Gb). Over the course of 80 frames or so, kernel_task grows from 3Gb of usage to over 35Gb. Then I get a system error message (not a crash in my plug-in or FCP), that "System has run out of Application Memory". Oy. I read this is related to virtual memory become scarce. Crap. I KNOW I don't have a memory leak in my code (it's code we've used for YEARS and have analyzed it's memory usage quite rigorously). And the code works if the frame retrieval and processing is in the same thread. Of course we allocate and release memory in our plug-in using malloc, but the memory allocations and deallocations are all balanced. I thought maybe there's some issue with concurrent memory allocations by FCP and our plug-in, but malloc and other memory routines are supposed to be thread safe. So perhaps some memory fragmentation? But wouldn't that probably happen even if our processing is happening in line (and in the same thread) as the frame retrieval? Anyone have any ideas? Bueller? Pete _______________________________________________ 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/pete%40revisionfx.com This email sent to pete(a)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) 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

Multicam processing
by Lyndon Hill 15 Sep '17

15 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, I’m not an expert in multicam (or FCPX either), but I heard that it’s possible for a plugin to be applied to a multicam clip. From what they were saying, create a multicam clip, drop it on the timeline, drop the filter on the multicam clip and the plugin works on each clip. When I tried this with my plugin it worked on the current angle only. If I cut the multicam clip, then I have to drop the plugin on each section. This is actually what I would expect to happen. I don’t see anything in the FxPlug API that supports the action as described to me. thanks in advance Lyndon _______________________________________________ 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

Question about growing memory problem with our plug-in
by Peter Litwinowicz 14 Sep '17

14 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: Question about growing memory problem with our plug-in User-agent: Microsoft-MacOutlook/14.7.7.170905 I'm having one heck of a time with my analysis pass plug-in that we're creating. If I get an FxImage, copy the image to my own memory, dealloc the FxImage, then process, then get another FxImage, copy, deallocate, then process, in the same thread… then all goes fine. Well our analysis works about as fast as a CPU memory fetch of an FxImage, so I figured I would get images on the main thread, and process on another thread. So now I get an FxImage then copy, then "throw" over to another thread for processing, then concurrently (on the main thread) get another FxImage. Repeat. Goes about 2x as fast, as you might expect. EXCEPT All goes fine for about 500 frames. Then all of a sudden kernel_task starts to grow memory by leaps and bounds. Before 500 frames, kernel_task is at 3Gb of memory usage, FCP is at about 1.2Gb. Both remain approximately constant Then memory continues to grow for kernel_task, while FCP stays constant (at about 1.2Gb). Over the course of 80 frames or so, kernel_task grows from 3Gb of usage to over 35Gb. Then I get a system error message (not a crash in my plug-in or FCP), that "System has run out of Application Memory". Oy. I read this is related to virtual memory become scarce. Crap. I KNOW I don't have a memory leak in my code (it's code we've used for YEARS and have analyzed it's memory usage quite rigorously). And the code works if the frame retrieval and processing is in the same thread. Of course we allocate and release memory in our plug-in using malloc, but the memory allocations and deallocations are all balanced. I thought maybe there's some issue with concurrent memory allocations by FCP and our plug-in, but malloc and other memory routines are supposed to be thread safe. So perhaps some memory fragmentation? But wouldn't that probably happen even if our processing is happening in line (and in the same thread) as the frame retrieval? Anyone have any ideas? Bueller? Pete _______________________________________________ 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

Accessing parameter widgets
by Lyndon Hill 13 Sep '17

13 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi, When I use [FxParameterCreationAPI_v4 addPushButtonWithName:@“Generate” …] the push button gets placed on a line in the filter parameters with a label as depicted below: Generate [Generate] How can I change the first label to something else ? e.g. Important Initialisation [Generate] Also, I was wondering if it is possible to access menu entries from [FxParameterCreationAPI addPopupMenuWithName:…] in order to enable/disable certain options ? Or are these things only possible through custom UI ? Many thanks in advance, Lyndon Hill _______________________________________________ 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: Pro-apps-dev Digest, Vol 14, Issue 18 -[FxCustomParameterActionAPI currentFxTime:]
by Darrin Cardani 13 Sep '17

13 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com I think this is a notational issue and a little bit of sloppiness on my part. When writing an Objective-C method name, a colon indicates that’s where a parameter goes. If you look at our documentation for, say, NSArray, you’ll see that every method that takes a parameter ends in a colon or has parts of the name separated by colons. <https://developer.apple.com/documentation/foundation/nsarray?language=objc <https://developer.apple.com/documentation/foundation/nsarray?language=objc>> For example, there’s [-NSArray initWithArray:] and [-NSArray initWithArray:copyItems:]. I was a little sloppy in that I wrote about the FxCustomParameterActionAPI, but I should have actually written FxCustomParameterActionAPI_v3, which does contain the -currentFxTime: method. This method takes a pointer to an FxTime and returns void rather than the older method which simply returns a double representing the frame number. Sorry for any confusion I may have caused! Darrin > On Sep 13, 2017, at 6:13 AM, Dieter Becker <dieterdavebecker(a)gmail.com> wrote: > > Hi Darrin, > > you mention and I quote >> 1) You can get the current playhead time by using the >> -[FxCustomParameterActionAPI currentFxTime:] method. > > A) The FxCustomParameterActionAPI does not have a currentFxTime - only a > currentTime which is very diff. from currentFxTime > B) Notice the little colon after currentFxTime in your answer. It is missing > a parameter. The method cannot be called like that. It needs a parameter > which makes not sense when getting a value from a method > > I wrote another mail regarding this possible bug… Could you please provide a > workaround, thx > > — Dieter > >> On 19. May 2017, at 21:00, pro-apps-dev-request(a)lists.apple.com >> <mailto:pro-apps-dev-request@lists.apple.com> wrote: >> >> Send Pro-apps-dev mailing list submissions to >> pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.apple.com/mailman/listinfo/pro-apps-dev >> or, via email, send a message with subject or body 'help' to >> pro-apps-dev-request(a)lists.apple.com >> >> You can reach the person managing the list at >> pro-apps-dev-owner(a)lists.apple.com >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Pro-apps-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: FCPX current playhead and identifying a clip in FxPlug >> (Darrin Cardani) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 19 May 2017 11:15:04 -0700 >> From: Darrin Cardani <dcardani(a)apple.com> >> To: Daniel Walz <daniel(a)filmstro.com> >> Cc: pro-apps-dev <pro-apps-dev(a)lists.apple.com> >> Subject: Re: FCPX current playhead and identifying a clip in FxPlug >> Message-ID: <0E688182-B6AB-4B13-97B7-C9F926F2D9CE(a)apple.com> >> Content-Type: text/plain; charset="utf-8" >> >> Daniel, >> >> You mention that you are working on an audio generator and that you’ve >> written an FxGenerator. It’s not clear what you’re trying to accomplish, but >> FxPlug doesn’t currently support audio reading or writing at all. To answer >> your questions: >> >> 1) You can get the current playhead time by using the >> -[FxCustomParameterActionAPI currentFxTime:] method. >> >> 2) The XML should contain the UUID of your generator. You may have to decode >> the data before you can get to the UUID, though. I haven’t looked at FCPX >> XML in a while. >> >> 3) You cannot hide the controls of anything other than your own generator. >> >> 4) I’ll have to ask about this one. >> >> 5) If your generator is not adding images, you shouldn’t be using a >> generator. That is their sole purpose. Having said that, no, there’s no way >> to tell that a preview is being rendered vs. a regular render, nor is there >> a way to tell which preview is being rendered. >> >> 6) You can right click next to the parameter’s name to bring up the menu >> which will allow you to publish the button. It’s a little confusing, >> unfortunately. >> >> Darrin >> >>> On May 16, 2017, at 7:51 AM, Daniel Walz <daniel(a)filmstro.com> wrote: >>> >>> Dear fellow developers, >>> >>> currently I am working on an audio generator plugin. So far I created a >>> FxGenerator. But I have a few questions: >>> >>> 1) Is there an API to get the current state of playback, like playing, >>> playhead and selected clip? >>> >>> 2) Is there a way to mark a generator clip so I can recognise it in the XML >>> later on, so I can create a compound clip around the generator and the >>> generated/ingested audio? >>> >>> 3) Can I hide the visual controls in the timeline for transform, trim, >>> distort andCompositing? >>> >>> 4) When I publish the parameters (addFloatSliderWithName), it will only >>> show one dimensional keyframes. What do I have to specify to get a 2-D >>> keyframe (value over time) like e.g. the opacity? >>> >>> 5) Can I display a pictogram in the thumbnails in the timeline? I want >>> something like the "Placeholder" clip. Because our generator is not adding >>> any images, I want to show the user a distinction to video clips (like >>> displaying a note symbol or alike). Is that possible? >>> >>> 6) If I add a button using "addPushButtonWithName", it shows up in motion, >>> but I cannot publish it. Is there a setting I didn't see, or is there a >>> technical reason not to have a button in FCPX? I wanted it to trigger an >>> offline render step. >>> >>> >>> Sorry for that long email, and thanks for all insights, >>> >>> Daniel >>> >>> -- >>> Daniel Walz | Software Developer >>> >>> Filmstro | Music that Moves. >>> >>> www.filmstro.com <http://www.filmstro.com/> | twitter/filmstro >>> <https://twitter.com/filmstro> | vimeo/filmstro <https://vimeo.com/filmstro> >>> _______________________________________________ >>> 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 >> >>

1 0

Re: Pro-apps-dev Digest, Vol 14, Issue 18 -[FxCustomParameterActionAPI currentFxTime:]
by Dieter Becker 13 Sep '17

13 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=lSkXNQwT8l+IC/kTDsKVHwtGVcqzeUYIgIzvuRQ7tG4=; b=TkneXvJW/dje99g1x7nrTruuA+OCbMiOENtPCJGFfPiIL2fmnsYaR6ArSBP636wteO zDtNEj+5UD2Be0Y7AZrCRCdIQVK7lxcEh0TGtJOYoKOc9voXyWNF3RxOPkjNk/fg7cPz ufgVg6vMqtozufpXa5xpDXs7DPfmfxnivgQv1v2lQq0PnhcJEyiypLNsQ6YyCV+hwVvo f3dAsruwOzbPrXYCwKD5il+8S0+2BwpQVOCjekbSpsTekPg69hT/0btBKHM4kQXo/Wpz /2MCXCs3lVKtx7z/D1qbjIPkzxlBax8e+U+x2ewkyLrDk32I/o5iHFiaOJwD1i9rCdSJ sf1w== Hi Darrin, you mention and I quote > 1) You can get the current playhead time by using the > -[FxCustomParameterActionAPI currentFxTime:] method. A) The FxCustomParameterActionAPI does not have a currentFxTime - only a currentTime which is very diff. from currentFxTime B) Notice the little colon after currentFxTime in your answer. It is missing a parameter. The method cannot be called like that. It needs a parameter which makes not sense when getting a value from a method I wrote another mail regarding this possible bug… Could you please provide a workaround, thx — Dieter > On 19. May 2017, at 21:00, pro-apps-dev-request(a)lists.apple.com wrote: > > Send Pro-apps-dev mailing list submissions to > pro-apps-dev(a)lists.apple.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.apple.com/mailman/listinfo/pro-apps-dev > or, via email, send a message with subject or body 'help' to > pro-apps-dev-request(a)lists.apple.com > > You can reach the person managing the list at > pro-apps-dev-owner(a)lists.apple.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pro-apps-dev digest..." > > > Today's Topics: > > 1. Re: FCPX current playhead and identifying a clip in FxPlug > (Darrin Cardani) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 19 May 2017 11:15:04 -0700 > From: Darrin Cardani <dcardani(a)apple.com> > To: Daniel Walz <daniel(a)filmstro.com> > Cc: pro-apps-dev <pro-apps-dev(a)lists.apple.com> > Subject: Re: FCPX current playhead and identifying a clip in FxPlug > Message-ID: <0E688182-B6AB-4B13-97B7-C9F926F2D9CE(a)apple.com> > Content-Type: text/plain; charset="utf-8" > > Daniel, > > You mention that you are working on an audio generator and that you’ve > written an FxGenerator. It’s not clear what you’re trying to accomplish, but > FxPlug doesn’t currently support audio reading or writing at all. To answer > your questions: > > 1) You can get the current playhead time by using the > -[FxCustomParameterActionAPI currentFxTime:] method. > > 2) The XML should contain the UUID of your generator. You may have to decode > the data before you can get to the UUID, though. I haven’t looked at FCPX XML > in a while. > > 3) You cannot hide the controls of anything other than your own generator. > > 4) I’ll have to ask about this one. > > 5) If your generator is not adding images, you shouldn’t be using a > generator. That is their sole purpose. Having said that, no, there’s no way > to tell that a preview is being rendered vs. a regular render, nor is there a > way to tell which preview is being rendered. > > 6) You can right click next to the parameter’s name to bring up the menu > which will allow you to publish the button. It’s a little confusing, > unfortunately. > > Darrin > >> On May 16, 2017, at 7:51 AM, Daniel Walz <daniel(a)filmstro.com> wrote: >> >> Dear fellow developers, >> >> currently I am working on an audio generator plugin. So far I created a >> FxGenerator. But I have a few questions: >> >> 1) Is there an API to get the current state of playback, like playing, >> playhead and selected clip? >> >> 2) Is there a way to mark a generator clip so I can recognise it in the XML >> later on, so I can create a compound clip around the generator and the >> generated/ingested audio? >> >> 3) Can I hide the visual controls in the timeline for transform, trim, >> distort andCompositing? >> >> 4) When I publish the parameters (addFloatSliderWithName), it will only show >> one dimensional keyframes. What do I have to specify to get a 2-D keyframe >> (value over time) like e.g. the opacity? >> >> 5) Can I display a pictogram in the thumbnails in the timeline? I want >> something like the "Placeholder" clip. Because our generator is not adding >> any images, I want to show the user a distinction to video clips (like >> displaying a note symbol or alike). Is that possible? >> >> 6) If I add a button using "addPushButtonWithName", it shows up in motion, >> but I cannot publish it. Is there a setting I didn't see, or is there a >> technical reason not to have a button in FCPX? I wanted it to trigger an >> offline render step. >> >> >> Sorry for that long email, and thanks for all insights, >> >> Daniel >> >> -- >> Daniel Walz | Software Developer >> >> Filmstro | Music that Moves. >> >> www.filmstro.com <http://www.filmstro.com/> | twitter/filmstro >> <https://twitter.com/filmstro> | vimeo/filmstro <https://vimeo.com/filmstro> >> _______________________________________________ >> 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 > >

1 0