Colin Nicholls

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?

@Matthew Carr, try disabling FX at the project level (it's the button in the Mix Module) and see if the behavior changes. If it does, then the problem is being caused by one or more FX plugins.

Are you trying to run another DAW or audio application at the same time? What happens if you reboot and just open Sonar?

Different products can co-exist, e.g. Cakewalk SONAR Platinum; Cakewalk By Bandlab, and the new Sonar. Different Tiers of new Sonar can be accessed providing you maintain two Bandlab accounts, one with an associated premium subscription, and one "normal" user. Then you can sign out/in as different Bandlab users to compare the differences between Premium and Free Tier. If you install the latest UPDATE to any of the products mentioned above, then that is the version you are able to use, short of re-installing the previous update. All the plugins installed should be available in all versions of the Cakewalk applications, as I understand it.

At the risk of going off-topic, the creators of ChatGPT and its ilk have trained their predictive text engines on a LOT of information made freely available on the Internet, including a LOT of obsolete or deprecated technologies, but that isn't a reason to bring those technologies back. Other than declaring CAL Scripts as an unsupported and unmaintained feature of Sonar, there has been no hint of it being removed. Would it make a difference if someone promised not to remove it? I think we've all been around the block enough to know that anything and everything is subject to change with no notice at all (sometimes we get a month, nice!) regardless of what anyone has been promised in the past. I don't expect CAL to suddenly become unavailable in Sonar, for what it's worth.