Colin Nicholls

Oh - and we can still fire up CbB and load themes as a source of inspiration, going forward. That hasn't gone away.

Shucks Erik, thank you. It's amazing what you can achieve when you are between jobs and have people appreciating your efforts. I echo your sentiments. I've been mourning the loss of theming also, but looking forward to what is coming - cross fingers - with respect to color customization in New Sonar. However for those of you expecting a "Young Lady's Primer to Color Theming in New Sonar", please don't hold your breath waiting for it 😄

Ugh, I've never used it. Yeah that's suboptimal for me too. I don't know whether we should log bugs/feature requests for individual color tweaks or just group them all under a general "hurry up with user color customization already" thread.

https://www.cakewalk.com/sonar Download, execute, follow the instructions

@jimlynch22 Given your constraints I recommend you stick with Mercury or Mercury classic. In PRV, If you are a fan of "light background PRV" - like me - it's about your only sane choice. In Track View, you can adjust the data zoom level (as I think you have done, I think) to make the note blobs larger, and choose track colors that improve the contrast of note blob to background.

I'm not sure which module would be appropriate, or even if it was suitable for every Audio Driver type, but I feel like so many "Sonar sounds like crap" posts might be eliminated if the buffer size were obviously visible without drilling down into the preferences dialog

"Sonar" is not "Cakewalk By Bandlab", it is a different program with different user interface engine that is vector-based instead of bitmap, and is able to be variably scaled but retain "crisp" appearance. In other words, the graphics you see are not generated the same way, and there is no method to make them look any closer to the CbB appearance. With respect to the colors, try adjusting the Saturation slider in Preference > Customization > Colors From your screenshots, it appears it may need moving to the right in order to match what you see in CbB.

Check the status of the Preference > File > Advanced > [ ] Allow only one project open at a time

I'm not so sure, because I've been able to configure CbB also such that I can't record anything, 😉 Seriously though, I would start with the basics. Enable one set of inputs and one set of output only. Then create an empty project, no plugins. Add an audio track and assign output to the one output that you enabled. Drag a known good test audio file into the track and test playback. Works? Good, discard that track now. Now add a new adio track, and set the input to the one input you enabled. Arm the track for record and press Record in the transport. Are you getting data printed into the audio track? (could be a flat line (i.e. no signal) but is it recording? If so, great. Now double-check that your mic is plugged in to the right input. Does it need +48V phantom power? Re-do the test. Getting signal? (Whether you can hear the output as you record (i.e. input monitoring enabled) isn't the test you're doing right now. That's for later. Report back on your progress.

Yay!

If you have a blank project that exhibits the problem, I would try opening it on my system and seeing if the problem is saved with the project. It might not be a content-dependent problem.

Off-topic, but I love the NUC form factor. I use a NUC 12 myself. On-topic, I have not seen this behavior recently. Are you able to share the project?

Can you open the projects in Safe Mode ?

That's just, like, your opinion, man.

Also... bear with me here... what if you try to export as "test_.wav" - do you get test__.wav ? what if you attempt to export to a filename without a file extension?

I'm clutching at straws here but could there be a hidden file test.wav that is forcing the underscore? I mean, i would have expected test (2).wav or similar rather than an underscore but... ?!? I didn't see anything immediately obvious in the video, thanks for sharing that.

This has nothing to do with Sonar and a lot to do with very stupid choices

Is there any chance you guys can post a short video showing the problem? This is intriguing.

There's no chance your filename includes pesky higher-order ascii (or unicode) characters is there?

Off topic, but I challenge your premise here. MSFT's Aero Glass was tried, and retired. Orders of magnitude advances in GPU power since then aren't going to change the fact that it is a bad idea.

The "Add Track" / "choose plugin" menu shows VST2, VST3 in identical colors making it hard to discern. Also, the Browser shows them in different colours but the icon is also hard to discern. I suggest assuming either VST2 or VST3 (probably VST3) and only identifying the plugin type if it is different from the default. That would vastly improve clarity.

Huh, I never noticed that. I've gotten into the habit of dragging instruments from the Browser, where they are likewise hard to distinguish but at least they use different colors there. Both the menu and the Browser would be better served by just assuming VST2 (or VST3, take your pick) and identifying plugins that are not the default type.

Do you have a controller sending a CC or something to enable RecArm ?

Thanks for writing out those instructions. I followed them as exactly as I could, and - you guessed it - could not reproduce the issue. IN my case, I copied a random .wav file into D:\TEMP\ and used that in the filename picker dialog. I can confirm it overwrote the existing file with the new export, and didn't append an underscore. If you enter a filename that doesn't already exist on disk; export to it; then re-export picking the existing file, does the behavior still happen?

Is it adding an underscore even when you provide an override to the preset name template in the Export Audio dialog? In other words, how exactly are you doing this?