• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Have to manually reload my Control Surface Plugin on Premiere 2021 restart

New Here ,
Apr 17, 2024 Apr 17, 2024

Copy link to clipboard

Copied

Hello All,

I have a question regarding Control Surface plugin reload behavior that differs based on deployment location.

 

Background:
I implemented Control Surface Plugin for Adobe Premiere Pro 2021, following Adobe SDK example. I tried two deployment locations for testing:

1. "C:\Program Files\Adobe\Common\Plug-ins\ControlSurface"
2. "C:\Program Files\Adobe\Adobe Premiere Pro 2021\Plug-Ins\ControlSurface"

 

In both cases, I can successfully load the plugin by going to Edit->Preferences->Control Surface->Add. Plugin is listed, successfully loads and works. However, after I close Premier Pro and open it again, only with the second deployment path it automatically loads the plugin and it is ready to work immediately.
If my deployment path is 1) I have to re-do the Edit->Preferences->Control Surface->Add steps every time I start Premiere.

 

Question:
Is there a way to ensure that with the first deployment path auto-loading of the plugin on Premiere start works as well? The first deployment path is preferable as we don't have to worry about Premiere updates and installing for different Premiere versions. The fact that both paths result in plugin being discovered in Edit->Preferences->Control Surface suggests that they should both work the same but clearly not.

 

Any help is appreciated!

 

Thanks,
Oleg

TOPICS
Error or problem , SDK

Views

150

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

New Here , Apr 19, 2024 Apr 19, 2024

Hello Bruce,

 

Everything (including my modified SDK example) works fine now. What I did was the following (hope it helps someone who may run into the same problem):

1. I built another, completely unrelated, SDK example - SDK File Importer, and deployed it to "C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore\"
2. Noticed that my Control Surface plugin was initializing on Premiere restart. (I have added code that writes to a text file during plugin initialization)
3. Even after deleting SDK File I

...

Votes

Translate

Translate
Adobe Employee ,
Apr 18, 2024 Apr 18, 2024

Copy link to clipboard

Copied

Confirming: Does the (unmodified) SDK example plugin stay selected, across PPro sessions? 

Votes

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 ,
Apr 19, 2024 Apr 19, 2024

Copy link to clipboard

Copied

Hello Bruce,

 

Everything (including my modified SDK example) works fine now. What I did was the following (hope it helps someone who may run into the same problem):

1. I built another, completely unrelated, SDK example - SDK File Importer, and deployed it to "C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore\"
2. Noticed that my Control Surface plugin was initializing on Premiere restart. (I have added code that writes to a text file during plugin initialization)
3. Even after deleting SDK File Importer plugin altogether, Control Surface Plugin works as expected now, successfully reloads any time Premiere is restarted.


I also tried resetting plugin cache and plugin continues to load fine on startup. I deployed another Surface Plugin (different file name and id) and it also re-loads perfectly fine now. Just to remind, I am talking about deploying to directory "C:\Program Files\Adobe\Common\Plug-ins\ControlSurface\".

 

My only guesses are that either something was off with my Premiere installation to begin with, or it was some strange plugin caching issue. Regardless, deployment of an unrelated plugin to MediaCore\ directory fixed it somehow.
I don't want to uninstall and then re-install Premiere to investigate this further so I just leave it as is for now.  If I eventually figure out what caused this, I will post an update. Any insights are welcome, of course! Would be interesting to figure this out.

 

Thanks and Regards,
Oleg

 

Votes

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
Adobe Employee ,
Apr 19, 2024 Apr 19, 2024

Copy link to clipboard

Copied

LATEST

1. Glad it's working.
2. That's super weird!

Speculative: Perhaps the presence of that new plugin convinced PPro to blow plugin cache, which may have cached a load failure of your plugin...? ¯\_(ツ)_/¯

Votes

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