Steve Moddelmog

How do you set up CbB to make TTS-1 the default player for a MIDI file? I was unaware of this capability.

I'd never noticed it, but it seems like I do get a little bit of the effect you're talking about. I had changed the "High DPI scaling override" in Properties / Compatibility. When I uncheck that box, I don't notice any flicker.

Thanks!

Yes, the August version of Sonar. I have pm'ed the file to you. One thing I noticed that I didn't mention in my message - it has a tab at the bottom next to Console and Piano Roll that says "Loop Construction <Melodyne> Track 1." I don't remember what that was about - I don't recall ever using "loop construction" and I don't think I've ever seen that tab before in any project. Unfortunately this one was started seven years ago and I don't remember what I might have been doing that created that tab. Possibly changing the tempo? But closing the tab in CbB does cause it to crash, even if I first render the Melodyne clips. Thanks for taking a look.

I agree. The clips were so small I didn't notice them, and they are 7 years old...

Problem solved, though I don't understand it. I tried loading the project in Sonar in safe mode. The last thing it asked was about loading Melodyne. I said no and it loaded fine. So I went back to it in CbB, discovered there were two very short clips with unrendered Melodyne edits, rendered them, and saved. Now it loads in Sonar. What's strange is (a) it wasn't a problem for CbB, and (b) even stranger, it loaded fine initially in Sonar when I made a few edits this morning (nothing to do with Melodyne or the track that had the unrendered clips) and gave me no error or strange behavior when I saved it. Only when I tried to open it again...

Done, except for the dmp file

Title is pretty descriptive. I have a project that I've worked on off and on since 2017. I made some edits in "new" Sonar this morning and it played just fine. I was done with my session, so I saved it, closed Sonar, and went about my business. When I tried to open it a few hours later, I can see Kontakt starting to load samples and then Sonar shuts down with no warning. I have rebooted and still same situation. So I tried to open it in CbB and it opens and plays just fine. Cannot figure out how CbB is ok with it and Sonar, which the final edits were made in, is not ok. Screenshot below. Plugins are : DR-008 VC-64 BlueVerb DRV-2080 Kontakt 5 NI Replika Ultra Analog VA2 (VST 3) Ozone 6 The project has three audio tracks, and Sonar and CbB are both set to find Audio in the same location. Any thoughts, besides just using CbB instead of Sonar

Solved my problem I have a default workspace (that I created in CbB several years ago) that loads when I start Sonar. I did my little toggle of tooltips, saved the workspace, and now tooltips are active when I star Sonar. I'm surprised by this, because 1. That same workspace also loads when I start CbB, and tooltips are always enabled, and 2. I have made other changes to Sonar in Preferences / Customization / Display (for example, I've turned off DPI awareness), and they've "stuck" without saving that workspace. Wonder why tooltips is different in that regard. Anyway, thanks for all the suggestions!

I looked there after uninstalling and didn't see it. Only CbB and Cakewalk Next products. But just now it offered an update to CPC, and now there is a section for Sonar.

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?

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...