August 2017 - Pro-apps-dev - lists.apple.com

Phantom slider in FCPX
by Paul Miller 31 Aug '17

31 Aug '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:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=6lapMSyF6ve37K4XooGCIeZxs/TtcGdnRMr1O+mNNT4=; b=WX2WhIjCMEgNNG1JmRl8FAChaR7y/9akne1fTtFlA4H2J0IW08IButw+bxO2FVzOd6 sLxYWDqbngmcFlEkNMggtyfLE/UU8WpWdwZBd7BEl/92IboKlmww747T0pOQ6Ol8BkLU fxYNzNjvH5TIzSjvpICjJiVCaNjWWPSpbGsNnbkG91M7PCSPxIWegR1ciQIZt7vBYvp2 6UTmCm/Odu9GcWpGP6k6KLstptW9zMV6eqsUsz+2qh6BmPAos2eFUxz+SLIJQg5E7oOI IpJPaIaUgDmRK3gBnBxEjuERjZ9BE8dpPq8ffY/V1euV27GnT4Ug4fdekTCnl8CnsXgU JbPA== User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Has anyone else seen this, know what causes it, and how to fix it? _______________________________________________ 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'm using the moef-fiddling technique to get my parameter groups to show up in FCP, as I have done in the past. I've noticed a few of my effects have a phantom slider, with no label, and extremely large values, sometimes appearing as the first parameter in a group. It does not appear in Motion, and it's definitely not being defined by my effect. I note that after dragging the slider around, I am no longer able to remove the effect with the Delete key. I have to use Edit->Remove Effects.

1 0

Re: proper current way to build a new FxPlug?
by Darrin Cardani 28 Aug '17

28 Aug '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Paul, If there’s any way you could file a detailed bug report on this today, that would be enormously helpful to everyone involved (including developers like you!). We have spent a lot of time trying to reproduce and get bugs about these issues filed, and unfortunately, they’re very hard to make happen. That means that our OS developers spend time trying to reproduce them, and if they can’t, they send them back to us as “unable to reproduce”. Any additional information you can provide about what’s happening may give them some hints as to what’s going wrong or where. I’d hate to see a problem like this not get fixed in High Sierra. Darrin > On Aug 27, 2017, at 2:02 PM, Paul Miller <paul(a)fxtech.com> wrote: > > Thanks for the tip Lyndon. That didn't work either. > > Here is something that DID work. I created a whole other user, logged into > that, ran the FxPlug .app, then ran pluginkit -m, and it showed up! Also, > there were more than a page of entries in the pluginkit output. When I'm > logged into my normal user, there are only maybe ten or so! > > So what's going on here? How do I get my normal user account to see all of > the usual pluginkit entries that appear for other, new, users? > > Another note: I noticed that after turning on code-signing for the template > plugin, the signing failed. check-signature explains that an embedded > framework: > > DFT FxPlug.app/: a sealed resource is missing or invalid > In subcomponent: .../DFT FxPlug.app/Contents/PlugIns/DFT > FxPlug.pluginkit/Contents/Frameworks/FxPlug.framework > NO > > FxPlug.framework is malformed, at least according to the ever-changing > code-signing rules in Sierra. How am I supposed to rectify this? > > > On 8/27/17 9:01 AM, Lyndon Hill wrote: >> Hi Paul, >> >> I had a similar experience. I don’t think I nailed down a series of steps to >> make it compile and work out of the box straight away. Just make sure that >> the target you compiled did in fact create the plugin inside the application >> bundle. Run the application, maybe reboot too. Then magically the problem >> goes away. >> >> Check the console after running Motion or run Motion from the shell to check >> any messages regarding the plugin. >> You don’t need to fiddle with pluginkit. >> >> 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: proper current way to build a new FxPlug?
by Paul Miller 27 Aug '17

