Sonar 2025.02 Feedback

[Lassi Kangasluoma]

26 minutes ago, Wookiee said:

Is there anything common in the projects, like a particular plugin? 

No. One of the projects does not even have any plug-ins, just pure vocal tracks.

[Wookiee]

When it crashes have you grabbed the dump it generates and looked at the event list.

[Wayne Bangert]

When I use the quick start window I can not get the PLAY LIST files to show. This was a handy feature in the Cakewalk by Bandlab version. I keep those files in a separate folder so when I add the folder location it appears in the drop down list but no files show when selected.

[dantarbill]

I'm seeing a lot of traffic about what I'm thinking is a fairly few users about special edge case issues with 2025.02 (31.02.0.077).

Could I make the assumption that, on the main, this release is stable and installable...or am I just being lazy and failing to read between the lines?

Thanks for your reasonable responses.

[IgoRr]

Just now, dantarbill said:

Could I make the assumption that, on the main, this release is stable and installable

Personally, I can say that this latest version (build 077) is very stable, works reliably, predictably, and is noticeably better than previous versions. Although, there are still some minor flaws, but they do not affect the overall operation of DAW. In any case, everything works quite reliably on my computer.

[DeeringAmps]

Latest build working fine in the office and the studio here. But I’ve only once had an “issue”, affected a small number of users, and that was solved quickly!

t

[Andrey_rbk]

I don’t know if it appeared in this update or perhaps earlier. But I can’t create a new bus from sending to a bus. There are no problems with this in Cakewalk by BandLab.

 

[IgoRr]

1 hour ago, Andrey_rbk said:

I can’t create a new bus from sending to a bus.

I just checked it in my Sonar - everything works completely normally, after assigning a send to a new bus, this one is instantly created without the slightest problem.

Edited April 6 by IgoRr

[Andrey_rbk]

2 hours ago, IgoRr said:

I just checked it in my Sonar - everything works completely normally, after assigning a send to a new bus, this one is instantly created without the slightest problem.

You misunderstood me. Try creating send from an existing send. Exactly how I did it.

[Andrey_rbk]

Here's how it works in Cakewalk and Sonar.
 

 

 

Edited April 6 by Andrey_rbk

[Andrey_rbk]

Next bug.

If you choose to create from a send - New aux track. Sonar crashes.
 

Edited April 6 by Andrey_rbk

[IgoRr]

23 minutes ago, Andrey_rbk said:

Try creating send from an existing send. Exactly how I did it.

Here you go, I did exactly as in your screenshot, and everything works. In addition, when creating a send to a new AUX track, it also works completely normally. You definitely have something wrong with the installation of Sonar, or some problems in the system itself, since such simple actions constantly cause failures.

[Andrey_rbk]

In the first video, when you change the send, why did two sends change at once?

[Andrey_rbk]

5 minutes ago, IgoRr said:

Here you go, I did exactly as in your screenshot, and everything works. In addition, when creating a send to a new AUX track, it also works completely normally. You definitely have something wrong with the installation of Sonar, or some problems in the system itself, since such simple actions constantly cause failures.

In the first video, when you change the send, why did two sends change at once?

[IgoRr]

2 minutes ago, Andrey_rbk said:

In the first video, when you change the send, why did two sends change at once?

Yes, indeed, I just now noticed, this is an obvious bug for the developers to note. But the bus is still created, and then you can manually reassign the sender outputs, and on the second issue, everything works normally, Sonar does not crash.

[Lassi Kangasluoma]

On 4/1/2025 at 3:54 PM, Lassi Kangasluoma said:

Up until now Sonar has been working perfectly, but today it started crashing. Always the same way. The project opens and you can play it, but as soon as you stop the playback, the whole thing freezes.  Same thing with the free version.

From the dump it seems that Kernel32.dll is the culprit. 

Minidump.txt: 
Faulting Module: C:\WINDOWS\System32\KERNEL32.DLL
App Version: 31.02.0.077 (Release)

