Sonar 2025.08 Feedback

[pistolpete]

4 hours ago, Jim Stamper said:

Are you using the free version or paid version? 

I'm running the free version. I choose not to pay for this. Due to the risk of having vsts deleted or other digital mishaps to my projects, I've paused on Sonar's use for now. It's wait and see.  I only use it for legacy projects anyway.

[David Baay]

1 hour ago, Gene Martin said:

I'm seeing the same issues reported in previous posts: Suprisingly high processor usage

I believe there was only one other mention of high CPU usage in 8 pages of posts to this thread, and CTO Noel Borthwick responded that there have been no changes to the audio engine that would have precipitated a problem.

Every new release elicits some spurious reports of performance issues that almost inevitably turn out to be due to other causes. You'll need to look for other changes to your environment, Sonar configuration or project content that would account for this.

[Ted Raven]

On 8/26/2025 at 6:06 PM, David Baay said:

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

I don't have this issue in CbB nor did I have it in any old Sonar version. So it cannot be a hardware/driver issue nor an old issue. Also, it happens with or without the use of plug ins. And even with only MIDI tracks. 2025/08 is my first version of the new Sonar, so I cannot tell if it happened in previous versions as well.

Edited 13 hours ago by Ted Raven

[David Baay]

7 minutes ago, Ted Raven said:

Also, it happens with or without the use of plug ins. And even with only MIDI tracks.

It only happens at 1:01:000? If it doesn't also happen when starting playback further into the project, it's not the audio engine.

What audio interface and driver mode?

Did you maybe have a non-zero Fade On Start value set in older versions that was obscuring the click?

Maybe share a simple demo project just to be sure it's not the project itself.

Try disabling the 64-bit Mix Engine.

Also try Reset Config to Defaults in Preferences > Configuration File. Sonar will back up your AUD.INI and replace it with a default.

 

 

[Ted Raven]

20 minutes ago, David Baay said:

It only happens at 1:01:000? If it doesn't also happen when starting playback further into the project, it's not the audio engine.

What audio interface and driver mode?

Did you maybe have a non-zero Fade On Start value set in older versions that was obscuring the click?

Maybe share a simple demo project just to be sure it's not the project itself.

Try disabling the 64-bit Mix Engine.

Also try Reset Config to Defaults in Preferences > Configuration File. Sonar will back up your AUD.INI and replace it with a default.

 

 

Ha, good point. I actually haven't tried yet if it happens when I start the playback anywhere later than 1:01:000.

Audio interface: Focusrite Scarlett 2i2 3rd Gen.
Driver mode: ASIO.

No Fade, no CCs in the track at all (only one track).

I will disable the 64-bit mixing engine and try.

I will also do the reset (though I have not changed much in the preferences yet). So I won't need a config backup.

Thanks for your help.

[Noel Borthwick]

Anyone experiencing problems and using Focusrite interfaces please first ensure that you contact their support for the newest drivers since there are known problems as discussed in this thread,

[David Baay]

6 hours ago, Ted Raven said:

Focusrite Scarlett 2i2 3rd Gen.

Noel beat me to it.

 

[jeejeestudio]

Hi,

When I choose Utilities--> Mackie Control -1

This is the view I get. 

I can increase the opened window when pulling the edges, but it is not remembered.