Sonar 2024.12 Feedback

[IgoRr]

3 minutes ago, John T said:

I'm not seeing this problem with the latest Sonar.

This is great, but unfortunately I have this problem. And not only me, in this same thread, there were other users who wrote about similar problems with the absence of text in the cursor tooltip field on the "Automations" line, and the absence of ordinal numbers in the track titles, and in another thread several people noted similar problems with the absence of text.

So, this is not an isolated phenomenon in only my computer, I think that it depends on some elements in the system, but I have already said more than once: I do not install absolutely anything "unusual" or suspicious, these are programs and elements that have been tested for decades. The issue comes down to the unwillingness of developers to mess with problems under Windows 10, and this is, in fact, forcing the transition to Windows 11, the second member of the team is already openly telling me about this.

[msmcleod]

FWIW I'm using Windows 10 still and not seeing any issues.

I've got two Windows 10 boots on this machine: one is my dev boot, which has a bunch of random stuff on it, the other is my DAW boot which is relatively clean.  Neither have any issues with text/fonts.

[Wookiee]

No issues here with Sonar on Windows 10.

[mettelus]

6 hours ago, IgoRr said:

there were other users who wrote about similar problems with the absence of text

Years ago I had a similar issue with the Staff View and one of the bakers posted the font used (for the SV note data) on the old forums. Font issues can easily arise if a person using an app doesn't have that exact font installed (Windows will choose the closest alternative it "thinks" applies; but may not fit, or even look remotely accurate in my case).

Something the bakers would need to answer specifically is exactly which font is being used in these affected fields, so users seeing that issue can check to see if they have that font present on their computer (as it may not be).

[IgoRr]

1 hour ago, mettelus said:

Something the bakers would need to answer specifically is exactly which font is being used in these affected fields, so users seeing that issue can check to see if they have that font present on their computer

Good afternoon!
Ben and I discussed these issues at length and in detail, Windows 11 uses the OpenFont font instead of the TrueFont font used in Windows 10. But these are system fonts, which, as it turned out, do not affect the specific bug in the latest versions of Sonar. There was also a suspicion that Sonar had problems with the "Beausite Classic" font in my system, we searched for this font for a long time, I sent to Ben Staton debug information, but it was not in the system at all, this version was not confirmed either.

But I have already repeated several times: on THIS SAME system, with all the SAME programs and elements, in Sonar version 29.09.0.138 (Rebuild_1) beta, the texts are displayed completely normally, I specifically installed this old version to check. That is why I see that the problem is in the latest versions of Sonar, something was changed, after which the text stopped displaying in several sections. Oh well, none of the bakers want to do anything anyway.

[pwalpwal]

1 hour ago, mettelus said:

font

really?

[Mark D.]

OK, something of a fix but not really. The latest update allows Console View to disable resizable option - No such options for the Track View. Here is the issue.
When disabled in Console view, you still have no option to make the FX box infinitely expand. So even if Track View had this change, it doesn't fix this problem.