Jump to content

Sonar 2024.12 Feedback


Recommended Posts

Hi all - please use this topic to post feedback specific to the Sonar 2024.12 release. Release-specific feedback is valuable to us, and consolidating it in a single topic is extremely helpful.

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.

Thanks in advance!

Sonar 2024 Overview

  • Like 1
  • Thanks 3
Link to comment
Share on other sites

I reported the issue "impossible to stop playback" when track pane is horizontally zoomed to the max with version 2024.09.
Issue is still there in version 2024.12

Kind regards, Marc.
----------
Hello,
With Sonar 2024.09:
When track pane is horizontally zoomed to the max, and project is playing, User Interface become unresponsive and it is impossible to stop playback, nor by the keyboard, nor by mouse, nor by midi control.
This is not project specific, the only way to stop playback is to wait the end of project or to kill cakewalk application by the task manager.

This was corrected in CbB back in 2020, but the issue is back in Sonar 2024.09

Kind Regards, Marc.

Link to comment
Share on other sites

Hi,

1. Just Updated via Sonar notification Download was Update Release Setup_30.12.0.004.exe but the 'Help About' still displays version 2024.11 (build 120 64bit) 

Am I still a version behind?  or is the Banner wrong? 

2. When trying to use 'Clip, Clip Automation, Clip Gain' when a waveform is selected, it only changes ( raise/lower) part of the waveform selected.  (See attached) 

3.  And where is the Set Project Start and End Markers command located now?    (Not that the End marker worked anyway! ) 

 

Anyhoo - Appreciate the updates  

Clip Gain.png

Link to comment
Share on other sites

2 minutes ago, icu81b4 said:

Hi,

1. Just Updated via Sonar notification Download was Update Release Setup_30.12.0.004.exe but the 'Help About' still displays version 2024.11 (build 120 64bit) 

Am I still a version behind?  or is the Banner wrong? 

2. When trying to use 'Clip, Clip Automation, Clip Gain' when a waveform is selected, it only changes ( raise/lower) part of the waveform selected.  (See attached) 

3.  And where is the Set Project Start and End Markers command located now?    (Not that the End marker worked anyway! ) 

 

Anyhoo - Appreciate the updates  

Clip Gain.png

 

It sounds like you may have downloaded the update, but not installed it. The Start Screen will also display the currently installed version, and you can install the update from there as well

  • Like 1
Link to comment
Share on other sites

17 hours ago, Marc Bleuwart said:

I reported the issue "impossible to stop playback" when track pane is horizontally zoomed to the max with version 2024.09.
Issue is still there in version 2024.12

Kind regards, Marc.
----------
Hello,
With Sonar 2024.09:
When track pane is horizontally zoomed to the max, and project is playing, User Interface become unresponsive and it is impossible to stop playback, nor by the keyboard, nor by mouse, nor by midi control.
This is not project specific, the only way to stop playback is to wait the end of project or to kill cakewalk application by the task manager.

This was corrected in CbB back in 2020, but the issue is back in Sonar 2024.09

Kind Regards, Marc.

Thanks for the report. We've improved this for the next update so that it thins the scroll frequency when playing. 
I'm assuming that you zoomed in for an edit but forgot to zoom out? Generally, it's not very useful to be so heavily zoomed in. In any case, its fixed for next time.

  • Like 3
Link to comment
Share on other sites

1 hour ago, Noel Borthwick said:

Thanks for the report. We've improved this for the next update so that it thins the scroll frequency when playing. 
I'm assuming that you zoomed in for an edit but forgot to zoom out? Generally, it's not very useful to be so heavily zoomed in. In any case, its fixed for next time.

Thanks for the reply, good to know that it'll be improved.
Yes sometimes it's useful to heavy zoom in for adjusting timing of waveforms, and sometimes I forget to zoom out and when I start playback, I can't stop Sonar and have to wait the end of the project. Some live recording projects can have very long duration ....

 

  • Thanks 1
Link to comment
Share on other sites

On 12/10/2024 at 4:39 PM, Jonathan Sasor said:

 

It sounds like you may have downloaded the update, but not installed it. The Start Screen will also display the currently installed version, and you can install the update from there as well

