Skip to main content
Inspiring
June 11, 2017
Answered

How do I manage Premiere Pro Plug-ins?

  • June 11, 2017
  • 2 replies
  • 13199 views

I have the exact same problem every time I get a new major update to PP. Some plug-in from either SmartSound or Plerleyes is not up to date and I get an transitory error message dialog box on every WAV file I import. Here's a screen shot of the dialog box: 2017-06-11_1620 which reads:

"Premiere Pro version 11.1 is not compatible with the Premiere Pro Plug-in version 5.8.5".

If PP knows the plugin is incompatible they why does it install it during the update? Why can't this dialog give me a hint about which plug-in it's complaining about? Is there an error log somewhere?

Now I have to go on a hunt for how to manage the plugins for PP, which is not documented anywhere very clearly that I can find. (This isn't a VST plugin so the existing VST plugin manager in PP isn't useful.

Can anyone shed some light on how to track down these plug-ins? Oh and Adobe, please improve your update installations. They break other things too. On this last one I couldn't get Windows 7 to let PS open graphics files. I had to open PS and then have it open the files. Took awhile but I fixed it. It would just be nicer if the installation took care of that.

Correct answer Rob Shaver

https://forums.adobe.com/people/Rob+Shaver  wrote

So I'm hoping somebody at Adobe will read this and say, "Hey, this is a two hour job to fix and only a 30 day job to test and verify. Why don't we just go ahead and do it?"

File a feature request:

Feature Request/Bug Report Form


Feature request filed!

2 replies

Legend
June 12, 2017

If PP knows the plugin is incompatible they why does it install it during the update?

i don't believe PP is installing the plug-in.  Normally they all get installed to a common folder which won't be affected by an update.  So after the update, PP is just reading the already installed plug-in, which is no longer compatible.

I do see your point on the missing data, though.  It would seem obvious for PP to tell you the name as well as the version of the troublesome plug-in.

R Neil Haugen
Legend
June 11, 2017

Although you use those plugins within PrPro, they're not really Adobe's responsibility ... they make the API's available for the plugin makers, but it's up to the makers to keep their plugins up to date with PrPro. So, as a user, anytime you update PrPro you need to get the latest updates from the folks you get plugins from.

I've got some Red Giant stuff ... same thing. It's my job to see that my Red Giant works in PrPro (or Resolve) when I update either app.

Neil

Everyone's mileage always varies ...
Inspiring
June 12, 2017

@ R Neil Haugen, I get your point.

My point is that Adobe should want to make their customers have a smooth experience. The first time that dialog box pops up they could have a check box to disable or even delete the offending plugin when I click the OK button to dismiss it. I'm not a pro and don't really do that much editing any more so every time this happens it take me a half a day to track down the info about how to find and uninstall the offending plugin and/or seek out the newest replacement plugin.

So I'm hoping somebody at Adobe will read this and say, "Hey, this is a two hour job to fix and only a 30 day job to test and verify. Why don't we just go ahead and do it?" But I'm not holding my breath. It's been 4 years or so since I requested an enhancement to fix PP's inability to treat spanned files as a single clip for MOV format. At Adobe's request I've even supplied them with sample files. But no joy in Mudville.

Okay, now I'm whining so that's all for this session. I've figured it out on my own before, I can do it again.

Thanks for your consideration. Peace, Love, Laughter: Rob:-]

R Neil Haugen
Legend
June 12, 2017

I understand ... they don't always seem to follow my obviously correct suggestions either ... what's up with that?

Neil

Everyone's mileage always varies ...