There was a Windows update yesterday and Kernel32.DLL was modified at 9.31 yesterday. I did a System restore to before that point, but to no avail.  Next step is probably to uninstall Sonar and hope for the best...

disko3_04012025_164533.dmp 2.22 MB · 2 downloads

It seems that this was some type of conflict with my audio interface. When I disconnected everything and restarted, everything worked, even after I connected them back. It happened again, but again, it could be mitigated the same way. 

[Promidi]

On 4/8/2025 at 2:38 PM, Lassi Kangasluoma said:

It seems that this was some type of conflict with my audio interface. When I disconnected everything and restarted, everything worked, even after I connected them back. It happened again, but again, it could be mitigated the same way. 

What happens if you uninstall and reinstall (update if necessary) your audio interface drivers?

[Andres Medina]

I've found what appears to be a bug: 

Exporting audio files adds a (-1) number to the filename (and often duplicates de track name) only when the project contains at least 2 hardware outputs, and one bus feeds another via Sends.

I confirm that this does not happens in Cakewalk (2024.12 build 125, 64 bit)

This is my post in the main Sonar Forum:

 

[aleo]

I have encountered a few problems with Sonar 2025.02 and reported them to Cakewalk Support, though some of them appeared as far back as v. 2024.11. 

In February we upgraded our DAW computer to an Intel Ultra Core 7 265K, 3.88G.Hz, 32 GB RAM PC with 64 bit O.S. running Windows 11 Pro, v. 24H2.  We installed v. 2025.02, build 077 which has been running very smoothly on the new computer, but in spite of the new, clean installation the four problems with Sonar reappeared.

1.  Crazy or impossible automation envelopes appear after a MIDI clip has been moved:

     after creating an envelope in a track, draw a line linear or curved connecting the

     right-most node in the clip to a node outside the clip near its right side.  Go to clips

     and move the clip to the left, say one measure.  Go back to track automation and find

     that Sonar has created a new node on the right edge of the clip. Try to delete this node

     and an impossible envelope appears with new nodes and parallel envelopes that can’t

     be played or easily deleted.  Refer to attached screenshot below.

2.   A 10 second delay occurs whenever a project is closed containing simple instrument

      tracks of either Absynth 5 or FM 8.  Most of these are small projects with no other

      plug-ins.  If you click again on Close or File you get a “Sonar is Not Responding”

      message.  We have not encountered any delay with projects containing Massive,

      Omnisphere, Dimension Pro, or Zeta tracks.  There is no delay with projects

      containing only MIDI tracks, only audio tracks, or a mixture of MIDI and audio.

3.  The Quick Start screen appears every time we initiate Sonar even though it has been

     unchecked in Preferences and in the Quick Start screen itself.

4.  Local/Off-Line Help was not included in either v. 2024.11 or 2025.02.  To obtain

     Local Help we had to request, download, and execute a separate file supplied to us by

     Cakewalk Support.  At this point, Local Help is working in Sonar, but it should

     be an integral part of Sonar (included in the installation) just as it was in CbB.

Cakewalk Support advised uninstalling then re-installing Sonar 2025.02 and we did this three weeks ago, but again, all four problems we encountered months ago reappeared in the new installation.  Cakewalk Support has not come up with a solution to date; I don't know what more I can do on my end.

 

[msmcleod]

1 hour ago, aleo said:

1.  Crazy or impossible automation envelopes appear after a MIDI clip has been moved:

     after creating an envelope in a track, draw a line linear or curved connecting the

     right-most node in the clip to a node outside the clip near its right side.  Go to clips

     and move the clip to the left, say one measure.  Go back to track automation and find

     that Sonar has created a new node on the right edge of the clip. Try to delete this node

     and an impossible envelope appears with new nodes and parallel envelopes that can’t

     be played or easily deleted.  Refer to attached screenshot below.

I've tried to repro using the steps above but cannot.

Can you put together a video showing this happening from scratch?  I normally use screen2gif for screen video captures.

A sample project may help as well.