27 Aug '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-transfer-encoding :content-language; bh=ncr1vE6+7kAsP8c5/QsluIHpCFRst5Veh/melf75hPE=; b=cUR13KVNSzhv2veItUTGQTD4TvdbMHJdIryyZyjOnyIu46SLZWF4eozdzDUIHOoj+o c0QQDlVVZcJfLStJuCSN7JmNR+aHaWjkyEohVp4NxoY5svNukBYh3v3e2ADBN5JsSgn8 nKqC0UFtYGKChP9xqD6A15h/kIICfD/KVuht9gRaHbMpJ1kEl7GmFwX6LjY3tJE3k12/ Kg9LoPlQ7LzP0uqs5Kvpp26HTK1tX7G0aV7nXwRPr0+OnT8EJ6H41d/o5Zr1/mLYVgyl hjOtsB6rN0r0mFVGLHGvCXTCc43PxdLQLGRhCM2amsmSIQ44jnYhwQd2NLGug3w93kJ8 inhA== User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Thanks for the tip Lyndon. That didn't work either. DFT FxPlug.app/: a sealed resource is missing or invalid NO On 8/27/17 9:01 AM, Lyndon Hill wrote: Hi Paul, I had a similar experience. I don’t think I nailed down a series of steps to make it compile and work out of the box straight away. Just make sure that the target you compiled did in fact create the plugin inside the application bundle. Run the application, maybe reboot too. Then magically the problem goes away. Check the console after running Motion or run Motion from the shell to check any messages regarding the plugin. You don’t need to fiddle with pluginkit. 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 Here is something that DID work. I created a whole other user, logged into that, ran the FxPlug .app, then ran pluginkit -m, and it showed up! Also, there were more than a page of entries in the pluginkit output. When I'm logged into my normal user, there are only maybe ten or so! So what's going on here? How do I get my normal user account to see all of the usual pluginkit entries that appear for other, new, users? Another note: I noticed that after turning on code-signing for the template plugin, the signing failed. check-signature explains that an embedded framework: In subcomponent: .../DFT FxPlug.app/Contents/PlugIns/DFT FxPlug.pluginkit/Contents/Frameworks/FxPlug.framework FxPlug.framework is malformed, at least according to the ever-changing code-signing rules in Sierra. How am I supposed to rectify this?

1 0

Re: proper current way to build a new FxPlug?
by Lyndon Hill 27 Aug '17

27 Aug '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Paul, I had a similar experience. I don’t think I nailed down a series of steps to make it compile and work out of the box straight away. Just make sure that the target you compiled did in fact create the plugin inside the application bundle. Run the application, maybe reboot too. Then magically the problem goes away. Check the console after running Motion or run Motion from the shell to check any messages regarding the plugin. You don’t need to fiddle with pluginkit. 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

Re: proper current way to build a new FxPlug?
by Darrin Cardani 26 Aug '17

