Steve Moddelmog

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?

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.

Very frustrating that while the .cwp file clearly must have the name of the plugin (otherwise you'd have to manually load the desired plugin every time you re-opened a project), that information is not store in plain text. I have many, many old files from the days of dxi that I'd like to resuscitate and work on where the plugin now has a modern VST (Native Instruments plugins, for example), but I didn't do track notes back then and I'd never be able to figure out what plugin to load. If that information could be extracted from the file, I could replace, say, the dxi of FM8 with the most recent VST and then load the preset I originally used. Ditto for old versions of VSTs (say Absynth 4) with newer versions (Absynth 5) and load the preset whose name I found poking into the .cwp file. Yet the developers must know how to get that information - would really be great to see a tool created to do so. THAT would entice me to buy a subscription to the new Sonar.

I did the three-day trial of Sonar and learned the following: 1. A lot of my non-scalable VSTs are now so tiny in nuSonar that I can't use them. For example, Native Instruments synths except for Kontakt. 2. Due to eyesight issues, I need a theme where PRV has white keys / black keys and a white grid with dark gridlines. I could accomplish this with Theme Editor in CBB, but as of now there doesn't seem to be a theme editor for nuSonar. 3. Small thing but I've found it very helpful in CBB lately: in CBB, if you hover over the bar graph in the Performance Module, you get real time info on Audio Processing, Engine Load, and number of Late Buffers. This feature is missing in nuSonar. The only real advantage I found in nuSonar was the crispness of the text and graphics. Has anyone found anything else that is a super useful improvement?

Nothing free expected, but the payment model is not what is wanted. I have yet to see a user on these forums or in any CW social media groups say they were hoping for a subscription model.

SPLAT would be ok. A few CBB features I would miss, but nothing earth-shattering. If the ability to activate with Command Center ceased to exist, I have X3. I've used it a bit, and I do think that would be a step backwards and possibly a reason to look for a new DAW. But it would be usable in a pinch, and the advantage is it would open the hundreds of Cakewalk projects I have.