site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=reply-to:subject:references:to:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=TcX2B1QKEcF62U/zvzC2Ro55QA9BsfHOZ1bBlJt+s7s=; b=WFExMmioUUmj5bq5S4n32qTWqln5JN0oithuk/QsXl6p6m/BCNJQGzt3QUbXamfSZt Mvx421RF0ysWfVL9T2N6IhvmAzRGu03QB4S9x3eC6XNL3UNLds/1lsVTZJVsPim5e41S LTChbMbQggbAHCUuScmNakdLTzL09KkLDyekwtediHdRQQRQ9xOTmSiVrXTXKArM2h46 ZUWWCvxhhbu2QUQ27lS72vas0IGePq+H/lBYiZwF7VlXomJ0IS73D7U+TH8xMWX7AW9E Nl8M6ovVbN5d7rdiKjttojTIQJ7ZtU4pmAuEoXVyiQzeMax5VezgfnczqPbyejIxEpET VLyw== Organization: FXTECH User-agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Daniel - Let me know if you stumble across a fix. -Paul On 5/3/2017 3:31 PM, Daniel Walz wrote: Hi Darrin, thanks for the answer. I tried that, removed all symlinks I created of either FxPlug folder in /Library and in ~/Library. I also started the Wrapper Application from Finder and let it run for a couple of seconds. But neither pluginkit -m shows anything, nor it is visible in motion. I also tried to reduce deployment target to 10.11 (but I am on 10.12 though). No change. Can I look into launchServices database? Is it worth resetting it's cache? Exists there any logging from that service? Thanks for walking me through. Daniel On Wed, May 3, 2017 at 8:51 PM, Darrin Cardani <dcardani@apple.com <mailto:dcardani@apple.com>> wrote: Daniel, You don’t need to do the linking to /Library/Plug-Ins/FxPlug/ since you’re working with PluginKit. I’d remove the link just to make sure it’s not causing any other issues. Next, I would find your plug-in’s application in the Finder and double-click on it from the Finder to launch it. We have seen cases where Launch Services doesn’t notice the plug-in the first time it’s launched from Xcode. As such, it doesn’t register with PluginKit. Launching it by hand from the Finder seems to nudge Launch Services to where it recognizes the plug-in. Let me know if that works for you. Darrin On May 3, 2017, at 4:28 AM, Daniel Walz <daniel@filmstro.com <mailto:daniel@filmstro.com>> wrote: Hi everybody, I try to create a generative plugin with FxPlugin. I am using FxPlug SDK 3.1.1 on OSX 10.12.4 First I create an empty FxPlug project with XCode (8.3.2). Then I change the base class to @interface FilmstroFxPlugPlugIn : NSObject <FxGenerator> and adapt the frameSetup removing RenderInfo, that the FxGenerator doesn't have: - (BOOL)frameSetup:(FxRenderInfo)renderInfo hardware:(BOOL *)canRenderHardware software:(BOOL *)canRenderSoftware and also the renderOutput removing the inputImage: - (BOOL)renderOutput:(FxImage *)outputImage withInfo:(FxRenderInfo)renderInfo For a start I commented everything out and return YES. The project builds fine, no warnings (except the documentation inside the SDK). Then I link from products the .fxplug into /Library/Plug-Ins/FxPlug/ But pluginkit doesn't show the plugin. pluginkit -a finishes without a message. But still pluginkit -m doesn't list the plugin. I can run the Application as well, but it shows only an empty window, as I didn't implement anything there. How can I troubleshoot, why it is not showing up? N.B. I had a version showing up, but then I realised, that my changes didn't have any effect, so I removed all traces by hand. Now I tried to start over, but now I don't even see an empty plugin. I used XCodes "New FxPlug project", so the GUIDs should be unique. Thanks for help, 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@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@apple.com <mailto:dcardani@apple.com> -- *Daniel Walz* | Software Developer Filmstro | Music that Moves. Sussex Innovation Centre | Science Park Square | Brighton, BN1 9SB daniel@filmstro.com <mailto:daniel@filmstro.com> | Personal mobile: +44 7491 836 008 <tel:+44%207491%20836008> 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@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@fxtech.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com We're seeing this exact issue with a bunch of our plugins. Worked fine in El Capitan, and randomly doesn't work in Sierra, usually on machines that were upgraded. Clean installs usually fix it. We've been waiting on input from the launch services folks for months.