Sonar 2025.02 Feedback

[Wookiee]

2 minutes ago, IgoRr said:

Yes, I have already updated the C++ libraries several times directly from the source using the bakers' link in the Sonar discussion. I updated these sets before using DaVinci for the first time (I have a portable version), and after using it, after installing Adobe Acrobat, after reinstalling Sonar, etc., I am sure that this can be excluded from the reasons. And regarding sending the project file - I can send an empty project (template), in which I have everything exactly the same as on the GIF, does this make sense?

Sending an empty template is meaningless, whilst it may contain some information the additional data from recordings may, help. It is your choice, I am just trying to get you some help, if you don't want to follow my suggestions that is your decision. 

[IgoRr]

5 minutes ago, Wookiee said:

I am just trying to get you some help

I am grateful to you for your help, but I already said - in any (!) project, the same thing happens to me - the buttons in ProChannel are not displayed as enabled, it does not depend on the number of tracks, or the number of instruments or processing. I can send any project, but I just thought - if everything is exactly the same in an empty project, is it easier to send an empty one? That's why I asked you - does it make sense?

[David Baay]

@p-w-m, @Neil Scott, @Aaron Doss and others experiencing UI reponse/lagging issues. I'm wondering if this might be fallout from the experimental 'Enabe GPU Acceleration' option in Preference s> Customization Display.

I suggest you try disabling it.

Edited 3 hours ago by David Baay

[IgoRr]

5 minutes ago, David Baay said:

I suggest you try disabling it.

I've never had such bugs, but there are a couple of unexplained bugs with the absence of text (name of modules) in the menu for adding modules in ProChannel, and in the pop-up hint field near the cursor on the "automatisms" line, I already wrote about these bugs here. But all the other functionality in Sonar/Cakewalk works completely normally and reliably, and in the latest build, this strange thing appeared. I checked the setting you specified - I had this option disabled, I tried to enable it, checked - the same thing, then disabled it again - nothing changed again.
Do I understand correctly that most users do not have this (as in my GIF) in the latest version of Sonar?

[David Baay]

7 minutes ago, IgoRr said:

Do I understand correctly that most users do not have this (as in my GIF) in the latest version of Sonar?

Prochannel buttons show up enabled in the Console View as expected here.

[IgoRr]

2 minutes ago, David Baay said:

Prochannel buttons show up enabled in the Console View

Then it's really strange... I could assume that the reason for such anomalies could be that I don't have a discrete graphics card, but in the previous version of Sonar, this didn't happen, although absolutely everything remained the same - the system, monitor settings, drivers, plugins, etc. I am becoming increasingly convinced that the new iteration of Sonar is extremely sensitive to any (!) system elements, drivers, and third-party programs installed in the system, which seems very counterproductive to me. Or I can only think that this all happens because of working in Windows 10, and most have already switched to Windows 11, where such anomalies do not occur, no other logical conclusions can be drawn.

[David Baay]

1 hour ago, IgoRr said:

I could assume that the reason for such anomalies could be that I don't have a discrete graphics card

Not sure what you have going on, but everything's good here on both my Win 11 laptop with onboard Intel graphics and my Win10 desktop with Nvidia. Are you sure it's not project-specific and maybe plugin-related?

[IgoRr]

23 minutes ago, David Baay said:

Are you sure it's not project-specific and maybe plugin-related?

I don't know how else to explain that in a completely empty clean project without a single plugin or instrument, when opening the mixer, the "ON" buttons on ProChannel are not displayed as enabled. I specifically created an empty clean project without any instruments or plugins in the "VSTi" rack, in which the same thing happens. This is the same for a project with a single MIDI track, with 10 MIDI tracks, with 1 or 10 audio tracks, and with combined MIDI and audio tracks. The same thing happens in all other projects, and when activating the "FX" and "PDC" buttons, which completely excludes a software or hardware connection for this phenomenon.
I'll just repeat once again: in the previous version of Sonar, under the same conditions, with the same system elements, programs, drivers and everything else, the buttons on ProChannel were displayed completely normally.