Colin Nicholls

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.

I can reproduce this on my system using @Promidi's sample project. Note that the project opens with both the Drum Pane and the Note Pane open, and I can observe the controller pane auto-shrink only after expanding the Controller pane to fully obscure the Note Pane. Good one!

No, it doesn't work that way. Why do you care? Are you that pushed for disk space ? If so, my guess is that you have other problems, but following the advice given by @sjoens will address that space issue.

I remember seeing this bug earlier also - both clicking on the note or changing the zoom level of the PRV would shrink the velocity pane until it eventually disappeared. However, I can not duplicate your experience in this latest version. (2024.12) Do you still see the problem when the note pane is also open? (Previously this would only happen if the note pane was completely closed).

Sorry to break it to you but that is just not how things work. Swtich to the free Cakewalk By Bandlab and use that for a while. It's light-years ahead of SONAR Platinum. And it's Free.

I've done this for certain selected CDs, and even written about the process. I've had mixed results to be honest.

If you've performed your own comparisons between Sonar and CbB, on two different machines (with the same hardware config settings for each app of course), then you have the best data you could possibly get for your situation. My experience differs: Sonar is equally as performant as CbB, if not "better". I use quotes because it is a subjective take. It requires a lot of effort to obtain hard data for definitive comparisons and honestly, I've never felt the need to put that effort in. I'm not even sure I'd be able to. I'm not doubting your experience, but be prepared to have answers to questions like "how are you measuring CPU use" etc.

Time to bump this. Obviously I'm not a fan of the default colors in the palette, and the ability to customize it would be awesome. I don't need multiple presets; I would just like to be able to modify the existing one.

Off-topic, @Astraios, but damn your color choices make Sonar look pretty good. Also, is that the Classic Royale Windows theme?

I have one of those - i9-12900K - and it is plenty enough machine for anything I can throw at it. I don't think you''ll be disappointed.

Windows User Interface Guidelines has entered the chat

It's not a mystery. I've written about this. Reading this thread makes me wonder if an update for that article is in order. I realize it kind of proves your point, in that the goal of the article is to say, "Yes, Drum Maps are a little tricky, and here's why", and it is not intended to be "here's how to use a Drum Map effectively with the smallest headache possible". So perhaps it is a separate article. Things get even worse when you've customized AD2's keyboard mapping to your own personal key/drum controller preferences, and you need to build your own drum map and not just pull one off the Internet...

The only tempo possible is synchronized to your heart beat, I would have thought. Ok, sorry! I'll stop

We totally need an ignition key graphic on that feature. Never realized I needed it, but now... I want it.

Try the "Feedback Loop" forum; might get more traction there

Put me down on the side of liking the new UI.

Never mind. As you were

So you're only experiencing this problem with one specific project?