Premiere Pro is not recognizing my plugin

New Here ,
Jun 08, 2015 Jun 08, 2015

Copy link to clipboard

Copied

Hi,

  I am developing One Adobe Premiere Pro Exporter Plugin. Working version: Adobe Premiere Pro 2014.

As per the Premiere Pro SDK document, I installed MSVC & Adobe Premiere Pro 2014 in One machine. I set all the environment variables and started my Exporter plugin development.

My Final output has,

Exporteri265.prm, + 2 x DLL files. In the PC where I developed the exporter, I copied Exporteri265.prm to C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Plug-ins\Common

and 2 x DLL files to C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\

In My development PC(where it has MSVC + Premiere Pro 2014), all works fine. Premiere Pro is able to load the plugin.

Recently we purchased one more license and installed in a Test PC (Only Premiere Pro, No MSVC). In this machine I copied the executable in the same way. But Premiere Pro is not loading my plugin.

It gives one loading error (Log File).


Loading C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Plug-ins\Common\Exporteri265.prm

Invalid registry entry found so the plugin will be loaded from disk.

Loading from disk...

The library could not be loaded.

The same technique works fine in my development PC. But not in Test PC.

I checked all the registry settings. HKEY_LOCAL_MACHINE. I also moved my .prm to C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore. Not working.

Can somebody help me?? What is missing in my approach??

Regards,

Subash

TOPICS
SDK

Views

1.4K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jun 09, 2015 Jun 09, 2015

Hi Subash,

If you are building on one system and specifically having problems loading the plug-in on another system, make sure you're building the plug-in using the Release configuration, not the Debug config.

Cheers,

Zac

Likes

Translate

Translate
Adobe Employee ,
Jun 09, 2015 Jun 09, 2015

Copy link to clipboard

Copied

Hi Subash,

If you are building on one system and specifically having problems loading the plug-in on another system, make sure you're building the plug-in using the Release configuration, not the Debug config.

Cheers,

Zac

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 21, 2022 May 21, 2022

Copy link to clipboard

Copied

@Zac Lam I have the same problem, What's the difference  between  the Release configuration, not the Debug config? I thought they were just the difference on compilation optimization. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 21, 2022 May 21, 2022

Copy link to clipboard

Copied

LATEST

 I have the same problem, What's the difference  between  the Release configuration and the Debug config? I thought they were just the difference on compilation optimization. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines