shane

Correct, no lock next to screenset. Here is how it defaults before I minimize all tracks:

Hmmm (thanks all!) F/Ctrl F: this simply (maximizes but still fits all content on screen. It doesn't go backwards/opposite or "minimize all tracks"? Screenset: nope, don't even know what that is. I found it (upper right) and toggled away from #1 and then back; it went back to about 1.5x track height? The only thing I have found to minimize all is clicking the middle of the right hand zoom and dragging up, but this moves the entire song up and out of sight for some reason.

YES! I am using 150% Zoom in Windows. While toggling between 150% and 100% doesn't change the track height, it does of course shrink the whole Sonar size. It doesn't seem to impact the track height on restarting Sonar though.

...instead, it always makes Tracks about 2x their normal width/size. Super painful to go to each track and Zoom out fully. Previously, Track zoom seemed to be preserved, or at least they were always zoomed fully out.

Still using trial mode for eval, but noted the new 2024.9 update will not show graphics/visualizations for any of the ADDED Pro Channel plugins like the LA-2A, Concrete Limiter, etc.? These visualized/worked fine before the update.

Update after a few weeks of VST2 vs. VST3: Seems like VST3 versions are ok AS LONG AS YOU DON'T AUTOMATE PARAMETERS. With this automation, dropouts and Late Buffers are constant. Freezing the audio cures the issue(s)

Daily Sonar user here.... This (still) happens to me about 4 times a week, and I always thought it was one of my hardware drivers; either the MIDISPORT 8x8 (likely) or RME Fireface UFX (less likely, but not impossible) or something along that hardware chain-- could be a Firewire driver or USB driver is the culprit. Frustrating because it just quits, and I CTRL-ALT-DEL and can't force quit in task manager. The FASTEST solution has always been to reboot.

Not a plugin per se, but DONT FORGET you can transpose audio right in Cakewalk. You just have to select "transpose audio" in the drop down. Surprisingly good results, depending on your audio source.

Wow. I'll roll back to VST2 and see how it helps. Just wish they would address us Cakewalk users... seems they did, then set us to "ignore for now"

Anyone get anywhere with SoundToys on this? I heard from Support a couple times, but it wasn't very helpful. These ST plugins are grinding this project to a halt.

I've been emailing with ST support for a few days reporting this; Little Alter Boy is giving me CPU spiking and "late buffers" (which continually increase. I assume Little Microshift is the same. Important note: I am NOT using these on live inputs, they are inserted as regular plugins. Previously, the beta cured similar dropouts, whereas in about the last month they have returned. This was around the time of the new Cakewalk 2023.09 (build 062)

I believe it overwrites it, but figured I'd ask here. Also; I think re-installing the previous version is good enough, but again wanted to ask.

I can't believe I don't know this: what is the proper way to uninstall the latest beta Cakewalk and revert to the previous version? Is it just to re-install the previous version?

Downgraded to build 55 and the problem persists. It's now CPU spiking on projects that previously werent. Anyone else having this issue?

Here is a link to the full download: link removed by admin