[Topic moved here.]
I don't have experience myself with modern versions of Cakewalk, and it isn't a host that we officially support, but conceivably something here might help:
viewtopic.php?f=3&t=20667&p=154721#p154721
mdyde wrote: I have no experience myself with Sibelius Ultimate, and I don't think we've had any feedback from other users on it. I'm not sure whether the AU or VST Links are compatibility with it, but conversely I know of no specific reason that they shouldn't be, since they adhere to the standards (e.g. the AU Link passes Apple's AU validation). Sibelius isn't a host that we officially support or test with for v5+, I'm afraid.
My quick thoughts, in case they're of any help:
- If Sibelius supports both AU and VST plug-ins and you can't get it to work with one of those two formats then you could perhaps try the other [if you're using a Mac].
...
- The Hauptwerk AU/VST plug-in links only allow a single instance to be loaded, so make absolutely certain that the host isn't trying to load two instances (even temporarily). E.g. try launching the host with a clean project, in case it was opening with a project that already had an instance of the plug-in loaded.
- See also the general notes in the "Hauptwerk AU/VST Link plug-in" section in the main Hauptwerk user guide (pages 264-266 in the current v7.0 version).
- If all else fails, instead of using the AU/VST plug-ins, you could potentially route MIDI from the host to Hauptwerk via macOS' built-in virtual MIDI cable functionality (the IAC Driver).
Also:
- Make sure that the plug-in is in the host's (i.e. Cakwalk's) plug-ins search path.
- Try loading an empty project in the host, in case it's trying to load multiple instances of the plug-in due to an existing project that uses it already being loaded.
- Try using the host's function to scan for plug-ins again.
- Hauptwerk's VST plug-in is in VST2 format (which almost all hosts support), not yet VST3.