26 Aug '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Paul, That’s very odd. What OS are you on? There should be nothing else you need to do to the template. You can try turning on code-signing and also sandboxing to see if that fixes the problem. I don’t believe you need either of those, but I could be wrong. I have heard of one other thing that sometimes fixes a problem like this. Some developers have reported that booting into single-user mode and then booting back into regular mode resets something and allows this to work. Obviously you shouldn’t have to do that, but it’s one more thing you can try. Darrin > On Aug 26, 2017, at 11:14 AM, Paul Miller <paul(a)fxtech.com> wrote: > > Hey Darrin - > > I tried that - nothing seems to work. Am I supposed to do anything else to > the template project to get it to work (such as turn on code-signing)? > > I'm running Sierra 10.12.5 and XCode 8.3.3. Do I need any particular version > of Motion or FCP installed? > > Thanks! > > -Paul > > > On 8/26/17 1:11 PM, Darrin Cardani wrote: >> Paul, >> >> This is likely due to a bug in Launch Services (hopefully resolved in High >> Sierra). I’ve found that I often have to go to the Finder and manually >> launch the app once for it to get registered. After that it shows up from >> the command line and in Motion. >> >> To do that, you can go to the Project Navigator in Xcode, twirl open your >> project, then twirl open the “Products” folder. If you right click or >> control click on the App shell, there should be an option to “Show in >> Finder” or “Reveal in Finder” or something like that. Choosing that will >> open the enclosing folder. Just double-click it to launch and then quit it. >> >> Darrin >> >>> On Aug 26, 2017, at 10:58 AM, Paul Miller <paul(a)fxtech.com> wrote: >>> >>> In the past I've built all of my FxPlugs by hand. This time I'd like to use >>> the template that comes with the latest SDK I could find (3.1.1). >>> >>> I used the template in XCode to create the stock template plugin with the >>> name of my choice. It built the shell app and everything, so I ran it and >>> then quit it. It is my understanding that this should register the fxplug >>> with the system. But I tried running pluginkit -mA and it does not show up >>> - nor does it show up in Motion. >>> >>> I also tried manually registering it with pluginkit -a but that also had no >>> effect. >>> >>> Is there some other step I'm missing? >>> >>> >>> _______________________________________________ >>> 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: proper current way to build a new FxPlug?
by Paul Miller 26 Aug '17

26 Aug '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:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ds75xUEuHwOGpw1JpRYTykT/MzR0/1ykA4yseuJZNww=; b=VzyUQ6cAWKX1dQQLkzG2GGhJ8iy6GETqQqzx/u+cB9ODg4eyIFS5jGSFiuQbro1n9M Icy7od5qkrJ7QnZHbQs49dc9fQQnuBlC2XogsQHAQbPeqdwD3hRtWNv/ZYWWqBym5Szn nZeCBeYwpNsoIJqCfVYTB9Eew+i/CyAG7FW5BdSwHoyrbAP03C1AZ9XbcZH8Y6MjWQV4 hqQ5pq4bXCazVygxcbsm14zNNfXJSKWGzZcHER9wFwuYh5+9uGIT+gjRH+L7+Xr7CCJP A5ohnfZ+uebaSQR7lr/SGzByaoxC53cLqWpUurYyYie4oun+QV2/xH+U5ePidOY3yRLB RmNA== User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Hey Darrin - Thanks! -Paul On 8/26/17 1:11 PM, Darrin Cardani wrote: Paul, This is likely due to a bug in Launch Services (hopefully resolved in High Sierra). I’ve found that I often have to go to the Finder and manually launch the app once for it to get registered. After that it shows up from the command line and in Motion. To do that, you can go to the Project Navigator in Xcode, twirl open your project, then twirl open the “Products” folder. If you right click or control click on the App shell, there should be an option to “Show in Finder” or “Reveal in Finder” or something like that. Choosing that will open the enclosing folder. Just double-click it to launch and then quit it. Darrin On Aug 26, 2017, at 10:58 AM, Paul Miller <paul(a)fxtech.com> wrote: In the past I've built all of my FxPlugs by hand. This time I'd like to use the template that comes with the latest SDK I could find (3.1.1). I used the template in XCode to create the stock template plugin with the name of my choice. It built the shell app and everything, so I ran it and then quit it. It is my understanding that this should register the fxplug with the system. But I tried running pluginkit -mA and it does not show up - nor does it show up in Motion. I also tried manually registering it with pluginkit -a but that also had no effect. Is there some other step I'm missing? _______________________________________________ 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 I tried that - nothing seems to work. Am I supposed to do anything else to the template project to get it to work (such as turn on code-signing)? I'm running Sierra 10.12.5 and XCode 8.3.3. Do I need any particular version of Motion or FCP installed?

1 0

Re: proper current way to build a new FxPlug?
by Darrin Cardani 26 Aug '17

