Skip to main content
C
Commandor16
Participant
August 23, 2017
Question

Problems with plugins .bundle from Premiere Pro SDK for macOS

  • August 23, 2017
  • 1 reply
  • 2938 views

Hi all,

I am using:

SDK - Premiere Pro CC 2017.1

Program - Adobe Premiere Pro CC 2017.1

OS - macOS Sierra

After compile Vignette plugin from Premiere Pro SDK, it is not load to Premiere. But Premiere founded this plugin.

In log file: "No loaders recognized this plugin, so the plugin is set to ignore."

Does anyone have a solution to this problem? Please, help me.

This topic has been closed for replies.

1 reply

Z
Zac Lam
Inspiring
September 7, 2017

Hi Sergei,

Have you installed the latest CUDA Toolkit from nVidia?

A
AtonMusic
Known Participant
November 3, 2017

I can't even get the example to compile...

getting following error in Xcode 9 with latest cuda toolkit.

nvcc fatal   : The version ('90000') of the host compiler ('Apple clang') is not supported

In general this sdk seems to be a bit 'clunky' at least for someone who is used to programming on a Mac!

A
AtonMusic
Known Participant
November 8, 2017

If there are specific things we could do to make the PPro C++ SDK more user-friendly*, let us know.

* Other than by re-writing everything for Cocoa.


In Addition to Above Post..

We have written numerous of drawing classes for our other plug-ins in i.e. FCPx and Standalone.

Those use NSControls to draw. Which is a lot easier than using the DrawBots.

So - when an effect is being instantiate we grab the CocoaPlatformView_for_UI_PlatformSubView and add an NSView to that.

This works quite ok for but there is a huge problem.

Your CocoaPlatformView_for_UI_PlatformSubView which overlays the CustomUI and provides the NSTrackingArea is ​not ​being clipped to the Effects Control View's DVAMacContainerView but to the DVAMacRootView. This of course causes havoc on our drawing and which is not being clipped to the scrolling Effects Control View and will thus draw over which ever view lying beneath in the coordinate system. If only CocoaPlatformView_for_UI_PlatformSubView would be clipped to the Effect Controls View we could be drawing and handling events with Cocoa. This approach would be mean MUCH less work for you as SDK Writers. It could probably be done on Windows as well....

PS - Given the fact the numerous of your 3rd pty developers are extending Apple classes with their own methods you could potentially run in to serious bugs.

Just try setting CocoaPlatformView_for_UI_PlatformSubView' layer's backGroundcolor to blue. And you will see that your own NSVIew 9CocoaPlatformView_for_UI_PlatformSubView) IS not being clipped to effect control window -  like its supposed to. It actually extends beyond its intended view space and is just waiting to cause a bug ;-)

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices