AAE error -9013 after 12.2 HD install

[Boombatty]

After installing 12.2 it appears my SSL Duende plugins have been deactivated. Upon trying to re-activate them in a prior session I get an AAE 9013 error.
After trashing preferences and restarting, Pro Tools now says the plugins are not found in the plugins folder (though they are indeed there).

Seems similar to people with East West Play? Any help would be appreciated. Might have to go back to 12.1 very soon...

June 2010 Mac Pro quad core, 24GB ram, 2x1TB HDD.

[simonjewel]

Originally Posted by Boombatty

After installing 12.2 it appears my SSL Duende plugins have been deactivated. Upon trying to re-activate them in a prior session I get an AAE 9013 error.
After trashing preferences and restarting, Pro Tools now says the plugins are not found in the plugins folder (though they are indeed there).

Seems similar to people with East West Play? Any help would be appreciated. Might have to go back to 12.1 very soon...

June 2010 Mac Pro quad core, 24GB ram, 2x1TB HDD.

What method of authorization are you using? I seem to recall something about transferring over to iLok from the old system some time ago, maybe it's that causing you the problem? I have the SSL Duende bundle on my computer running 12.2 and no issues at all thus far :)

[Riture]

I am experiencing a similar problem with SSL Duende Plug-ins after upgrading to 12.2; tried similar things to resolve to no avail. I have the new iLok version with the iLok manager as version 2.5.2.1034 (r29969).

[simonjewel]

Originally Posted by Riture

I am experiencing a similar problem with SSL Duende Plug-ins after upgrading to 12.2; tried similar things to resolve to no avail. I have the new iLok version with the iLok manager as version 2.5.2.1034 (r29969).

What is your computer and OS?

[Boombatty]

Hey simonjewel,

I am indeed using iLok2. Latest version of the License manager and v5.1.1 64bit Duende plugins. Did you authorize the licenses to your computer instead of iLok?

Thanks,
Matt

[simonjewel]

Hey Matt,

No my Duende bundle is iLok licensed .... Same version as yours, 5.1.1 on Yosemite 10.10.5 pro tools 12.2 ... Try uninstalling them and then do a reinstall perhaps?

[simonjewel]

Oh, one other possibility, I'm on vanilla not HD at my home rig ... So maybe you'll need to contact SSL tech support on this one

[Boombatty]

hmm.. 10.5.5 here too. I've had more time to play around with things today. It's only the x-verb that is giving me problems (and it's the only one I was using for this project!). I'll keep working at it and let you know if I solve it.

[simonjewel]

Originally Posted by Boombatty

hmm.. 10.5.5 here too. I've had more time to play around with things today. It's only the x-verb that is giving me problems (and it's the only one I was using for this project!). I'll keep working at it and let you know if I solve it.

Coolio, thanks :)

[Boombatty]

The 9013 error is gone after trashing prefs and all that. Did some other general troubleshooting, tried to uninstall and reinstall the duende plugins though I could find all the files it told me to uninstall, even after using terminal to show hidden files. The plugins were no problem but I couldn't find those listed under "Also manually remove the following files." Here are SSL's uninstall instructions:

Mac

Delete the Duende Native plug-ins in these locations

AU: MacHD>Library>Audio>Plug-ins>Components
VST2: MacHD>Library>Audio>Plug-ins>VST
VST3: MacHD>Library>Audio>Plug-ins>VST3
RTAS: MacHD>Library>Application Support>Digidesign>Plug-ins
AAX: MacHD>Library>Application Support>Avid>Audio>Plug-ins

Also manually remove the following files:

MacHD>Library>Application Support>DuendeLicense
MacHD>Library>Application Support>WrapperConfig20
MacHD>Library>Application Support>com.fxpansion.fxshared.bundle
MacHD>Library>Application Support>vstprobe.log

Now, when Pro Tools loads the plugins I can visually see it list X-Verb as one of the ones it loads but it doesn't come up as an option when in a session. If I try to activate an instance of it on a previous session Pro Tools tells me the plugin isn't in the folder. But here's a screenshot that says otherwise!