Jump to content

Sonar 2025.08 Feedback


Recommended Posts

31 minutes ago, foldaway said:

After updating to build 31.08.0.035, I'm seeing lower playback performance.  The track I'm working on is complex but played smoothly in the previous build but not in this build.
Is there any way to rollback to the previous build, so I check test further?

Check %USERPROFILE%\downloads\Cakewalk

Link to comment
Share on other sites

1 hour ago, foldaway said:

After updating to build 31.08.0.035, I'm seeing lower playback performance.  The track I'm working on is complex but played smoothly in the previous build but not in this build.
Is there any way to rollback to the previous build, so I check test further?

https://www.windowslatest.com/2025/08/20/microsoft-is-investigating-windows-11-kb5063878-ssd-data-corruption-failure-issue/

 

Link to comment
Share on other sites

Yeah, it's set to 24-bit  in Preferences. I'm not trying to set it from the module.
I'll take a couple of screenshots when I'm at the studio later.
Thanks for your replies.

EDIT:  Thanks guys. Yes, I was looking under Device Settings - Audio Driver Bit Depth which displayed a greyed out "24 bit"
David got it right with 'Record Bit Depth' under Preferences > File Audio > Data.
Now the Transport Module shows I've set it up properly.
Does this mean that audio driver bit depth displays the maximum bit depth available  and the record bit depth is what the user sets it at?

Thanks again and BR
 

Edited by LouHela
Solution found
Link to comment
Share on other sites

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.

  • Like 3
Link to comment
Share on other sites

13 hours ago, Promidi said:

Check %USERPROFILE%\downloads\Cakewalk

Thanks.

After reinstalling 31.08.0.014 the performance was back to normal and the track played without issue.  So it seems there definitely is something going with the latest build.

nb. on Win10, so not related to the recent Win11 Update issue.

Edited by foldaway
Link to comment
Share on other sites

2 hours ago, foldaway said:

So it seems there definitely is something going with the latest build.

Just to be clear, how are you judging that performance has changed?

The only thing I can think of that could have affected performance would be Sonar replacing Sonitus plugins with the new "Core" VST3 versions that might (?) have been removed on rollback.

If the affected projects are using Sonitus, try disabling 'Replace if Possible...' under Preferences > File > VST Settings > VST3 Migration with the update installed.

Link to comment
Share on other sites

1 hour ago, David Baay said:

Just to be clear, how are you judging that performance has changed?

The only thing I can think of that could have affected performance would be Sonar replacing Sonitus plugins with the new "Core" VST3 versions that might (?) have been removed on rollback.

If the affected projects are using Sonitus, try disabling 'Replace if Possible...' under Preferences > File > VST Settings > VST3 Migration with the update installed.

Hi David,

The project I'm working on doesn't use any Sonitus plugins, so that's not going to be an issue on this occasion.

Re: Judging performance;

With the latest build, the most complex parts will be played back with 95-100% drop-out.  Such that playback will continue  but the audio will be mostly silent for these parts.

With build 31.08.0.014, these complex parts playback with zero drop-out.

All settings remain the same between versions, as far as I'm aware

Link to comment
Share on other sites

7 minutes ago, Noel Borthwick said:

Please don't spam this thread with issues not related to the current release. Unrelated posts will be removed.

Sir, this is not spam. I am addressing an issue and seeking help. Please share the link to report the bug (even in a PM). I am sincere and have been a Cakewalk user for over 30 years.

Link to comment
Share on other sites

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.

Quote

We request that  discussion in this thread be restricted to issues directly concerning this release, to make it easier for us to assist users. For other topics, kindly use the feature request section or create new posts.  Off topic messages will be deleted.

Regarding general bugs you can either report them to support or from the help menu itself.
image.png

Link to comment
Share on other sites

1. I create a virtual instrument track with IK Multimedia Modo Drum, actually an instrument track and a related MIDI track.

When I play or use the piano roll, I can hear the drums. -> Fine

2. Since there is only the piano roll, I change to a drum map (on the MIDI track output I select New Drum Map and select the desired drum map from the list.

When I open the piano roll, the drum map is shown but I cannot hear the drums anymore. The instrument track seems to got disconnected from the MIDI track.

I tried several thing like renaming, deletion and re-creation of the tracks and so on, without success.

Is this a bug or am I doing something wrong?

 

Btw., nice move showing the note names in the piano roll.

Link to comment
Share on other sites

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.

Suggestion: Delay the playback for about a quarter second after the audio engine has been started (which is the solution, other manufacturers use and also solves potential MIDI timing glitches in the beginning of a track).

Of course, I could place my audio from mesure 2 instead of 1 but that would interfere with the time an measure numbers, unless there was an optional delay, that lets the track begin with measure 0 instead of 1 and still starts the time with measure 1.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...