Steve Moddelmog

Thanks. Yeah, none of those are read-only. I guess is use use Revo to do a deep uninstall and then re-install Sonar. Not sure why, but my intuition is that won't fix it. I guess because I didn't do anything "non-standard" in the original installation, and this has been an issue since the first day I installed Sonar. As I said above, I did reach out to Support and got a response but no suggestions - just noted it as a potential bug. I wish that someone technical at Cakewalk who understands what files are involved in making Tooltips work would chime in here.

Where is the prefs file that would pertain to this? None of the *.ini files are read-only. (I did see a registry entry.) Also, if I make other changes in Preferences / Configuration / Display, they are saved and are reflected the next time I open Sonar - only Tooltips are not (and even so, the box is checked, they just don't work until unchecking and then checking again).

Yes, I enable tooltips every time and they work for that session but then don't when I start Sonar again even though Preferences / Customization / Display shows tooltips as being enabled. So I must uncheck "show tooltips," click "apply," then recheck "show tooltips." I tried the suggestion of uninstalling and then reinstalling Sonar, but no luck. It didn't try to download any C++ files. But I resinstalled from my original installer - I cannot for the life of me find where to download Sonar now. Hugely frustrating. Even Google Gemini just directs you to the CbB download page, even if you are very specific about including "Sonar" in the name of the product you are looking for. Cakewalk really doesn't seem very interested in making it available. So for now I am going back to CbB. Too many things not working for me in Sonar. I was just buying month-to-month but jumped on a recent annual discount, which I now very much regret.

Sure. For example, if you hover the mouse over the graph in the Toolbar Performance Module, you should see real time info on "Audio Processing," "Engine Load," and "Late Buffers." Actually hovering over any icon in the toolbar should display a brief explanation of the icon's function. Thanks for checking.

Yes, back in July. I got a response on July 21 saying they would "note this issue," though they didn't specifically acknowledge there actually was an issue.

Not a single reply - I guess that means tooltips are working fine for everyone except me?

I am mostly using CbB because I find PRV difficult with the existing themes. None of them have enough contrast between white keys and black keys. There's probably a reason why those keys are white and black on an actual piano!

Every time I start Sonar, if I look in Preferences / Display I can see that Tooltips are enabled. However, they don't work, and I have to toggle off then on to get them working for that session. I exit Sonar with them enabled, start Sonar again, and have to go through the same thing all over again. Never have any problems like this in CbB. Is anyone else experiencing this?

Ah, I see. So the fact that it was correct for the keys and notes I selected was purely accidental😉

I just did it with Project/Insert Meter/Key change. I changed the key to D major and black keys show as #. The next measure I changed it to B flat and I got a flat symbol (sorry, not sure how to type that online - I know how to do it in Word) on black keys. And if I go back the the previous measure that was in D major, they still show as #.

I now see that there is another arrow to drag once I do the first drag - not visible until I have created a big gray window. However, I can only drag that second window to be a maximim of 7" x 4 3/4", resulting in a 4 pt. or 5 pt. font size (measured by creating a 4 pt. font and a 5 pt. font in Microsoft Word for comparison). Better, but not exactly usable.

When I drag the lower right corner of Ozone 11, the window gets larger but the actual GUI does not - just a bunch of gray space is created by dragging. I do see what you're saying now about Massive X. It is otherwise so small I had to know what I was looking for and where. Thanks.

I'm finding that doesn't work with some plugins - for example Native Instruments plugins that don't have standalone versions such as Massive X and Izotope 11. You can get a big windows by doing it, but the actual size of the plugin GUI is unchanged and doesn't fill the window.

I'm trying out Sonar. A lot of plugins appear very tiny on the screen - for example Native Instruments synths except Kontakt. Someone kindly pointed out that I could uncheck "Enable Plugin DPI Awareness" to get back to a usable window size. However, this doesn't seem to work for plugins that don't have standalone versions - specifically Massive X and Izotope 11. I don't use Massive X much, so no big deal, but I use Izotope on every project. The plugin window for it is about 4 3/4" x 2 3/4". If I uncheck "Enable Plugin DPI Awareness" the window is much larger but the plugin still only occupies 4 3/4" by 2 3/4" of the window. Any suggestions would be most welcome!

Well, the way you have to handle it in Arturia is to use each synth's scaling options. Still a pain...

Yipes - I'm going to have to do that for all my Arturia VSTs - something like 40 synths.

Well, I am an idiot. I unchecked the DPI box on the VST2 instead of the VST3. All is good. Thanks.

Yes, the VST3. Version 1.4.6

Nope, they are all stubbornly the exact same tiny size with or without the box checked.

OK, that worked.

Stranger still - I unchecked the box for AAS Tassman 4.1 and it fixed the scaling for it. But it doesn't work for any Native Instruments synths. I've tried Reaktor, Massive X, etc.

3840 x 2160, 250%

The setting "stuck" the last time I unchecked it, but it (FM8) is still tiny in Sonar/

1. I disabled "Plugin DPI Awareness' for FM8, rescanned everything, and it was still tiny. I tried closing and re-opening Sonar and the "Plugin DPI Awareness" bon for FM8 was checked again. 2. Yes, in Mercury Classic I'm referring to the shading of the sharps. I'm using Tungsten Classic and it's much worse since both all the grid is very dar. 3. I cannot put the cursor anywhere in the performance module that brings up the real-time information.