26 Aug '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Paul, This is likely due to a bug in Launch Services (hopefully resolved in High Sierra). I’ve found that I often have to go to the Finder and manually launch the app once for it to get registered. After that it shows up from the command line and in Motion. To do that, you can go to the Project Navigator in Xcode, twirl open your project, then twirl open the “Products” folder. If you right click or control click on the App shell, there should be an option to “Show in Finder” or “Reveal in Finder” or something like that. Choosing that will open the enclosing folder. Just double-click it to launch and then quit it. Darrin > On Aug 26, 2017, at 10:58 AM, Paul Miller <paul(a)fxtech.com> wrote: > > In the past I've built all of my FxPlugs by hand. This time I'd like to use > the template that comes with the latest SDK I could find (3.1.1). > > I used the template in XCode to create the stock template plugin with the > name of my choice. It built the shell app and everything, so I ran it and > then quit it. It is my understanding that this should register the fxplug > with the system. But I tried running pluginkit -mA and it does not show up - > nor does it show up in Motion. > > I also tried manually registering it with pluginkit -a but that also had no > effect. > > Is there some other step I'm missing? > > > _______________________________________________ > 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

proper current way to build a new FxPlug?
by Paul Miller 26 Aug '17

26 Aug '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:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=KHj+0QVCDWBAKMVwo+W1Hyy1zCtPBb0uhjAVk7RSSho=; b=J6gJnE1OgI9VMk5ZTDBVbul+ClgoHvt2fV0ngzXjkj3JQsA1gnXpLCHwxM/NktuEIF dC/rwqL7iFA9fmRroCEFRUJALXgMa0LDuiJKnvkla1XREsGoikgxfrq3j0dWJoMQhgTB n4/YQrKzq1N4i9jCV+Qp+1P7X4cB0R37lsK4+F1bsgSTbpyfDDonENVe+Pi43KodXvf1 PlCOql/katIp0DQYIZy97mFDAWbRbiDOnnsUCNNCnafrDkdSJWkSSRjiE0vChIsZnU6E ZEw3LLHm+hRAYa0pH5/cmt4eNCxdxdv1vLCD9YF1DkS3AzlPtBIbkih+fl8VrMffwDph VhjA== User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Is there some other step I'm missing? _______________________________________________ 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 In the past I've built all of my FxPlugs by hand. This time I'd like to use the template that comes with the latest SDK I could find (3.1.1). I used the template in XCode to create the stock template plugin with the name of my choice. It built the shell app and everything, so I ran it and then quit it. It is my understanding that this should register the fxplug with the system. But I tried running pluginkit -mA and it does not show up - nor does it show up in Motion. I also tried manually registering it with pluginkit -a but that also had no effect.

1 0

Re: Compound Parameters
by Darrin Cardani 25 Aug '17

25 Aug '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com > On Aug 25, 2017, at 1:37 PM, Lyndon Hill <lyndon(a)tiliam.com> wrote: > > Hi Darrin, > > Thanks for the quick response. > >> There’s no official support for publishing parameter groups at this time. > > I see. > > So in the user guide and help page “compound parameters” are a different > thing ? Ah, yes. Compound parameters are points and colors, for example. They have 3 values (we call them channels internally). So you could have an x and y channel or a red, green, blue, and alpha channel for a single parameter. I believe that’s the distinction, though I sheepishly admit that I haven’t read through the manuals carefully lately. > If it’s not a bug then being able to programmatically collapse a group is, > surely ? Being able to do one and not the other is definitely a bug. I’m trying to determine whether both should be allowed or neither. I’ve emailed design and I’m sure we’ll end up filing a Radar about this one way or another. Darrin _______________________________________________ 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: Compound Parameters
by Lyndon Hill 25 Aug '17

25 Aug '17

site_archiver(a)lists.apple.com Delivered-To: pro-apps-dev(a)lists.apple.com Hi Peter, everyone, Thanks a lot, that’s fixed my problem very quickly. Just to be super clear for the archive: in the publishSettings tag in the MOEF you must add a target tag for the group but delete the tags for sub parameters. 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