Thanks for the reply Jonathan,  I switched on my PC this moring and Sonar is now displaying the updated version  (I didn't need to re-install or run the .exe again) 

So that's item 1. sorted. 

Item 2.   I can set the End  marker to Now time ... but it doesn't stop the project. 

Item 3. Is still an issue,  where the clip gain doesn't adjust all the waveform. See below. 

Thanks

Alan.

 

 

Edited by icu81b4
Add gif
Link to comment
Share on other sites

New issues found:

1. While I had an open project, I opened the File menu to export audio and the option wasn't there. I realized that the menus were all set up like there were no projects open. I couldn't even close the open project - I exited Sonar and restarted and menus were fine. I think related - some time earlier in the session, I turned on the Preference to "Allow Only One Open Project at a Time". I'm guessing I had 2 projects open, I turned on "allow only 1", then I closed one of the projects. Sonar may now assume I've closed all projects since "there can only be one"...

2. After restarting Sonar due to issue 1, in the quick start menu, my file has " (untitled)" at the end of it, although it has a title, and it doesn't include "(untitled)" in it  :). You can see in the screenshot below that the file in the Sonar title bar doesn't have that odd suffix. I imagine this is related to issue 1.

image.png.cf857475f16938a2dc906740028208b4.png

Old issues reported previously:

3. The Inspector has graphical issues in the bottom right side when scrolling content down - in the area that is fixed on the left side with track name and number in it.

4. ProChannel module UI is not visible in the Console view immediately on creation. Closing the Console and reopening it fixes this. See screenshot.
image.png.f30f362e2a9e2fce9e42ae686bf2a410.png

 

Same display set up as before: Dual monitors: 1920x1080

Windows Scaling: 125%

Sonar Display Scale: 110%

 

Edited by crazy sniffable
Link to comment
Share on other sites

I updated Sonar yesterday when I opened it. I am working on a new piece in the new Sonar , and am having a problem in Unify with the Unified Plasmonic library. On a Unify track that was added in Sonar, I selected the Plasmonic Unified library and selected one of the patches. When I save the project, and reopen it, Unify still has the title of the patch I selected showing, but when I double click on Plasmonic, it shows (and plays) the default patch (After the Rain). If I click on the patch I had selected (which is still highlighted) then Plasmonic shows (and plays) the corrected patch. Each time I save the project, it reverts and I have to go to all the tracks that I had selected from Plasmonic and reset them. All of the tracks in my project are Unify tracks, and the other tracks that are not Plasmonic do not revert or change. 

I just created a new project and added a single track with an instance of Unify. Then selected Unified Plasmonic and chose the Polariton patch. Then I saved the project, closed Sonar, and reopened it, and opened Unify on that track. It showed Polariton as the title, but when I double clicked on Plasmonic, it showed the default patch.

This did not happen in the previous version of Sonar as I have been working on this piece for about a month.
 

It turns out that this problem was using an outdated version of Plasmonic. It is not a problem with Sonar.  After I updated Plasmonic, everything works the way it should.

Edited by Martin Schiff
Problem solved
Link to comment
Share on other sites

Here’s one . I have always used Track Templates for VST instruments. For Acoustic Bass I use Rapture. I also put the Boost11 in the bin set at boost off and limiter at -5db. 
When I load the track template everything works perfectly except the bass is too loud. 
Boost 11 is returning to its stupid default which is boosted 6db and limiting to 0. 
 

All my others templates the effects are maintaining my settings.
I’ve tried re saving it and I even deleted and re made one. 

Link to comment
Share on other sites

8 hours ago, Sock Monkey said:

Here’s one . I have always used Track Templates for VST instruments. For Acoustic Bass I use Rapture. I also put the Boost11 in the bin set at boost off and limiter at -5db. 
When I load the track template everything works perfectly except the bass is too loud. 
Boost 11 is returning to its stupid default which is boosted 6db and limiting to 0. 
 

All my others templates the effects are maintaining my settings.
I’ve tried re saving it and I even deleted and re made one. 

Have you reported it through the official report page?

Link to comment
Share on other sites

Well I have no serious issues to report with the new 2024.12 release, just SERIOUSLY NOTICABLE PERFORMANCE gains.

It's like my old AMD FX 8370 CPU is on a very well-deserved vacation running. 

50 Audio/MIDI tracks with 2 instances of Addictive Drums 2 using Alesis Sample Pad Pro as MIDI controllre.,

Novation Impulse 61 MIDI keyboard controller used for;

2 instances of Dimension Pro

Cakewalk SI Strings

Cakewalk TTS-1

ProChannel modules, various Waves, Universal Audio, Softube, and iZotope audio FX plugins.

Audio processing maxing out @ 23%, Engine load maxing out 43%, "O" (zero) late buffers.

SonarPerformance2024_12.thumb.jpg.38ac93ad417024ed5b16940961b0f0b4.jpg

 

Using 6.8 GB of 32GB RAM

CakewalkSonarperformancestatsRAMusage2024-12-11_6-46-26.jpg.bbc8b68d4761d855d7f947f5facf90f1.jpg

 

Focusrite Scarlett 18i20 gen 2 running smooth as silk @ 24/48 mix latency 4 ms

Sonar4msrecordinglatency2024-12-13_4-16-33.jpg.d376412ded7c0e871deb88a226e93101.jpg

 

After performing a glitch free 3-4 hour recording session, including audio mixing session in Bandlab Studio, it sounds like THIS!

Not exactly my ultimate best, but certainly not bad at all for the time I put into it and spent 'field testing' Sonar. I am EXTREMELY PLEASED!

 

 

Edited by Steev
  • Like 1
Link to comment
Share on other sites

On 12/11/2024 at 9:41 AM, icu81b4 said:

Thanks for the reply Jonathan,  I switched on my PC this moring and Sonar is now displaying the updated version  (I didn't need to re-install or run the .exe again) 

So that's item 1. sorted. 

Item 2.   I can set the End  marker to Now time ... but it doesn't stop the project. 

Item 3. Is still an issue,  where the clip gain doesn't adjust all the waveform. See below. 

Thanks

Alan.

 

 

 

Item 2. is now Sorted - Thanks @David Baay

 

Just Item 3.  Where Clip Gain only alters a part of the waveform instead of all of it. 

 

 

Link to comment
Share on other sites

53 minutes ago, icu81b4 said:

Clip Gain only alters a part of the waveform instead of all of it. 

I coudn't reproduce this. A few questions:

Is it audible or just a waveform drawing error?

Have you seen more than one instance of this?

Is it a single clip in a single-lane track?

Was the range of the lowered gain segment modified after setting the level?

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