Hello everybody !
I’m also using VS2008, and I’m kind of experiencing the same problems than you guys.
SimplePlugin (demo plugin included in the RTAS-SDK) compiles and links only in release.
By slightly tweaking the RTAS sdk, it’s possible to link a debug version of project SimplePlugin to the release version of PlugingLib.lib. This works for compilation and linking, but at runtime, ProTools refuses to load the plugin, and it is not possible to debug it.
This is behavior with RTAS sdk 8.0, 8.1 and 9.0. With old version 7.3, debug builds work fine, and it is possible to use VS2008 debugger.
When trying Introjucer’s default plugin, I run into the same problem : the release version is working fine (PS : one just has to set project properties/linker/manifest->generate manifest to yes, so that ProTools finds the CRT dlls, as we compile with /MD - Jules…), but the debug version however shows the same behavior than debug-SimplePlugin : compiles, links, but doesn’t load up in protools…
This is the behavior with RTAS sdk 8.0, 8.1 and 9.0 (i did minor adjustments to juce_RTAS code to match the tiny changes between version 8 to 9) Juce does not support version 7.3, so I didn’t test it.
Now, my feeling is that it all comes from a bug in RTAS sdk. Digidesign guys probably know about it, but I’m not sure if it is very high on their priority list.
In the meantime, can anyone think of a workaround to still get a debug build working (or sth looking like it…)
My deep problem is actually that the plugin I’m supposed to port to RTAS crashes when opened in ProTools, reading memory somewhere it isn’t allowed to. Unfortunately :
- since it only happens with this RTAS plugin, and not trivial JUCE-generated RTAS, I suspect the bug is in my code.
- since I’ve only got a release build of the plugin, I can’t see what happens inside this opaque binary.
- since the bug doesn’t occur in the VST version, I suspect it is kind of a tricky one to find, so a debugger would really be helpful !
Thank you in advance for any idea…