Sonar 2025.07 Feedback

[Noel Borthwick]

11 hours ago, Matthew Carr said:

Does anyone else find that the Stop button on the transport (or by pressing spacebar) is now really quite laggy?

Playback starts instantly, but after pressing stop icon (or spacebar)

a) Playback stops instantly
b) The green play icon remains green, the stop icon remains grey
c) There is a delay of around 50ms. During this time it's possible to click on the start button again, but playback doesn't start until the delay reaches an end.
d) After the delay finishes, it's possible to press play again and playback starts immediately.

This means if I'm using spacebar to review a hit or short section of playback pressing spacebar works the first time with immediate playback. But after pressing spacebar to stop playback, I can't immediately press the spacebar to listen again - the delay kicks in.

No-one else is reporting this, so maybe it's specific to me - if anyone sees the same, pls chime in and will raise as bug.

Behaviour is the same for the pause button.

Using latest version of Sonar (build 84) with an XR18 interface in ASIO mode with a buffer of 128 samples (changing buffer size has no effect on this transport delay)

EDIT 1: Tested this on same project / hardware in CbB , and there is no delay when stopping playback.

EDIT 2: Tested this on same project / hardware in Sonar (31.06.0.048) , and there is a delay

Ensure that fade on stop is set to zero.

[brundlefly]

12 hours ago, Matthew Carr said:

c) There is a delay of around 50ms. During this time it's possible to click on the start button again, but playback doesn't start until the delay reaches an end.

I would think the delay must be a significantly larger fraction of a second to be noticeable much less bothersome. 50ms is on the order of the fastest double-click the most agile mouse handlers can achieve.

[Matthew Carr]

9 hours ago, David Baay said:

I would think the delay must be a significantly larger fraction of a second to be noticeable much less bothersome. 50ms is on the order of the fastest double-click the most agile mouse handlers can achieve.

Sorry, brain fade 😒... around 500ms

[Matthew Carr]

9 hours ago, David Baay said:

I would think the delay must be a significantly larger fraction of a second to be noticeable much less bothersome. 50ms is on the order of the fastest double-click the most agile mouse handlers can achieve.

Sorry, brain fade....😒 The delay is around half a second, so 500ms

10 hours ago, Noel Borthwick said:

Ensure that fade on stop is set to zero.

The Fade on stop is set to 0 - perhaps there is another setting that could cause this behaviour? Seems plausible given behaviour is not present in my instance of CbB on same PC

17 hours ago, Colin Nicholls said:

