vst~ Shell Plugins Problems
I have to run a patch in Max 7 in 32 bit mode but want to include some new elements with the Blue Ripple Sound O3A plugins for ambisonics. I'm running Max 7.3.6 on OS 10.12. The plugins are 32 and 64 bit.
Max is not scanning my plugin folder correctly and only shows the shell or folder for each plugin. If I try to use the plugin ID with the plug message, it doesn't load, if I try to use the subname message, it also doesn't load. Actually what happens is that vst~ only ever loads one plugin, which I assume is just the first in the shell folder. Whatever messages I send vst~ it only ever this particular plugin from the shell. This is the case for all of the five O3A shells that I have: Upmixing, Decoding, Manipulators, Decoders, and Core.
The plugins work fine on Max 8 once I launch a full audio scan from the preferences.
Based on some browsing of the forum it seems that other shell plugins work fine on Max 7, so I'm wondering where the issue may lie.
Thanks
Nick
just to make sure: you already gave vst~ a sufficient number of in/out channels?
yup, 2 in and 16 out as required by the O3A plugins. I'm baffled why it doesn't work if other shell plugins work for people on Max 7.
You can try them yourself as the Core library is free. If you're interested in ambisonics or spatialisation then it'll be of interest anyway, incredible renderings, effects, decodings, and visualisations:
https://www.blueripplesound.com/products/o3a-core
I was having that issue (only see "03Acore" & then only loads panner). ICST and other HOA plug-ins where working as expected. I had always used the "plug" message to load. Switching to dragging the plug-in from the left hand bar solved the problem for me. And I see all the Blue Ripple plug-ins listed there as well.
*did not try from MAX 7, MAX 8 on OS 10.13