Also make sure, there is NO single line with the warning string "!ID collision", as once you see it, AG falls back to JUCE ID's as described above. The SSLGChannel log entries from above should look like this now:
After this, you have to make AG server try to use disk location independent ID's again, by manually updating the config, as this setting has no UI: Try having only one container version of waves plugins installed. I think you need to figure out a way to "clean up" your setup. I guess the number part depends only on the installation order of plugins and is thus not reliable. Waves is using plugin file names like "WaveShell#number#-VST #container version#_圆4.dll" for all of their plugins. Thats why the server fails (and the plugin stays greyed out). Now, the ID AG tries to load is: "VST-SSLGChannel Stereo- 838cb03c-53434753", which has a different disk location hash than the other two. SSLGChannel Stereo format=VST ins=1 outs=1 instrument=0Īs you see, two SSLGChannel plugins, same plugin ID, different disk locations. This happens for example when upgrading Waves container versions, when the old and new containers are installed.
This is the case for you, as you have multiple plugins with different disk locations, but the same plugin ID. AG stores a settings value for it (see below). This fallback decision remains going forward.
Once a collision is found (two plugins with the same ID), AG falls back to the JUCE default. This works only, if there is no conflicting ID's. AG tries to use only the unique plugin ID and avoid using the disk location (which is the JUCE behavior). One thing I changed in beta10 is the use of plugin ID's. adding plugin VST-SSLGChannel Stereo-838cb03c-53434753. The problem are these messages, where the server complains about plugins it does not find:
0 kommentar(er)
