Shayne White

SoundCloud used to allow 96KHz uploads, which is what I prefer. Is that not possible anymore? 44.1KHz is an obsolete format in my opinion.

I feel that Skylight already got an "update" and that was Tungsten. That was the move to a modern, flat, dark interface. It took a little getting used to but I decided I liked it better than Mercury and that's what I use now. Please don't change anything, it's perfect. Sometimes in the past Cakewalk went backwards with their interfaces -- for example, going from Sonar 3's beautiful blue scheme to Sonar 4 and 5's gray was int he wrong direction; thankfully, the colors could be fixed easily. But then Sonar 6-8 was so horribly ugly I boycotted upgrading until Cakewalk gave me a special deal for 8.5 ahead of the X1 release, which was when Cakewalk finally got it right again.

VST2 and VST3 plugins install differently. VST2 installers let you choose where to place your plugins; I simply have all my mine in C:\VST. You have to manually tell Cakewalk where to look for VST2 plugins you install via the Plugin Manager. VST3, on the other hand, is automatic -- all VST3 plugins will install into C:\Program Files\Common Files\VST3 no matter what. Again I'd recommend going into the Plugin Manager (it's in the Utilities Menu I think?) to make sure Cakewalk is searching in that folder.

I've never had Sonar/Cakewalk crash with sidechaining. I've only done it with Sonitus plugins (DirectX) and VST3 though. Maybe the problem is with VST2 plugins as Noel mentioned?

As I recall, you need to run Cakewalk with admin privileges for Pentagon not to crash. I'm not sure about the others, but it could be the case as well.

There's a dropdown menu right above the track list that allows you to pick what mix options are displayed. Make sure it's set to "All" or "Mix." I always leave it on All.

Having ThreadSchedulingModel set to 2 may "look" nicer on the CPU meter but I've found it actually makes audio performance worse. I have a quad-core (8 with hyper threading) laptop and the 0 setting works the best. Of course, there could be other issues that could be causing audio clicks/dropouts. For instance, on my computer (it's actually a 2016 MacBook Pro running Boot Camp ha ha) I have to disable the ACPI battery driver (that monitors the battery level), the Wi-fi adapter, and the onboard sound to get glitch-free audio performance. The battery driver is the worst culprit. You'll want to download the LatencyMon program (do a Google search) and run it to see if other drivers are interfering with your computer's audio performance.

Looks like the workaround is to save the track in a project "template" and then copy and paste the MIDI track into a new project as needed. After that, I only have to set up the remote control settings. It'd still be nicer to use actual track templates!

I'm trying to set up MIDI track templates so that I can control hardware or VST synths via an external MIDI controller. When I automate them, I typically use MIDI automation lanes that output NRPNs. I then set up remote control settings on each automation lane that respond to my external controller's CCs. But when I save a MIDI track set up this way as a template, none of the automation carries over to the new track template. I can't even set up a volume curve going over CC7 and have it save to a track template. That's kind of ridiculous! Hopefully this will get fixed in a future update?

I’ve had similar issues with BandLab Assist either not updating or not displaying anything other than a vertical white screen. Re-downloading from the web site seemed to fix it. I’m very grateful for BandLab for keeping Cakewalk alive and bringing us the forums (look great by the way!), but unfortunately Bandlab Assist is very poorly designed compared to the old Cakewalk Command Center. I hope they migrate that over soon. ?