Thanks cocell! I think that may be the ticket! Here’s what I’m trying now…
If you log in to your Avid/Digidesign developer account from here (mine is a digidesign account):
…and run THIS version of PT, you can run plugins that aren’t digitally signed yet (I think). I’m guessing the fact that the plugin isn’t PACE Code-Signed yet makes it un-runnable from regular PT. So, you’re supposed to build/test it in this beta PT, then when it’s all working, have it PACE signed and then you’re good to go.
For Beta builds, I’m pretty sure they need to be Signed to test but you cannot debug.
The Latest downloadable Dev Build is 12.4.0x56.
I hope I dont get in trouble for this information.
I just tried last week to build the aaxlibrary in VS2015, but there is no project file, only VS2012. I opened it in VS2015 but it didn’t compile out of the box, so I put the windows build aside to continue developing in OSX.
Were you able to compile the aax library in VS2015? I don’t want to install several VS versions…
About the “No valid plugin”, you are right, the development build skips checking the signature and use the plugin anyways. The normal protools (and beta is a “yet to be normal”) will not load/use plugins without valid signature.
The other difference is you can attach a debugger to the development build but not to the normal ProTools, (as cocell already stated).
The script provided by Avid you’ll have figured out is confusing. If you get completely stuck on that part I have an alternative one which is easier to follow…
cocell, I’ve used the attached AAX template and it’s worked great! Now that I am signing the working AAX file that was created using the attached template, the signing tool is reading it as a directory, not a file – what a headache!
