Skip navigation
Currently Being Moderated

CS6 Exporter Plugin doesn't open in Premiere Elements 11 (Windows)

Jun 16, 2013 11:28 PM

Tags: #premiere_elements #exporter_api #export_param_suite

I want to make my (Windows) exporter-plugin compatible with Premeire Elements 11.

 

So far, I have been gotten my exporter-plugin to appear in Adobe Premiere Pro CS6 and Media Encoder CS6, and the plugin runs there correctly.

 

I then followed the directions for running Premeire CS6 to create an export a preset file (*.epr).  I copied copied  that exported *.epr file to "OTHERS/MyCompany/MyPreset.epr" in my Premere 11 [App installation folder].  (As well as copying the plugin-binary *.prm to Plug-ins/common

 

In the <Publish:Share> tab, when I use the mouse to highlight 'OTHERS', I receive an error-dialog-box :

 

"Premiere Elements has encountered an error.

[..\..\Src\Exporter_Accessors.cpp-213]"   [Continue]

 

After I click continue, I don't get the dialog-box for my exporter-plugin.  In the <Publish:Share> tab, I now see the warning-triangle and some text next to it: "Export Settings Invalid"

 
Replies
  • Currently Being Moderated
    Jun 17, 2013 5:01 PM   in reply to nvenc4everyone

    I'm checking on this for you.  At first glance, it looks like it may be related to your exporter's implementation of exSelQueryExportFileExtension.

     

    Zac

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 18, 2013 9:12 AM   in reply to nvenc4everyone

    Thanks for the feedback there!  I've passed it along to the Premiere Elements team.  Although the PPro SDK sample projects are not written specifically for Premiere Elements, ideally they should work without modification.

     

    Zac

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 18, 2013 12:49 PM   in reply to Zac Lam

    The Premiere Elements team notes that Premiere Elements 11 is based on the CS5.5 version of MediaCore.  So using the CS5.5 SDK is probably the best way to build plug-ins to specifically target Prem El 11.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 9:27 AM   in reply to nvenc4everyone

    It's in the StdParams.interfaceVer struct passed to the plugin.

     

    Headers\PrSDKExport.h

     

    #define prExportVersion100  1     // 9.00

    #define prExportVersion101  2     // 9.0.1

    #define prExportVersion200  3     // CS5

    #define prExportVersion250  4     // CS5.5

    #define prExportVersion300  5     // CS6

    #define EXPORTMOD_VERSION  prExportVersion300 // current version

     

    typedef struct

    {

    csSDK_int32     interfaceVer; // version # of interface (currently EXPORTMOD_VERSION)

    plugGetSPBasicSuiteFunc  getSPBasicSuite;

    } exportStdParms;

     

    I don't trust it though and do it by trial and error

     

         spError = spBasic->AcquireSuite(

             kPrSDKExportParamSuite,

             kPrSDKMemoryManagerSuiteVersion4, // aka kPrSDKExportParamSuiteVersion, // CS6 supports v4

             const_cast<const void**>(reinterpret_cast<void**>(&(mySettings->exportParamSuite))));

         if ( spError )

         {

         // Try again with the next version back...

         spError = spBasic->AcquireSuite(

             kPrSDKExportParamSuite,

             kPrSDKMemoryManagerSuiteVersion3, // compatible with Premiere Elements 11

             const_cast<const void**>(reinterpret_cast<void**>(&(mySettings->exportParamSuite))));

         }

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 11:29 AM   in reply to nvenc4everyone

    The App Info Suite lets you know the host application and version number of the application.  As Rallymax points out, the exporter API version is passed in.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points