Sonar 2025.08 Feedback

[Jean Corivo]

Print a marker list.

There seems to be a problem with markers in this version. I don't know if this problem is recent, but it is now impossible to print a marker list or export them to PDF format. This is quite useful when composing film music. If this could be fixed quickly, it would be greatly appreciated so that we don't have to redo the spotting session manually.

I checked the manual and indeed it says this on page 432: To display the Markers view, choose Views > Markers. From the Markers view, you can use the File > Print and File > Print Preview commands to print a listing of markers.

Edited Monday at 05:21 PM by Jean Corivo

[Promidi]

4 hours ago, Jean Corivo said:

There seems to be a problem with markers in this version

Looks like this function was borked ages ago.

I just tried it in Sonar Platinum, and when Markers list is displayed, Print and Print Preview is greyed out in there  as well.

Maybe drop a note to Sonar support.

https://help.cakewalk.com/hc/en-us/requests/new

[RobertLogan]

Hello,

I have been having a problem since the last two updates, which is that projects never remember my zoom settings. I have never had this problem with any version of Cakewalk or Sonar before (have been using Cakewalk since the days of Home Studio 9). Usually, when I'd open an old project, tracks would be sized as I'd last left them in all previous versions of Cakewalk and Cakewalk by Bandlab, and zoom settings would be the same as where I last left them. Now it is always zoomed out, which is very time consuming to deal with upon opening a project every time...

Edited yesterday at 01:14 AM by RobertLogan

[Promidi]

1 hour ago, RobertLogan said:

Hello,

I have been having a problem since the last two updates, which is that projects never remember my zoom settings.

My projects have always remembered my zoom settings.

My workflow is as follows:

I use a locked screenset and a Workspace where I have configured that workspace not to load Windows Layouts and Screen settings.

If I want to make a change to my screen layout in a given project, I open that project, make the change to my screen positions and zoom levels.
Then quickly unlock, then lock my screenset. 
Then I save my project.

This has always worked for me.

[Igor]

Hello!
This can't really be classified as a "bug", but it has been happening for the last few years with Cakewalk by Bandlab, and now with the new Sonar.  After reinstalling/clean installing the system (Windows), when opening old projects, a not entirely clear phenomenon occurs with some instruments - they do not sound, that is, a signal goes to them, the entire configuration remains unchanged, but there is no sound. At the same time, Cakewalk/Sonar do not show any notifications or warnings, the loading of projects is completely normal. This happened (and happens) with TTS-1, with Kontakt from Native Instruments, with some synthesizers, a couple of times with instruments from Spectrasonics, and today it happened with the Spire synthesizer. If you add the same instrument to the VSTi slot again, and redirect the output from the MIDI track to it, the sound appears and everything starts working normally. Apparently, CbB and Sonar for some reason do not recognize the synth identifier in old projects on a clean system, although the same instrument and the same version are installed. Is there any way to fix this situation so that this does not happen in the future?

[pistolpete]

I never had issues with vsts or synths in CbB. But when I converted over to the new Sonar, it deleted about a dozen vsts, including TTS-1, GroovePlayer, Sonitus effects and a number of others. It took a lot of time and effort to recover them. The GroovePlayer never restored correctly. Although I don't directly use it, somehow it's tied to the metronome, which is now permanently broken. There are now updates and changes to vsts for "core vsts" which are only available if you pay for a subscription. I am very concerned this might break the stable vsts that I have been using for a long time. This seems to me like a risk when any updates are applied now. There are a lot of bugs being reported from others after the switch over. Add to that, the new Sonar software isn't really supported on Windows10, adding driver issues and things breaking for that update too, for those who update OS. It's a lot of instability right now. Hopefully they get things fixed. 

[David Baay]

On 8/25/2025 at 9:06 AM, Ted Raven said:

When starting to play an audio track, the audio engine starts along with the audio playback at mesure 1:01:000 resulting in an audible click noise.

That is not typical and most likely due to some specific plugin that is misbehaving or possibly some other configuration or hardware/firmware/driver issue that needs to be addressed at the source.  And whereas the root cause would likely also affect earlier releases of Sonar and CbB, it doesn't belong in this release-specific feedback thread; you should bring it up in a new thread on the Sonar subforum or report it to Support for troubleshooting assistance. I know of only a few very specific situations in which a project will not start smoothly from 1:01:000, mostly involving the use of hardware synths though I have encountered issues with some VSTs for which other solutions are possible aside from moving the start time to 2:01.

Likewise the suggestion to provide some "pre-roll" or alternative measure-numbering functionality to address bonafide cases where starting playback at 1:01:000 is not viable does not belong here; it belongs in the general Feedback Loop subforum where it has been proposed and discussed before.

[David Baay]

8 hours ago, Igor said:

If you add the same instrument to the VSTi slot again, and redirect the output from the MIDI track to it, the sound appears and everything starts working normally. Apparently, CbB and Sonar for some reason do not recognize the synth identifier in old projects on a clean system, although the same instrument and the same version are installed.

I have never encountered a case of "no sound" that couldn't be resolved by identifying the specific root cause and addressing it directly. Replacing a synth or track is just incidentally addressing the root cause by setting eveything to defaults and re-initializing the synth.

Though there are a truly astounding array of possible causes of "No Sound" that sometimes make the brute-force solution more attractive than taking the time to troubleshoot properly, I will mention one of the the most insidious and confounding possibilities which is that RPN/NRPN messages in third-party MIDI have silenced the synth output which can be addressed by re-loading the synth by the Bypass/Power button in Synth Rack and enabling 'Do Not Intercept NRPNs' in properties and/or deleting them from the MIDI clip using Select > By Filter.

Edited 13 hours ago by David Baay