Colin Nicholls

Man, that is frustrating! I can see why you'd want to let of some steam; I'd do the same. Probably I'd use more swear words. But here's the thing: Many, many people with many, many different configurations are not experiencing this. For them, Sonar is working fine and in fact, better than CbB ever did. It HAS to be something about your hardware, or your software configuration. Installed any new plugins lately? Any other applications? Trying out other DAWs? What if you create a new empty project in Sonar. No plugs, just raw audio. How does cut-n-paste behave? Add another track or two. Then add virtual instruments. At what point does the problem start to appear? What are your hardware specs? What Audio interface? Driver model? buffer size? Take your project in the video, and save it somewhere else, and start pulling it apart until you isolate the problem. Does the crash happen when you disable the audio engine? What if you change audio from your current I/O interface to, say, Windows internal sound card (if possible). Change driver types. Have you run generic hardware tests on your machine? RAM test? could be a damaged memory chip. All this testing is a pain in the butt, I know. Maybe it would be easier to convert all your projects to a different DAW. God knows it's tempting, I've been there.

It depends where you're coming from. But here's a good place to start learning about what is new:

Not to refute your basic point, which is that contrast between clips and background in the Track View is clearly a pain point and could be improved, but I would encourage more honey, less vinegar.

Jeez you guys are harsh. Having worked in UI I know that there's no pleasing everyone, but cut them some slack. Overall the UI has been steadily improving, and any glitches are soon dealt with. It is OBVIOUS that they care about usability and no-one decided light-grey on white was by design. Report the issues as you see them, I'm sure they will get resolved. Also, it's a small development team and any effort put towards a theme editor to please the <10 people who actually care is not good use of resources. I'd prefer they concentrate on their core features, and I'm one of the <10 people.

Confirmed, I see this in Mercury theme only. Mercury Classic has black buttons with White text/icon and still looks a little strange, but very functional. I'm sure the UX Bakers will be all over this in the next release/patch. I'm a Light Theme user myself and it is much improved in 2025.05, in my opinion.

Very cool!

Honestly wondering why we don't have a sticky about ASIO4ALL at this point

Does this happen with a brand new empty project, just recording audio (no plugins) ? I would put money on this problem not being related to the latest update, but some other factor. Yes, it sucks not being able to roll back to a previous version; doing so would be a very handy way of eliminating the new update as the source, which would save us all a lot of time So many things might be the issue. When was the last Windows Update ? Are there any new Services running that you might not have noticed? Have you updated your graphics driver? Are you able to roll back to a more generic video driver and see if there is a change in Sonar behavior? Try changing your I/O buffer setttings , just to see if this affects the symptoms you're observing. Can you switch from ASIO to WDM or something like that, again , just to see if it has an effect? Check the locations on your hard drives for audio files, etc. Plenty of free space? Installed anything recently that might make a difference there? Perhaps run a health check on the drives.

Do you know what ASIO4ALL is? Read about it here. There are reasons why Cakewalk don't recommend it. Basically because there is no way to limit Sonar's use of the ASIO4ALL to only the small subset of use cases where ASIO4ALL is a reasonable choice. Sonar simply expects more from an AISO device. Like folks say, if your Audio interface doesn't have a proprietary/native ASIO driver, you will be BETTER OFF using WDM, which Sonar ALSO SUPPORTS.

For the longest time I had two MIDI interfaces connected to my DAW: My venerable USB Midisport 2x2, and sometime later my ECHO Layla PCI Audio interface added a third port, which I didn't use. My controllers (one keyboard and one drum pad) where both coming in via the midisport. I got very used to selecting the A port on the Midisport explicitly for any MIDI recording. After a while (15 years!?!) I think my eyes just filtered out the "all inputs" option; I just assumed you had to select a specific input to record to a MIDI track. Since my studio rebuild this year I now have one physical DIN input from my Quantum; and three "new" USB MIDI sources - Keylab MkII; Touche, and the Ghost Audio sliders. Suddenly that "all inputs" option makes a ton of useful sense. I decided to post this revelation in case there was one or two other sad individuals out there who shared my "feature blindness"

I've been using Cakewalk/ProAudio/Sonar since 1996 and I've never realized that I could select "All Inputs" and record simultaneously from multiple controllers. This is great! I feel such an idiot for not realizing it. I know, I know.... it's not like it's labelled "secret mysterious mode" or anything, it's literally called "all inputs". Do what you will with this information. (Context: It all started with a fairly recent acquisition of a Expressive-E Touche SE and a Ghost Note Audio slider controller. Yes I've been using different MIDI tracks to capture the data. No more!)

[never mind]

Did you mean the link to go to the Sonar 2024 overview, or should it be updated to go to the 2025 Overview ?

Prompts you to confirm each plugin at project load time, giving you the chance to skip them. Hold Shift down during project open.

Hi Lee, thanks for asking. I was not using the pro channel compressor. Way back when I started this thread, I was actually experiencing the issue in a "stitch-up" project, where I had 5 or six tracks, each with a single audio clip representing a previous project's mix down, combining them in a single exported file with careful level matching and cross-fades as each movement transitioned into the next one. The final export was 16 minutes long. It COULD, I suppose, have been plug-in related as David suggests above, but the only VSTs used were MLimiterMB and MLoudnessAnalyzer on the "master" bus. I managed to get a "clean" export by replicating the project in a different DAW. I mean, it was a simple project. I just needed a single 16 minute export to include in my Bandcamp upload 🙂 After that project, I took a long break from serious music projects (my new job gave me very little time for it). Here's the good news: I've opened that original "stitch-up" project in Sonar (complete with originally loaded plug-ins) and performed an audio export and listened through the full 16 minutes carefully, and it is completely clean. Here's the bad news: Almost everything else has changed since I originally posted the thread: New computer; new audio interface; new Sonar. So i don't know how useful it is to say "unable to reproduce" :-). But at the time I could not isolate the cause, and it drove me crazy for while.