Noel Borthwick

I created a project from a template, then changed record mode and then saved as the identical template name. On creating a project from that the record mode is retained just fine.

Not sure what you mean by self created presets. Please show a video or describe what exactly you are doing or attach a file for what you are trying to load.

I had no problems saving a template with modified record settings. On starting a project from the template the modified record settings were intact.

It's not a theory , all our applications work identically with project settings. You have to save the project file for the setting to be saved as part of the project or template. This is why its listed in preferences under "Project". You can read this in the help here.

Style dials are internally fx chains but they don't use Sonitus plugs internally. However FX chains and prochannel FX chains are all properly handled and any Sonitus plugins present will get migrated correctly.

@Dana Elston They do but you must ensure that "replace on project load is enabled" Please read the section on Automatic Migration from Sonitus plugins in Sonar

I've replied to your duplicate thread in the main forum. Its user error, not a bug. This thread is only to discuss and report issues related to the latest update, not general issues. Regarding general bugs you can either report them to support or from the help menu itself.

Unrelated to this update. You have some plugin in the circuit that are exposing latency. There is no other way for latency to happen in the DAW. You will have to troubleshoot your signal path to determine what's causing the latency. In Sonar there are useful tooltips to help you find out the net latency for an FX rack or a plugin or a track/bus. Hover over any FX rack or plugin header to see the net latency. You can also see net latency on a track or bus by looking in the inspector.

@Michael Heavner Its clearly noted that the record settings are per project settings. Changing it in the preferences will have no permanent effect unless you save your project. In your video you cancelled the save so of course it will not retain any changes you made. This is not a bug - its how the application is designed to work.

Please don't spam this thread with issues not related to the current release. Unrelated posts will be removed.

@foldaway I sent you a pm

The audio driver bit depth displays the but depth that the driver is currently reporting. In ASIO mode you cannot change the driver bit depth from the host. In fact most drivers don't allow you to change the bit depth and it's fixed. A Sonar project can contain audio at multiple bit depths - 16, 24, 32, 64. If you pick a record bit depth different from the driver bit depth it gets down or up converted to the specified depth. There is no value in choosing a record bit depth higher than what your driver can do.

Nobody else is reporting this so record a video so we can see what exactly is happening.

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?