September 2017 - Pro-apps-dev

Re: analysis pass question
by Peter Litwinowicz 11 Sep '17

11 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: analysis pass question User-agent: Microsoft-MacOutlook/14.7.6.170621 Yeah, I'm giving up on this one. ;-( I tried setting to every openGL context I've seen (I see up to 6 that FCP/Motion sets before renderOutput is called… I have 2 GPUs on a dual D700 Mac Pro). No luck. Setting it to one I've made doesn't seem very likely to work Darrin. It seems that the engine down deep is selecting one, not choosing the current openGL context. Can you verify? Pete From: Roman Kudinov <roman.kudinov(a)novelapp.com> Date: Sunday, September 10, 2017 at 12:30 AM To: <pro-apps-dev(a)lists.apple.com>, Peter Litwinowicz <pete(a)revisionfx.com>, Darrin Cardani <dcardani(a)apple.com> Subject: Re: analysis pass question Peter, Darrin, I used to experience exactly the same problem. I tried to create OpenGL context in a working thread, but [... getInputTexture] failed (don't remember exactly either with an error code or with empty black textures) all the same. I also tried to use shared OpenGL contexts, but I'm not experienced with it and I don't know either it doesn't work or I just used them incorrectly. Anyway I stopped trying cause my processing is written using OpenCL through OpenCV and it doesn't support multiple contexts which is required by plugins workflow. So I ended up with using [... getBitmap] method. However if you succeed some way with this, please let me know. Probably it is a matter of using shared contexts or setting context properly. > Pete, > > Yeah, I can see the dilemma you’re facing. Can you create your own OpenGL > context before calling into the temporal image API? If you do, what happens? > > Darrin > >> On Sep 8, 2017, at 2:08 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: >> >> Hey Darrin, et al., >> >> So I'm writing a plugin that is doing an analysis pass on a sequence. I do >> this in response to a user clicking a UI button in our plug-in interface. >> >> When I get CPU memory images using [FxTemporalImageAPI getBitmap] >> everything works just fine. >> >> However, if I try to get GPU texture, using [FxTemporalImageAPI >> getInputTexture], then I can't get the bits because the current OpenGL >> context is not set up. If I call [FxTexture textureID] and [FxTexture >> getTextureCoords], etc. I get the proper values. Calling –bind or –enable >> doesn't work either. >> >> Darrin, is there a way I can successfully use GPU textures if I'm not in >> –renderOutput? I presume I would need the OpenGL context and set the current >> context to that, but that is not something I've been able to successfully >> retrieve. >> >> 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

Re: FXPlug unregistering
by Peter Litwinowicz 11 Sep '17

11 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: FXPlug unregistering User-agent: Microsoft-MacOutlook/14.7.6.170621 Hard to file a bug when you don't know when/where/how it's happening. I know that doesn't help you much Darrin, but submitting a project isn't going to help if I can't tell you when I think it's happening. No rhyme or reason, and it's not very often. Pete From: Pro-apps-dev <pro-apps-dev-bounces+pete=revisionfx.com(a)lists.apple.com> on behalf of Darrin Cardani <dcardani(a)apple.com> Date: Monday, September 11, 2017 at 10:17 AM To: <fnelson(a)clemuniversity.com> Cc: <pro-apps-dev(a)lists.apple.com> Subject: Re: FXPlug unregistering This has been an ongoing issue we’ve been trying to isolate. If you could file a bug report with an example project, that would be enormously helpful in figuring out what’s going wrong. Same to anyone else seeing this. We need more data! Darrin > On Sep 11, 2017, at 9:44 AM, fnelson(a)clemuniversity.com wrote: > > I'm having an issue while testing my plugin where the FXPlug seems to > occasionally unregister itself. I copied my compiled fxplug .app to my > Applications folder and run: > > pluginkit -a testFXPlug.app/Contents/PlugIns/* in terminal. > > I open Motion, create the motion effect and everything works perfectly > in FCPX... for a while. Then it might be after a restart or just after a > few hours, FCPX won't see it anymore. Has anyone else experienced this? > Also, can anyone give me ideas for the best way to debug an FXPlug > plugin? Thanks so much!! > > Caroline > _______________________________________________ > 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/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

Re: FXPlug unregistering
by Darrin Cardani 11 Sep '17

11 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com This has been an ongoing issue we’ve been trying to isolate. If you could file a bug report with an example project, that would be enormously helpful in figuring out what’s going wrong. Same to anyone else seeing this. We need more data! Darrin > On Sep 11, 2017, at 9:44 AM, fnelson(a)clemuniversity.com wrote: > > I'm having an issue while testing my plugin where the FXPlug seems to > occasionally unregister itself. I copied my compiled fxplug .app to my > Applications folder and run: > > pluginkit -a testFXPlug.app/Contents/PlugIns/* in terminal. > > I open Motion, create the motion effect and everything works perfectly > in FCPX... for a while. Then it might be after a restart or just after a > few hours, FCPX won't see it anymore. Has anyone else experienced this? > Also, can anyone give me ideas for the best way to debug an FXPlug > plugin? Thanks so much!! > > Caroline > _______________________________________________ > 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 unregistering
by Paul Miller 11 Sep '17

11 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=reply-to:subject:to:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=IEq+n38T/H6PB4O2kpsLU8tJkBk6ZvepVy+283V40ag=; b=rRtr5o1UbI2CqFbUE2dDRGG9OvDYEclE1LSDSkh29txtCXz3BdFbZBfUvq2pO7AZF0 Ic8+KlUqQgejxxEd99khuaSApbUdYNcajW8wBHCDtNjjm8rJErxM3RJpAAvMcLTyAcrv uHwwqGaAk6yRtkpWjxURaOXEBL9wrtENLdp0fREaWG9nYeKK9yf0VPLphG7MNzGQ0UjF g51yczAZSz6/WgHCZvrUOsW5ZY4dGtebqo5Q+pudntqEKN9VfG5tL9pnh/GjHETPMwW4 q7SI3PL20z7TnhjAHXSLXZzf1hkG3Pva/FEN/2QuygQMbYyiuyHCMkzjnXTocgdfZ5b+ TjBA== Organization: FXTECH User-agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 On 9/11/2017 11:47 AM, Peter Litwinowicz wrote: Can't seem to figure out when it happens, so hard to file a bug report. Pete Date: Monday, September 11, 2017 at 9:44 AM To: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> Subject: FXPlug unregistering I'm having an issue while testing my plugin where the FXPlug seems to occasionally unregister itself. I copied my compiled fxplug .app to my Applications folder and run: pluginkit -a testFXPlug.app/Contents/PlugIns/* in terminal. I open Motion, create the motion effect and everything works perfectly in FCPX... for a while. Then it might be after a restart or just after a few hours, FCPX won't see it anymore. Has anyone else experienced this? Also, can anyone give me ideas for the best way to debug an FXPlug plugin? Thanks so much!! Caroline _______________________________________________ Do not post admin requests to the list. They will be ignored. 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 <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/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 Yes, I've been experiencing this as well. SEEMS to have started with Mac OS 10.12. Remember the good ole' days when hosts would just scan for shared libraries in a known location when they startup up? 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 <fnelson(a)clemuniversity.com <mailto:fnelson@clemuniversity.com>> Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com <mailto:Pro-apps-dev@lists.apple.com>)

1 0

Re: FXPlug unregistering
by Peter Litwinowicz 11 Sep '17

11 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: FXPlug unregistering User-agent: Microsoft-MacOutlook/14.7.6.170621 Yes, I've been experiencing this as well. SEEMS to have started with Mac OS 10.12. Can't seem to figure out when it happens, so hard to file a bug report. Pete From: Pro-apps-dev <pro-apps-dev-bounces+pete=revisionfx.com(a)lists.apple.com> on behalf of <fnelson(a)clemuniversity.com> Date: Monday, September 11, 2017 at 9:44 AM To: <pro-apps-dev(a)lists.apple.com> Subject: FXPlug unregistering I'm having an issue while testing my plugin where the FXPlug seems to occasionally unregister itself. I copied my compiled fxplug .app to my Applications folder and run: pluginkit -a testFXPlug.app/Contents/PlugIns/* in terminal. I open Motion, create the motion effect and everything works perfectly in FCPX... for a while. Then it might be after a restart or just after a few hours, FCPX won't see it anymore. Has anyone else experienced this? Also, can anyone give me ideas for the best way to debug an FXPlug plugin? Thanks so much!! Caroline _______________________________________________ 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

FXPlug unregistering
by fnelson＠clemuniversity.com 11 Sep '17

11 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= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=2ZkHgZC75ZJhRn4Psrd/D+CGl1XNF vmADmSP7FWzlbM=; b=JbusoL7xcINbtCjq65IOShEaD8aTgaQ5w8BENvKHPEY1A 9nz4TfAnEc/lt88vGT6l53jG0aF4acHVaf3pB7WmhXNWcWVUq0b1Noq+m0100QaZ 7h3cOSY9Qrk1YL1G2RKZk1Q6DEGRQwobw5Ru2YaAqW5pbuPaTT07YtDadIdXzwXN zH5hSnyDdFe03vANOCRe5g9dM8PsK7UVh7dDM9BmpxXxehfb8xnM9fK1gH+/DJz6 PaRipUgvyQIxlgDXywpVTpeEL7InUiTXTLqU0tf9dXrPcPFUM+oDlrsrBKkc7/SN qgc3OcscCEbgXp2eIfO2NnRYaIPT1WehoLRTYqFfA== I'm having an issue while testing my plugin where the FXPlug seems to occasionally unregister itself. I copied my compiled fxplug .app to my Applications folder and run: pluginkit -a testFXPlug.app/Contents/PlugIns/* in terminal. I open Motion, create the motion effect and everything works perfectly in FCPX... for a while. Then it might be after a restart or just after a few hours, FCPX won't see it anymore. Has anyone else experienced this? Also, can anyone give me ideas for the best way to debug an FXPlug plugin? Thanks so much!! Caroline _______________________________________________ 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: analysis pass question
by Roman Kudinov 10 Sep '17

10 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Peter, Darrin, Pete, Yeah, I can see the dilemma you’re facing. Can you create your own OpenGL context before calling into the temporal image API? If you do, what happens? Darrin On Sep 8, 2017, at 2:08 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: Hey Darrin, et al., So I'm writing a plugin that is doing an analysis pass on a sequence. I do this in response to a user clicking a UI button in our plug-in interface. When I get CPU memory images using [FxTemporalImageAPI getBitmap] everything works just fine. However, if I try to get GPU texture, using [FxTemporalImageAPI getInputTexture], then I can't get the bits because the current OpenGL context is not set up. If I call [FxTexture textureID] and [FxTexture getTextureCoords], etc. I get the proper values. Calling –bind or –enable doesn't work either. Darrin, is there a way I can successfully use GPU textures if I'm not in –renderOutput? I presume I would need the OpenGL context and set the current context to that, but that is not something I've been able to successfully retrieve. 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 I used to experience exactly the same problem. I tried to create OpenGL context in a working thread, but [... getInputTexture] failed (don't remember exactly either with an error code or with empty black textures) all the same. I also tried to use shared OpenGL contexts, but I'm not experienced with it and I don't know either it doesn't work or I just used them incorrectly. Anyway I stopped trying cause my processing is written using OpenCL through OpenCV and it doesn't support multiple contexts which is required by plugins workflow. So I ended up with using [... getBitmap] method. However if you succeed some way with this, please let me know. Probably it is a matter of using shared contexts or setting context properly.

1 0

Re: analysis pass question
by Darrin Cardani 09 Sep '17

09 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Pete, Yeah, I can see the dilemma you’re facing. Can you create your own OpenGL context before calling into the temporal image API? If you do, what happens? Darrin > On Sep 8, 2017, at 2:08 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > Hey Darrin, et al., > > So I'm writing a plugin that is doing an analysis pass on a sequence. I do > this in response to a user clicking a UI button in our plug-in interface. > > When I get CPU memory images using [FxTemporalImageAPI getBitmap] everything > works just fine. > > However, if I try to get GPU texture, using [FxTemporalImageAPI > getInputTexture], then I can't get the bits because the current OpenGL > context is not set up. If I call [FxTexture textureID] and [FxTexture > getTextureCoords], etc. I get the proper values. Calling –bind or –enable > doesn't work either. > > Darrin, is there a way I can successfully use GPU textures if I'm not in > –renderOutput? I presume I would need the OpenGL context and set the current > context to that, but that is not something I've been able to successfully > retrieve. > > 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

Re: Guidelines for FxDynamicParameter
by Ben Syverson 08 Sep '17

08 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/simple; d=bensyverson.com; s=bensyverson; t=1504912541; bh=aom6xLxl6q8pty8NiBKRhO5XbmNqxHG5IRq5ud3iSYY=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=DT4ugwKpui4nW2gfxoRA3z4N0Ai5sedD/dicvphxacFlCe5ghXgzyT9PS1Gz/hVxK F/n7GLD8tf1W/W9wuZJG2RGxL5lZFYsdK5ZLEjRCBEBbrLBLGGTpQTMmDR+776q6dw bBL6ttwk41otJe5dGKLgAarRorL66KCH724JczTk7ZKEQoeaZe+ckGgtIpxHTWY30H 6EoLH6kIVZyC94n+NhSnX+Mn+RS1iJDuZZ25ERcDELVqkYNcqziV2JFmgSagvxYKUr Qy2VxW2V9Ny8g0gvvGaSjihNuqGuZWtL7EALLOGHK1ELGsiV+81rgAypZyVO/jlpCg c1fTFShMTkniA== Darrin, Okay, for #3, that sounds good, although it’s counter-intuitive that the index of the parameter list doesn’t correspond to the UI order. Perhaps that should be reflected in the docs? #1 is now rdar://34341983 <rdar://34341983> I was able to resolve the crashing bug in #2 while removing parameters. It turns out, you must remove the parameters from a group before you remove the group itself. I don’t think that’s in the docs either, but it probably should be. It would also be helpful as a convenience if removing the group would simply remove all of the group’s parameters rather than crashing. Thanks again for all your help! Ben > On Sep 8, 2017, at 11:18, Darrin Cardani <dcardani(a)apple.com> wrote: > > Ben, > > Thanks for the explanation. Both #1 and #2 sound like bugs to me. Please file > Radars. I admit I’m surprised by the first one! Very strange! > > For #3, that sounds normal to me. The parameter and ID associations are > stored in something like a C++ map or an Objective-C dictionary, so their > order when iterating may not match the order you see them in the UI. The host > app does add up to 3 additional parameters. The Mix parameter, as you’ve > discovered, and it may also add 2 hidden checkboxes. One says that points > should be in the input image space vs. the output image space, and the other > says that point parameters have their Y-values flipped. These are for legacy > plug-ins. At some point we switched how we represent points and needed to add > these flags so that older instances of plug-ins would render how they used to > and newer instances would render the new way. You shouldn’t ever touch them. > (In fact, I’m not sure if we support those older versions anymore, so we > might even be able to remove them!) They are harmless. > > Darrin > >> On Sep 7, 2017, at 7:21 PM, Ben Syverson <ben(a)bensyverson.com >> <mailto:ben@bensyverson.com>> wrote: >> >> Darrin, >> >> Yeah, this is what I expected for FCPX, and for that reason, I don’t think >> my FCPX templates will expose any parameters other than the “Show Editor” >> button. >> >> As for my plugin: it’s conceptually similar to Conduit. The user will open >> my Editor window, where they can add and remove elements that have >> parameters. >> >> When the Editor is closed, my plugin will compare the old param list to the >> new one. If the IDs of the params haven’t changed, the plugin will use the >> FxParameterSettingAPI to update the param values. If the list has changed >> (params added or deleted), my plugin will remove all of the previous dynamic >> parameters, create the new ones, and set their values. >> >> The three issues I’m running into currently are: >> >> 1) I’m creating parameter subgroups dynamically, and at the end of every >> group, the same Mix slider is repeated: >> >> <Screenshot 2017-09-07 21.16.26.png> >> >> 2) In my -removeAllDynamicParameters method, calling -removeParameter: on >> the FxDynamicParameterAPI is an instant crash. I’m calling it on the main >> thread, between calls to the action API (-startAction: and -endAction:) >> >> <Screenshot 2017-09-07 21.18.33.png> >> >> 3) When I attempt to iterate over the parameters using -parameterIDAtIndex:, >> I get strange results. My dynamic parameters are first, then come the two I >> create in -addParameters, then come two parameters I didn’t create (10001 >> and 10002, Mix and ???). >> >> Id at index 0: 46 // First dynamic param >> Id at index 1: 49 >> Id at index 2: 50 >> (snip…) >> Id at index 15: 75 >> Id at index 16: 800 // Show Editor button >> Id at index 17: 808 // Custom param to store project data >> Id at index 18: 10001 // Mix >> Id at index 19: 10002 // ?? >> >> Any insights would be greatly appreciated! >> >> Ben >> >> >>> On Sep 7, 2017, at 12:15, Darrin Cardani <dcardani(a)apple.com >>> <mailto:dcardani@apple.com>> wrote: >>> >>> Oh - one other thing just occurred to me. Are you looking at this in Motion >>> or FCPX. While FCPX will properly read and create the dynamic parameters >>> stored in a template, the template will not be re-saved with new parameters >>> if the user performs an action that makes the parameter list change while >>> in FCPX. >>> >>> So, let’s say you have an “Add color” button in your plug-in’s UI. In >>> Motion, the user can press “Add Color” several times to add more color >>> parameters to the parameter list. When they save the document, all the >>> colors they added will be saved. When they re-open the document, Motion >>> will show all the colors they added. >>> >>> Now let’s say the user makes a Final Cut Effect in Motion and they add 2 >>> colors. They publish all the parameters, including the 2 extra colors and >>> save the template. Now they go into FCPX and apply the effect to a clip. >>> They should see all the parameters, including the 2 extra colors. >>> >>> At this point, if the user presses the “Add Color” button, the new 3rd >>> color will be added to the inspector and your plug-in will be aware of it. >>> But if they quit and re-open their project, the 3rd color will be gone >>> because FCPX does not update the template file. (And it would be bad if it >>> did, because other projects using that template would get updated, which is >>> probably not what the user wants.) >>> >>> Darrin >>> >>>> On Sep 7, 2017, at 10:00 AM, Darrin Cardani <dcardani(a)apple.com >>>> <mailto:dcardani@apple.com>> wrote: >>>> >>>> Ben, >>>> >>>> I’m a little lost as to what you’re trying to do. Can you walk me through >>>> a first use of your plug-in and then a second use of it? For dynamic >>>> parameters your plug-in added before the user saved, your plug-in >>>> shouldn’t have to create them on document open. They should be created for >>>> you by the host app. If you’re not seeing that, let me know. (But they >>>> won’t be created until after -addParameters is called.) >>>> >>>> The FxRetrievalAPIs should be available during -addParameters. I don’t >>>> know that we’ve ever tested whether they work properly during that time, >>>> though! (One doesn’t usually need to retrieve parameter values when you >>>> just created the parameter in the same function and set its value.) >>>> >>>> Darrin >>>> >>>>> On Sep 6, 2017, at 6:44 PM, Ben Syverson <ben(a)bensyverson.com >>>>> <mailto:ben@bensyverson.com>> wrote: >>>>> >>>>> Darrin, >>>>> >>>>> Okay, that makes some sense. Thank you! >>>>> >>>>> My second hidden parameter stores what is essentially a JSON >>>>> representation of the param array, so that can be used to create the >>>>> parameters. >>>>> >>>>> But in order to create the parameters in -addParameters, I would need to >>>>> retrieve that JSON value from the hidden param. Is it possible to use >>>>> FxParameterRetrievalAPI within -addParameters, and if so, what time >>>>> should I pass in? >>>>> >>>>> Or should I add the dynamic parameters outside of -addParameters? >>>>> Currently I’m checking to see if they exist during -renderOutput: and if >>>>> not, I’m creating them on the main thread. But that feels hacky. >>>>> >>>>> Thanks for your help! >>>>> >>>>> Ben >>>>> >>>>> >>>>>> On Sep 6, 2017, at 11:50, Darrin Cardani <dcardani(a)apple.com >>>>>> <mailto:dcardani@apple.com>> wrote: >>>>>> >>>>>> Ben, >>>>>> >>>>>> This is one of the more confusing aspects of our apps. When the user >>>>>> tells the app to add a plug-in to some footage, whether via a pop-up >>>>>> menu, dragging and dropping, cut/copy and pasting, or selecting it in a >>>>>> list and pressing the “Apply” button, the app first creates an instance >>>>>> of the plug-in and puts it on the drag & drop pasteboard. This is where >>>>>> your -addParameters method will get called. >>>>>> >>>>>> The application will then create a copy of what’s on the pasteboard and >>>>>> apply that copy to the footage. When creating a copy, it will call your >>>>>> plug-in’s -initWithAPIManager: method, but won’t call -addParameters. >>>>>> Since it already has an instance of the plug-in, it just copies the >>>>>> parameters itself. This means that anything you set up in -addParameters >>>>>> that isn’t a parameter will not actually make it into the instance that >>>>>> the user is actually using. >>>>>> >>>>>> I believe the reason we do this is so we have a single path in our code >>>>>> that all plug-in instantiation goes through, regardless of how the user >>>>>> interacted with the app. The reason we make a copy instead of just >>>>>> applying the one on the pasteboard is because the user can do a cut and >>>>>> paste or copy and paste multiple times. So we have to leave one on the >>>>>> pasteboard for that scenario. >>>>>> >>>>>> So I see a few ways you could deal with this: >>>>>> Set up your array in -initWithAPIManager:. You know the first 2 >>>>>> parameters are always the same and have the same IDs, so just add them >>>>>> to your array there. >>>>>> If you have a naming scheme that allows you to discern parameters or >>>>>> their types, you can iterate over the parameters you have and call >>>>>> [-FxDynamicParameterAPI parameter:name:] to get the name of each >>>>>> parameter and figure out its type from that, and do away with the array. >>>>>> Keep a 3rd hidden parameter that is your array of parameters. Then it >>>>>> will get copied when your parameters get copied. >>>>>> Let me know if any of those will work. Generally, if your plugin has >>>>>> data that can’t be generated at runtime, you need to stick it into a >>>>>> parameter for the app to save it. If you don’t do that, how are you >>>>>> planning on regenerating the list of the dynamic parameters when the >>>>>> user opens a saved document? >>>>>> >>>>>> Darrin >>>>>> >>>>>>> On Sep 6, 2017, at 6:53 AM, Ben Syverson <ben(a)bensyverson.com >>>>>>> <mailto:ben@bensyverson.com>> wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I’m working on a project that uses dynamic parameter creation, and >>>>>>> running into issues. >>>>>>> >>>>>>> I have two params which are always present (a “Show Editor” button and >>>>>>> a hidden custom parameter to store a project file). I’m adding these in >>>>>>> addParameters. >>>>>>> >>>>>>> In order to keep track of my parameter list, I’m using an >>>>>>> NSMutableArray property on the instance, self.paramsByIndex. So in >>>>>>> addParameters, I’m adding my first two parameters to my array. >>>>>>> >>>>>>> The first problem is that when I’m updating the paramList, my first two >>>>>>> params aren’t there. Is addParameters called on a separate instance of >>>>>>> my FxPlug? >>>>>>> >>>>>>> It’s making it really difficult to keep my list of parameters in sync >>>>>>> with what’s returned from the dynamic API (parameterIDAtIndex:, etc). >>>>>>> >>>>>>> Are there any guidelines for how & when to manage dynamic parameters? >>>>>>> At this point, I’m printing NSLogs to try to understand which of my >>>>>>> FxPlug methods are called in what order, and whether they’re all coming >>>>>>> from the same instance. >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>>> Ben >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>>> <https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com> >>>>>>> >>>>>>> This email sent to dcardani(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 >>>> <mailto:Pro-apps-dev@lists.apple.com>) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com >>>> <https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com> >>>> >>>> This email sent to dcardani(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/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

analysis pass question
by Peter Litwinowicz 08 Sep '17

08 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Thread-topic: analysis pass question User-agent: Microsoft-MacOutlook/14.7.6.170621 Hey Darrin, et al., So I'm writing a plugin that is doing an analysis pass on a sequence. I do this in response to a user clicking a UI button in our plug-in interface. When I get CPU memory images using [FxTemporalImageAPI getBitmap] everything works just fine. However, if I try to get GPU texture, using [FxTemporalImageAPI getInputTexture], then I can't get the bits because the current OpenGL context is not set up. If I call [FxTexture textureID] and [FxTexture getTextureCoords], etc. I get the proper values. Calling –bind or –enable doesn't work either. Darrin, is there a way I can successfully use GPU textures if I'm not in –renderOutput? I presume I would need the OpenGL context and set the current context to that, but that is not something I've been able to successfully retrieve. 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