@Matthew Carr, try disabling FX at the project level (it's the button in the Mix Module) and see if the behaviour changes. If it does, then the problem is being caused by one or more FX plugins.

Disabling FX has no effect - this behaviour occurs even in an empty project (e.g. start Sonar, select create Basic project)

[Noel Borthwick]

What is your driver mode and which audio interface are you using? Have you tried resetting your aud.ini?
If its happening in a blank project this has to be either settings or driver related. Definitely no code to delay stopping playback in Sonar other than what I showed.

[aleo]

I downloaded and installed the new 084 build today, but as soon as I initiated Sonar and selected a project several problems appeared in Track View:  corrupted volume envelopes in some clips, corrupted jump line after the last node in the tracks instead of a smooth row of dots.  black bar at top of clip is messed up, in the time or measure line at the top of the Clips Pane, both the numbers and tick lines are corrupted.  See the attached screenshots.  Maybe something went wrong with the download; please advise. 

[msmcleod]

22 hours ago, aleo said:

I downloaded and installed the new 084 build today, but as soon as I initiated Sonar and selected a project several problems appeared in Track View:  corrupted volume envelopes in some clips, corrupted jump line after the last node in the tracks instead of a smooth row of dots.  black bar at top of clip is messed up, in the time or measure line at the top of the Clips Pane, both the numbers and tick lines are corrupted.  See the attached screenshots.  Maybe something went wrong with the download; please advise. 

@aleo-  Can you send your .cwp file to @Jonathan Sasor - we'll take a look.

[gmp]

35 minutes ago, msmcleod said:

Can you send your .cwp file to @Jonathan Sasor - we'll take a look.

I just sent it

[Matthew Carr]

On 7/15/2025 at 4:31 PM, Noel Borthwick said:

What is your driver mode and which audio interface are you using? Have you tried resetting your aud.ini?
If its happening in a blank project this has to be either settings or driver related. Definitely no code to delay stopping playback in Sonar other than what I showed.

 Thanks for taking the time to respond to this Noel

I'm using an Behringer XR18 as my audio interface, ASIO Driver

The same settings/hardware are used for CbB and I don't get the delay.  I've compared screen by screen between Sonar and CbB and they have the same settings, with the exception of Offline Render using Elastique Efficient in Sonar vs Elastique Pro in CbB.

I deleted the Aud.Ini file (%USERPROFILE%\AppData\Roaming\Cakewalk\Sonar) and restarted Sonar to recreate it, but the delay remains - the new aud.ini is attached 

Comparing the Aud.ini files between

Sonar  (%USERPROFILE%\AppData\Roaming\Cakewalk\Sonar) , and
CbB     (%USERPROFILE%\AppData\Roaming\Cakewalk\Cakewalk Core)

the only differences are for the offline rendering and some settings which look like they have been added/deprecated between the two versions

I'm a bit stuck now, so any advice gratefully received!

AUD.INI

[Noel Borthwick]

Are you using any control surfaces?

[Matthew Carr]

11 minutes ago, Noel Borthwick said:

Are you using any control surfaces?

Yes. I use AZController and Cakewalk Generic  Surface

As a test, I removed the control surfaces from the Preferences Dialog, restarted Sonar, and the delay persists

Short vid to try and show the issue

 

 

Edited 3 hours ago by Matthew Carr

[Noel Borthwick]

Can you try a different audio interface to rule it out? If you dont have anything handy use your onboard audio device.

[aleo]

Mark, thanks for responding.  I sent a project file to Lois at Support earlier today along with a new screenshot.  Will  send copy to Jonathan.   BTW, the second time I initiated Sonar after my upgrade to build 084 it crashed (my first crash with Sonar).  I have the mini-dump file, but will need to use something like Drop Box and I don't have an account with them yet.

[Matthew Carr]

26 minutes ago, Noel Borthwick said:

Can you try a different audio interface to rule it out? If you dont have anything handy use your onboard audio device.

Tried with a Behringer UMC 404 HD and a BOSS GT001 - easiest things I had lying around that had ASIO

The delay persists with both of the other ASIO interfaces. Changing to WASAPI Exclusive, and the delay remains on both these interfaces.

This must be something specific to my install, as no one else seems to have this issue. Think the best test I could do now would be to install Sonar on different PC from scratch, and see if this problem persists - that's a tomorrow task though.

Edited 3 hours ago by Matthew Carr

[Арсений Гордеев]

Articulation maps

A very important part of using the software for me is working with articulations. In Sonar, I encounter the inability to assign articulations directly to notes, and I am forced to add them to a region. There are many scenarios where this approach is necessary. For example, in arpeggios, where all notes are spiccato and the last note of the passage is always staccato. It would be easier to select all the necessary notes and apply the desired articulation to them.

[Jim Fogle]

Are you using Articulation Maps or putting the articulation notes in the midi note window?

Edited 1 hour ago by Jim Fogle

[msmcleod]

27 minutes ago, Арсений Гордеев said:

Articulation maps

A very important part of using the software for me is working with articulations. In Sonar, I encounter the inability to assign articulations directly to notes, and I am forced to add them to a region. There are many scenarios where this approach is necessary. For example, in arpeggios, where all notes are spiccato and the last note of the passage is always staccato. It would be easier to select all the necessary notes and apply the desired articulation to them.

That's just how articulations work in Sonar.  They apply to everything underneath them.  Articulations are implemented in so many different ways within VSTi's, it would be impractical (probably impossible) to implement what you're asking for and have it work in all scenarios.

In your example above, the easiest way would be to cut the duration of the articulation short of the last note.
 

[Арсений Гордеев]

6 минут назад msmcleod сказал:

Именно так работают артикуляции в Sonar. Они применяются ко всему, что находится под ними. Артикуляция реализуется в VSTi настолько различными способами, что было бы непрактично (вероятно, невозможно) реализовать то, о чем вы просите, и заставить это работать во всех сценариях.

В приведенном выше примере самым простым способом было бы сократить длительность артикуляции до последней ноты.
 

This is strange, because in any other DAW, the articulation maps work exactly as I say. Based on your response, I assume that there is no hope for changes in the behavior of this feature in the future? It would be a shame if this were the case. Thank you for your response!

[Арсений Гордеев]

10 minutes ago, Jim Fogle said:

Are you using Articulation Maps or putting the articulation notes in the midi note window?

Articulation Maps