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 August 30 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.

[jeejeestudio]

Hi,

I'm coming back to color.

In a previous thread I asked about color of the tracks, which is working.
But what about color of the clips, like the headers of it, what I see now is actually all black (with current selected settings) and some small colored things which are the notes.

Is this possible to add in a future update for visibility (e.g. people who are not color-blind) ?
Also in this screenshot I do not understand why the upper tracks are reddish. Perhaps I changed something of which I don't know.

I checked the manual but on the track view and clips there is not much color info.

Thanks a lot.

[Bahmanyar Afroozeh]

5 minutes ago, jeejeestudio said:

Hi,

I'm coming back to color.

In a previous thread I asked about color of the tracks, which is working.
But what about color of the clips, like the headers of it, what I see now is actually all black (with current selected settings) and some small colored things which are the notes.

Is this possible to add in a future update for visibility (e.g. people who are not color-blind) ?
Also in this screenshot I do not understand why the upper tracks are reddish. Perhaps I changed something of which I don't know.

I checked the manual but on the track view and clips there is not much color info.

Thanks a lot.

The Redish colors are Because of Record arm of those tracks are enable

[David Baay]

1 hour ago, jeejeestudio said:

But what about color of the clips, like the headers of it, what I see now is actually all black (with current selected settings) and some small colored things which are the notes.

Yes, notes/waveforms automatically take on the color selected for the track while the background remains dark by default. You can uncheck Use Track Colors in clip properties and set custom foreground (notes/waveforms) and background clip colors independently of the track color. The foreground will initially be assigned the current track color.

[Benny Bear]

Sonar lastest version. Don't know if this is related to latest updated, but it has only just started happening. When I open a project, all the tracks are at the large height and all tracks are showing (even if they were hidden before). I have to start each session by resizing all the tracks to my requirements. Slightly annoying. Any ideas?

[jeejeestudio]

On 8/31/2025 at 7:31 PM, Bahmanyar Afroozeh said:

The Redish colors are Because of Record arm of those tracks are enable

Ah, thanks!

[jeejeestudio]

23 hours ago, David Baay said:

Yes, notes/waveforms automatically take on the color selected for the track while the background remains dark by default. You can uncheck Use Track Colors in clip properties and set custom foreground (notes/waveforms) and background clip colors independently of the track color. The foreground will initially be assigned the current track color.

Thanks. But to me that seems cumbersome to use.
Would be nice if the header of a clip takes over the color of the track automagically.
Something like this:

 

[David Baay]

On 8/6/2025 at 12:17 PM, Paul B said:

Sometimes I can playback or record for minutes at a time, sometimes the audio engine will fall apart every few seconds or so, it's seemingly random. I deleted a bunch of tracks to see if that helped, no difference. 

Try:

- Disabling the 64-bit Double Precision Mix Engine.

- Bypassing all plugins via the Fx button in the Mix module.

 

[David Baay]

4 hours ago, jeejeestudio said:

Would be nice if the header of a clip takes over the color of the track automagically.

Feature requests belong in the general Feedback Loop subforum. This thread is for feedback/questions/issues specific to the 25.08 release.

[Promidi]

On 8/26/2025 at 1:32 AM, Jean Corivo said:

but it is now impossible to print a marker list

I just revisited this.

What happens if you set the Makers Window to non floating? Is the File > Print is still greyed out?

On my PC, I set the Makers Window to non floating, then I was able to do a File > Print.

[mgustavo]

On 9/1/2025 at 5:44 AM, Benny Bear said:

When I open a project, all the tracks are at the large height and all tracks are showing (even if they were hidden before). I have to start each session by resizing all the tracks to my requirements.

Hi, also about this customization issue I've noticed music notation in Staff View is bigger than normal when I open an existing project (zoomed in exhibition).
However I'll watch if that happens with new projects, as recommended by Ben Staton in this thread.

Also I'd like to comment about an improvement I saw in Staff View (I guess it's from an early Sonar update).
I remember that after selecting a different size to printed score one also had to click in the preview image to see changes. In Sonar it seems the issue was fixed, as just after the selection changes will show up. Thanks!

Edited Tuesday at 01:54 PM by mgustavo

[Noel Borthwick]

17 hours ago, David Baay said:

Feature requests belong in the general Feedback Loop subforum. This thread is for feedback/questions/issues specific to the 25.08 release.

Also, this thread is to report issues that are specific to THIS release. Please refrain from using this thread as a general bit bucket for random reports. Make separate threads if you have a different problem.

[Noel Borthwick]

On 9/1/2025 at 4:44 AM, Benny Bear said:

Sonar lastest version. Don't know if this is related to latest updated, but it has only just started happening. When I open a project, all the tracks are at the large height and all tracks are showing (even if they were hidden before). I have to start each session by resizing all the tracks to my requirements. Slightly annoying. Any ideas?

This is indeed a small regression and will be fixed in the next release. See this thread where its already reported.