Larry T.

Yes, that was a bit twisted of me 😇 👍 🎶 🎵 Thanks Wookiee 🎶 🎵

Thanks Bjorn. Just tried to make this one small but, hopefully, mighty 👍 🎶 🎵

I've installed all the Cakewalk Product Center updates except: Cakewalk Drum Replacer Cakewalk Session Drummer Local Help Additional Pro Channel Modules Cakewalk Core Plugins What are your opinions on these? TIA.

From what I can tell by the following data the Focusrite Scarlett Solo 3rd Generation driver is changing my Windows 11 Cakewalk Sonar Paid membership MME (32 bit) Buffer setting: This is my Buffer setting that has been fine the last few days without using the Focusrite Solo: This is my Buffer setting after using the Focusrite Solo for some recordings: This is my Buffer setting after I changed back to the MME (32 bit) Windows driver and manually reset it:

Thanks Bass Guitar. I've never checked to see if my Scarlett Solo has the software mixer but I will. I'll look to see about setting the Focusrite Asio Buffer in my Scarlett Solo. I've looked in my Windows 11 audio settings but didn't find a setting to set the sample rate....what would I set it to...I'm not very well versed in this tech area 🤔

Thanks. It's sure looking like this is a Focusrite issue.

Hi Wookiee. It may be an Arturia issue that manifests when the Focusrite Asio driver is selected? It seems the only time the Buffer setting gets changed is when I use the Focusrite Asio driver. I'll check the Buffer setting every time I open Cakewalk Sonar Paid membership and post results. Thanks

Sorry for the confusion. My bad. Lots of things I'm having to deal with lately. I'm running: Cakewalk Sonar Paid membership Version: 2025.08 (Build 035, 64 bit) Update: I downloaded the new Focusrite Scarlett Solo driver. Seems stable. No Cakewalk Sonar crashes at all. Still having issue with Buffer setting not remaining where I set it. Will run for a few days and post status. Thanks for all the help and patience 👍

Thanks David. I will do that 👍

Thanks. I'll try that. I thought maybe the Focusrite Scarlett Solo may be resetting the Cakewalk Splat paid version Buffer setting.

That will set the Buffer??

Sonar Platinum paid version, released August 2025 👍

Hi Amberwolf. Sonar Platinum premium. And....here's the latest: In the new project started and underway I added some electric guitar using the Focusrite Scarlett Solo with its own Asio driver. After recording for about an hour I closed the project and opened about a hour later. I changed to the MME 32bit driver, opened the project and no audio on the midi synth. Luckily I did my routine of loading the Wasapi Shared driver, opening the project and still no audio. Restarted the pc, opened the project, loaded the MME driver and it finally recognized it. Back to work I went. So, what could it be? Windows 11, Focusrite or Splat paid issue? TIA.

In the old CbB once I set the Buffer Latency I never had to go back and reset it again. In the paid Sonar Platinum it doesn't remember the buffer setting and, it appears that when I started Sonar Plat with a Focusrite Scarlett Solo interface already connected and the Focusrite ASIO driver selected before loading the project, it caused, immediately after opening a new project, a complete shutdown of Sonar. This repeated about three consecutive times. So, I did a few restarts and shutdowns to see if it would self correct and it somewhat did. However, when opening the new project about 3 of my midi synth tracks had no volume, about 3 did. So, I opened an old project and found the same thing. So, I reopened the new project, which didn't shutdown at this point and checked the drivers. Running Windows 11; MME (32bit) is the new default driver Sonar (or Windows??) selects as the default. So, I checked the Buffer slide setting and found it was reset to Fast (all the way to the left). I found this to be a problem before and had found a stable setting at 20.0msec (882 samples) but something changed it. So, once I set the Buffer back to 20.0msec all the problems above went away. Anyone else had this or similar? TIA.

Thanks! 🎶 🎵

Thanks Mark. Appreciate the listen and kind words 🎶🎵 The reversed sounding runs are backwards guitar (Process, Apply Effect, Reverse) like "I'm Only Sleeping ", "Are You Experienced?", etc. 🎶 🎵

Yes, I was referring to the latest, paid version of Sonar.

Thank You for that clarity. I only try to max out the certain loudest parts that require to be positioned front and center, so to speak, not every track. Cheers 🎶🎵

Hi all. Here's Choir (alt instrumental). Observations welcome. link: https://larryterrano.bandcamp.com/track/choir A bit of history and info: This track was started on the free CbB version and finished using Cakewalk Sonar paid version. A few hiccups but nothing that could not be corrected. DAW: Cakewalk Sonar paid version pc: windows 11, Ultra 9 285 @ 2.50 GHz, 64GB Dual Channel DDR5 ram, DI Bass, DI electric guitars, Mic'ed acoustic guitars, SI drums, arturia minilab mkII, arturia analog lab 5 lite reference speakers: M-Audio BX3

Yes, "get a different output level on different passes of the track at the same point in the track". I'm no audio software engineer but what you said above sounds exactly like the problem I get with plug ins that do a lot of audio modulation. The track that I've been talking about is the Juno synth on Analog Lab V. This problem occurs on the Bell Pad synth as well which also uses a lot of audio modulation. I've resolved the problem by playing the area having the inconsistent output level issue numerous times and just keep lowering the Volume Automation node until the meter no longer peaks into the red, staying in the yellow and green. I really like to max the output level to .5dB of red to get the most volume and clarity but based on your trouble shooting it would seem that with certain plug ins that is simply not possible due to the fact that modulations occur differently every time. Thanks so much for your help and advice! 🎶🎵

Thank You David. I will see about uploading a video.

Thanks so much for the replies. The problem is inconsistent stability after making a Volume adjustment up or down in the volume adjustment line. I get different readings in the fader volume level, sometimes in the red, sometimes in the yellow, sometimes not red nor yellow after making a calculated audio level adjustment based on the fader level reading. Obviously, you guys don't have this problem. I had it previously in the last few years with the free CbB version. It's intermittent, impossible to predict, rendering the tool useless at that point in time. Usually I get frustrated and try later which sometimes works. It's not a deal breaker as I can always try other ways to make the correction.

Hi man. Yes, I understand what your saying. That is how I perceive and use the Volume Automation, as the volume fader of that track. It works as I expect it to most of the time. But, I will take another look at what you posted to see if my understanding of Volume Automation is faulty. Thanks. Edit: So, you don't have this problem, then?

I'm really enjoying Sonar Platinum. But, I'm not a fan of Volume Limiting tools so I use Sonar's Volume Automation and manually set the high volume cut off points. The issue I'm having is repeatability or consistency in the audio level after I've made a level change. Sometimes the audio adjustment aligns with the audio level reading, sometimes it's off by like 2.3dB's, so I adjust but then the next audio level doesn't correlate to the change I made. This happened the last few years with the CbB version so I thought it wouldn't happen with Sonar. Is this just a normal hiccup in all DAW's or something that can be fixed by the Sonar team? TIA.