Noel Borthwick

We've resolved the root cause of this issue with @matt and it will be fixed in the next release.

Please post plugin feedback in this thread.

We converted only the stock built in Sonitus factory presets, not user presets. You are talking about the presets you made in the Cakewalk preset picker here: Those presets are stored here: HKEY_CURRENT_USER\Software\Cakewalk Music Software\ActiveMovie\Presets However, the format isn't directly compatible with the core plugins which are VST3. I'd have to write some special migration code inside Sonar to allow them to be converted. I'll look into it and see what's involved. In any case it's not something that an end user will be able to do since only the plugin has knowledge of how to convert its legacy presets not even Sonar.

When it happens if you load the project again is it still silent? If so send us the project file and we can at least tell you if its routing related.

Well, you have to think about it enough to find out if you have accidently selected a global workspace. Workspaces are designed to save zoom settings, window positions and other view visibility settings, so if you are loading a project and the zoom has changed that is the 90% chance that you chose a workspace at install time and didn't realize it. Losing zoom settings in a project isn't problem others are running into. Make sure "None" is selected here.

Zoom makes good stuff. I have their older Zoom U44 which is quite cool. It has 4 in's and interfaces with the Zoom mic capsules so you can either use the 2 XLR inputs or plugin in a stereo mic capsule and use that for field recordings. It can also work on battery but uses USB power from a laptop. It can be quite useful when you need a portable solution. It has an ASIO driver too which is rare for devices in that class.

Have you updated to the latest version of Sonar from Product Center? The latest one is 31.08.0.035,

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.