Hi Nicholas, Tina, Thanks for your patience, I was out of the office most of last week. In more recent versions of the Premiere Pro SDK, the effects and transition samples all use the After Effects API as a foundation, and extend the plug-ins using additional Premiere Pro-specific APIs for transition capabilities and GPU support in Premiere Pro. So basically, it is fine to start with the AE SDK if you want to build an effect that renders on the CPU in Premiere Pro. But if you want GPU rendering, and/or to build transitions, you'll want to start with the samples in the Premiere Pro SDK. Are you building the plug-ins directly into the MediaCore plug-ins folder? This is what you need to do to debug a plug-in. In XCode, go to File > Project Settings. In the Project Settings dialog, click Advanced, choose Custom, switch the drop-down menu to Absolute, and fill in the MediaCore plug-ins folder: /Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/PrSDK <- I like to create and specify a subfolder 'PrSDK' just to keep things tidy. Also, when you say no plug-ins show up, are you referring to effects and transitions, or all types of plug-ins? Since the effects and transition samples use the AE API as a foundation, you'll also need to set up Xcode so that it knows where the After Effects SDK is. You can do this by going to Xcode > Preferences > Locations > Source Trees. In there, add the name AE_SDK_BASE_PATH, and the path should be the root of your downloaded AE SDK.
... View more