Noel Borthwick

The Cakewalk Core plugins will work in any host including CbB as long as you have an active BandLab membership and sign in to activate via the plugins. However, while Sonar can seamlessly migrate the Cakewalk Core Plugins suite from the old legacy Sonitus plugins at project load time the automatic migration will not work in prior Cakewalk hosts or other hosts. In CbB or SONAR Platinum you must disable the VST Migration settings before loading old projects containing Sonitus plugins, since it may lead to errors on loading these projects otherwise and cause plugin settings to be lost. To disable automatic migration turn off "Replace if possible on Project Load".

Hi @matt, Aha I see what happened here. Backwards migration is indeed working fine in Sonar. The issue here is that CbB doesn't have the code needed to handle backwards compatibility with DX and therefore when it detects the new plugins it replaces the old plugins with the new ones, but since the migration from DX to VST is not implemented in CbB, that part fails and it throws this error. I do not get any hang in CbB just this message. Most likely what is happening is that you get a bunch of these messages that are behind the application window and it makes it look like it's hung. Please check. The message is basically telling you that a plugin was replaced but the state couldn't be transferred. This logic is built into all Cakewalk applications from 2015 or so. The resolution to this is to turn off automatic replacement in Cbb here. PS: this is a classic example of why we cannot support old products in the field that are not updated anymore. Thanks for reporting this. We'll update the release notes for the plugins to tell people using CbB to disable automatic replacement.

See this reply.

We can consider it but why not use standard parameter learn in the host application? That's the more modern way to do it.

We're already on it and it will be released soon.

This is bizarre. Did you install the latest sonar update successfully? If you disable the automatic VST3 migration this will prevent auto loading the new plugins. You can change this in Preferences > VST Settings > VST3 Migration and uncheck "Replace if Possible on Project Load" Which version of windows are you running? Can you manually load these plugins? I suspect your problem is related to something else since nobody has reported this issue in months of testing. In any case if you can't resolve it send me a pm and we can do some further troubleshooting. PS: installing the new plugins has no bearing on the old dx plugins. They can coexist and will not affect other apps.

There is something messed up in your installation if you don't have common files/vst3 in your default vst scan path unless you manually removed it. Every clean installation of sonar includes that path because it is the standard vst3 location across it should never be removed. This is why it didn't work for you. All that is required is to install the latest version of sonar and then the core plugins add on without running through all the hoops you did

@Robert Glaser @Jon Paul Sapsford The hotfix is live now. Please try it and see if it fixed your issue. 31.08.0.035

We've got to the root cause of the PRV pane issue. We'll issue a hotfix soon today to address that issue. Sorry for the inconvenience.

Are you using a custom workspace? Set your workspace to None and retry.

@Robert Glaser I can't see why it would happen with new projects as well as old ones. Something is messed up with your view states. You may need to make a video showing exactly what you are doing. Try these troubleshooting steps first: 1. Set your Workspace to None. File - New. Add MIDI track and open PRV. Do you see the keyboard? If that doesnt work, try setting the workspace to Basic and retry. 2. Close Sonar first and go into regedit and find this key: HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Sonar\View Data Then rename it to View Data2 or something different. Now restart Sonar and try it again.

What are you having to reset? We're not aware of any change that mandates resetting layout. Which version did you upgrade from?

Im not sure why it took 45 mins to get working. If you are running Sonar with BandLab membership installing the addon takes seconds. Then once it scans the plugins are available. Opening a plugin automatically activates it. I've tested this on a clean system and the whole process took less than a minute. Can you provide more detail into what was unfriendly?

Or upgrade to Sonar Free for zero cost.

@Mark Morgon-Shaw can you send me a project that has this issue? Also if you resize the PRV and resave the project does it work on next open?