September 2017 - Pro-apps-dev

Re: FXPlug unregistering
by Rainer Standke 12 Sep '17

12 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com If you are developing with XCode- and I think you should be - then debugging is quite easy. Once you have compiled and done the usual voodoo, you launch the host app, and attach the Debugger to it in XCode’s Debug menu. Logging and breaking in your code should work as if this was a stand-alone app. These steps can be achieved with a post-build script - see Post-actions in your build settings in the Scheme editor. Hope this helps, Rainer > On Sep 11, 2017, at 09:44, 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/lists%40standke.com > > This email sent to lists(a)standke.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: analysis pass question
by Darrin Cardani 11 Sep '17

11 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Bummer. OK, then, please file a Radar about that, as well. Darrin > On Sep 11, 2017, at 3:50 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > However, if you create your context in the same share group as one that > we hand you, then any textures we create in our context should be available > in yours. I > > I actually store all the OpenGL contexts you use as current contexts when you > call RenderOutput. Stored 6 of them actually. Tried using each one I had on > my list, no go. > Pete > > From: Darrin Cardani <dcardani(a)apple.com <mailto:dcardani@apple.com>> > Date: Monday, September 11, 2017 at 3:46 PM > To: Peter Litwinowicz <pete(a)revisionfx.com <mailto:pete@revisionfx.com>> > Cc: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> > Subject: Re: analysis pass question > > Pete, > > Yes, at some point we have to create the texture and we need an OpenGL > context for that. We will choose one that we’ve created. However, if you > create your context in the same share group as one that we hand you, then any > textures we create in our context should be available in yours. I didn’t > think about that aspect before, so sorry for not mentioning it sooner. > > BTW, I would love to add an analysis API to FxPlug. As always, I recommend > writing up a Radar detailing what you would want that to look like. Several > developers have expressed interest in such an API, so I think it’s more > likely to get consideration from above. (And if anyone else reading this is > interested in such an API, please also file a Radar about it!) > > Darrin > >> On Sep 11, 2017, at 2:33 PM, Peter Litwinowicz <pete(a)revisionfx.com >> <mailto:pete@revisionfx.com>> wrote: >> >> 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 >> <mailto:roman.kudinov@novelapp.com>> >> Date: Sunday, September 10, 2017 at 12:30 AM >> To: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>>, >> Peter Litwinowicz <pete(a)revisionfx.com <mailto:pete@revisionfx.com>>, Darrin >> Cardani <dcardani(a)apple.com <mailto:dcardani@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 >>>> <mailto:pete@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: clipwell hiding in FCP X
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: clipwell hiding in FCP X User-agent: Microsoft-MacOutlook/14.7.6.170621 Once again Motion and FCP being so different with respect to FxPlus implmentation is getting in my way ;-( Pete From: Darrin Cardani <dcardani(a)apple.com> Date: Monday, September 11, 2017 at 3:41 PM To: Peter Litwinowicz <pete(a)revisionfx.com> Cc: <pro-apps-dev(a)lists.apple.com> Subject: Re: clipwell hiding in FCP X I’m not aware of a way to do this. The problem is that in FCPX drop zone parameters aren't FxPlug parameters, so I don’t see any way to access it. Darrin > On Sep 11, 2017, at 3:23 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > Okay, so I have an image clip well in our plug-in. I can hide/show that param > from within Motion. > > Not so with FCP. Darrin, is there a way I can hide my clipwell param from > within FCP X that perhaps uses some trickery other than setting > kFxParameterFlag_HIDDEN flags on the param? > > Alternatively: is there a way to put a clipwell as part of a group, to be > collapsed (that works in Motion too, but not FCP X). > 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: 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 However, if you create your context in the same share group as one that we hand you, then any textures we create in our context should be available in yours. I I actually store all the OpenGL contexts you use as current contexts when you call RenderOutput. Stored 6 of them actually. Tried using each one I had on my list, no go. Pete From: Darrin Cardani <dcardani(a)apple.com> Date: Monday, September 11, 2017 at 3:46 PM To: Peter Litwinowicz <pete(a)revisionfx.com> Cc: <pro-apps-dev(a)lists.apple.com> Subject: Re: analysis pass question Pete, Yes, at some point we have to create the texture and we need an OpenGL context for that. We will choose one that we’ve created. However, if you create your context in the same share group as one that we hand you, then any textures we create in our context should be available in yours. I didn’t think about that aspect before, so sorry for not mentioning it sooner. BTW, I would love to add an analysis API to FxPlug. As always, I recommend writing up a Radar detailing what you would want that to look like. Several developers have expressed interest in such an API, so I think it’s more likely to get consideration from above. (And if anyone else reading this is interested in such an API, please also file a Radar about it!) Darrin > On Sep 11, 2017, at 2:33 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > 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: analysis pass question
by Darrin Cardani 11 Sep '17

11 Sep '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Pete, Yes, at some point we have to create the texture and we need an OpenGL context for that. We will choose one that we’ve created. However, if you create your context in the same share group as one that we hand you, then any textures we create in our context should be available in yours. I didn’t think about that aspect before, so sorry for not mentioning it sooner. BTW, I would love to add an analysis API to FxPlug. As always, I recommend writing up a Radar detailing what you would want that to look like. Several developers have expressed interest in such an API, so I think it’s more likely to get consideration from above. (And if anyone else reading this is interested in such an API, please also file a Radar about it!) Darrin > On Sep 11, 2017, at 2:33 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > 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 > <mailto:roman.kudinov@novelapp.com>> > Date: Sunday, September 10, 2017 at 12:30 AM > To: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>>, > Peter Litwinowicz <pete(a)revisionfx.com <mailto:pete@revisionfx.com>>, Darrin > Cardani <dcardani(a)apple.com <mailto:dcardani@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 >>> <mailto:pete@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: clipwell hiding in FCP X
by Darrin Cardani 11 Sep '17

11 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. The problem is that in FCPX drop zone parameters aren't FxPlug parameters, so I don’t see any way to access it. Darrin > On Sep 11, 2017, at 3:23 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > Okay, so I have an image clip well in our plug-in. I can hide/show that > param from within Motion. > > Not so with FCP. Darrin, is there a way I can hide my clipwell param from > within FCP X that perhaps uses some trickery other than setting > kFxParameterFlag_HIDDEN flags on the param? > > Alternatively: is there a way to put a clipwell as part of a group, to be > collapsed (that works in Motion too, but not FCP X). > 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

clipwell hiding in FCP X
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: clipwell hiding in FCP X User-agent: Microsoft-MacOutlook/14.7.6.170621 Okay, so I have an image clip well in our plug-in. I can hide/show that param from within Motion. Not so with FCP. Darrin, is there a way I can hide my clipwell param from within FCP X that perhaps uses some trickery other than setting kFxParameterFlag_HIDDEN flags on the param? Alternatively: is there a way to put a clipwell as part of a group, to be collapsed (that works in Motion too, but not FCP X). 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 Ben Syverson 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/simple; d=bensyverson.com; s=bensyverson; t=1505166437; bh=7pHY2lIavPHiIiOlNyPvzGM0L8B0usgIguJWlF1pJWI=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=QMec3lXBe/kUEUnYBAQALQzoXLM7IvxUMOxNe8ZffW4XoG73GGHBDdA8QX3pQXODg TAVChEJBcV2ej8QaiQj7dwbFOd3klEctDHQdi12rOpQurZ2DYb/7YUTadX1ItwjVO8 hQMh07BU1Ll8s79l/iUaz8BW7HxXuTYNzKtJqmQdxty1dQZeS6T/ZZDl11YYvPysKW Aelpw5wFisxOjT4eJzbzLOfjTtA/yJV2u2TG2orBw/JlCyeRLITb+D7Fro8xiXxT6m rYQkNODLRdeszpZUTA0xHflENhxHgb9oVy5uMGZFwONPOmT2XpfUMNAKLPj2WitWZx x6xQAazpNj32g== +1 to the tip about Xcode’s build products directory. My plugin would just not update, and I thought I was going crazy. Finally I figured out that Xcode had created another copy in the build products directory, and Motion was using that version when it loaded. Ben > On Sep 11, 2017, at 16:41, Darrin Cardani <dcardani(a)apple.com> wrote: > > I hear you. Imagine trying to *fix* this bug without knowing when/where/how > it’s happening! > > By coincidence, I just hit this personally and figured out something that > might be useful to others on the list. I installed FxFactory to test a fix in > FCPX and none of the FxFactory plug-ins were loading. Checking “pluginkit > -mAvD -p FxPlug” at the command line revealed that there were 2 copies > loaded. One from /Applications, and one from another disk. I deleted the one > from the other disk and suddenly it started working again. It seems that > there was something off about the one on the other disk and when the OS would > try to load it, it would just silently fail. > > This probably doesn’t fix all instances of this problem, but might be worth > looking into when you hit this while debugging. Xcode, for example, will > sometimes create an all new directory to put your build products in and the > old ones will still be there. Perhaps that’s causing some confusion to the > system, similar to what I just experienced in some cases? > > Darrin > >> On Sep 11, 2017, at 2:32 PM, Peter Litwinowicz <pete(a)revisionfx.com >> <mailto:pete@revisionfx.com>> wrote: >> >> 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 >> <mailto:pro-apps-dev-bounces+pete=revisionfx.com@lists.apple.com>> on behalf >> of Darrin Cardani <dcardani(a)apple.com <mailto:dcardani@apple.com>> >> Date: Monday, September 11, 2017 at 10:17 AM >> To: <fnelson(a)clemuniversity.com <mailto:fnelson@clemuniversity.com>> >> Cc: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@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 >>> <mailto:fnelson@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 >>> <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/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/ben%40bensyverson.com > > This email sent to ben(a)bensyverson.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 I hear you. Imagine trying to *fix* this bug without knowing when/where/how it’s happening! By coincidence, I just hit this personally and figured out something that might be useful to others on the list. I installed FxFactory to test a fix in FCPX and none of the FxFactory plug-ins were loading. Checking “pluginkit -mAvD -p FxPlug” at the command line revealed that there were 2 copies loaded. One from /Applications, and one from another disk. I deleted the one from the other disk and suddenly it started working again. It seems that there was something off about the one on the other disk and when the OS would try to load it, it would just silently fail. This probably doesn’t fix all instances of this problem, but might be worth looking into when you hit this while debugging. Xcode, for example, will sometimes create an all new directory to put your build products in and the old ones will still be there. Perhaps that’s causing some confusion to the system, similar to what I just experienced in some cases? Darrin > On Sep 11, 2017, at 2:32 PM, Peter Litwinowicz <pete(a)revisionfx.com> wrote: > > 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 > <mailto:pro-apps-dev-bounces+pete=revisionfx.com@lists.apple.com>> on behalf > of Darrin Cardani <dcardani(a)apple.com <mailto:dcardani@apple.com>> > Date: Monday, September 11, 2017 at 10:17 AM > To: <fnelson(a)clemuniversity.com <mailto:fnelson@clemuniversity.com>> > Cc: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@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 >> <mailto:fnelson@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 >> <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/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/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=sender:reply-to:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GB2YDnsRz2o+N5dmJZIAbARfwoxnKFUbSA7L7OTlRdo=; b=Irr5npHlYEvobITDW+/iUcKQ+H1hNCeAhgGIQ7EKqOp+wLnx42ddyJKfzSix2Dv/Ng hFSVGzdQ7fHSH0LrBPux6yQtI2FwpkIgs5HiIX4+KZ7zMaK0RVTVqxDO32U3zf52sXnI GY7k4ddse/hRQSHvBpEJaCoTUHj2bhsisbqkoBV8AcD3BAeZ8Ea+9oIW++z5WCK86Ssl Ltg/lUT8YbroaKNrQuKTxsurVys9C1dRPy+Ny24sVbtpTvWDBvK5o8nhGuaHvi+tMBA/ Ss8E4RsdoHa3PhyfMmVvUbMi8eJLgz+ltfns8mu7OAjIM1O7JSl40M/uxIL9UxKcHf7j srxQ== User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 On 9/11/17 4:32 PM, Peter Litwinowicz wrote: Pete Date: Monday, September 11, 2017 at 10:17 AM To: <fnelson(a)clemuniversity.com <mailto:fnelson@clemuniversity.com>> Cc: <pro-apps-dev(a)lists.apple.com <mailto:pro-apps-dev@lists.apple.com>> Subject: Re: FXPlug unregistering Darrin On Sep 11, 2017, at 9:44 AM, fnelson(a)clemuniversity.com <mailto:fnelson@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 <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 to dcardani(a)apple.com <mailto:dcardani@apple.com> _______________________________________________ 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 There is clearly something in 10.12 that is causing FxPlugs to get lost/unregistered. It was working fine in previous MacOS releases. I've found that usually double-clicking on the FxPlug filter app wrapper thing will bring it back. Sometimes it doesn't, and I have to log into another user account and do it. 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. 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 Darrin Cardani <dcardani(a)apple.com <mailto:dcardani@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! Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com <mailto:Pro-apps-dev@lists.apple.com>)

1 0