Previously (in 10.4) I could add AU Lab as a custom executable in Xcode and use “Build and Go” to launch a plugin for debugging.
Now (even with the demo plugin) in 10.5 the plugin isn’t recognised when Xcode launches AU Lab. I can quit AU Lab and relaunch it manually, but of course the debugger is no longer attached. I’m guessing that it seems to be that the plugin is not quite finished being copied into ~/Library/Audio/Plug-Ins/Components/ before AU Lab is launched.
Nasty, that’s the sort of irritating problem that you can spend hours tracking down…
Good news though - I’m nearly ready with my Cocoa port, so you should be able to build 64-bit juce apps soon. I’ve got most of the main functionality working, though I’ve not started porting the different plugin wrappers yet. Hopefully that won’t be too much of a nightmare.
getParameterMin()
getParameterMax()
getParameterDefault()
getParameterUnit() - using AU unit constants for now
getScaledParameter()
setScaledParameter()
… to the plugin class (AudioProcessor subclass) code.
It just allows parameter ranges beyond 0…1 so that “correct” automation values show up in Logic (for example). No idea if this is worth it, considering the other wrappers, i.e., does VST support actual values or just 0…1?