[SOLVED] Cannot validate example Plugins AAX

Hey there,
I cannot load the JUCE example plugins into the Mac ProToolsDeveloper version.
The plugins build just fine but neither the digishell aaxval nor ProToolsDev seem to be able to validate any AAX Plugin i build. It works on Windows tho.
If I try to validate any JUCE example plugin with the digishell, the digishell just freezes and gives me no output anymore.

My specs:
-Mac Mini M1 Ventura
-JUCE 7.0.6
-aax sdk 2-5-1
-aax developer tools beta 2022-09-01
-XCode

I also checked for JUCE 7.0.1 aax sdk 2-4-1 so I think the problem is actually me :smiley:
Did anyone maybe have the same problems? There has to be somehting I am missing right now…
Is there any check that I can do

You did wrap/notarise the plugins, right?

Oh wait, the dev version is supposed to load unwrapped plugins. Maybe try it anyway just to get more information?

I didn’t do any notarizing, since I am not a certified AAX developer yet… Or is there any notarization process that I have to do even if I am not? I’ve just built the example plugin and tried to load it

I would try codesigning the plugins to run locally:

Thanks for that (Didn’t know that) Unfortunately it doesn’t solve the problem :confused:

D’oh! Sorry!

AAX plugins need to be signed even in dev version of Protools

What do you mean by signed ? Codesigned (codesign --force -s “Developer ID Application: XXXXXXX” “/Users/XXXXX/Library/Audio/Plug-Ins/VST3/sign/Plugin.aaxplugin” --timestamp -f) ? Or signed with some other tool?
I tried codesigning the plugins which did not change anything…

PACE codesigned

I don’t think this is correct… the readme states:
“5) Run the plug-in in an AAX host which supports unsigned AAX plug-ins, such as a
Pro Tools developer build, Media Composer, or the DSH command-line shell”
Also my plugins show up in ProToolsDev on Windows…

Maybe something that has changed along the year

Maybe idk. The Demo_Gain plugin example from ProTools itself (the one that comes with the sdk) seems to be able to be validated and run without any signing.

Are you building the plugin for the right target - arm64 and/or intel to match the the dev build?

Rail

2 Likes

:kissing_heart: no i didn’t. THANK YOU!!!