kday

Appreciate the help!

Hey thank You, buddy! That worked just what i needed. Appreciate all your help you're the greatest!

It still displays the other Notifications like Melodyne

I don't use Melodyne and i don't want to keep being reminded of Melodyne Updates every time I load up the program. Is there any way to to cut off the Melodyne update message so I don't have to be reminded of this update, or any updates when I start up the Bandlab program? Thanks

Thanks, I did that and that worked. But I want to try the ripple effect option to see if that works too. But I forgot where the ripple effect is, how do I get to that? One other thing that worked was the Creat Region FX option that allowed individual editing of tracks.

Thanks, but where is the ripple edit button? How do I get to it?

I'm trying to move or copy just one single Track in a song, but it keeps selecting multiple tracks instead and moves them all at once. It's sorta stuck on select ALL. Am I doing something wrong here? Thanks

Yeah, Windows 11 was a total failure regarding the Explorer Menu. It's like how can a company be so dumb as to totally destroy decades of Explorer progress to only destroy it all overnight in a backwards move? I think the biggest mistake Windows ever made. Fortunately there is a fix that restores the Windows 10 menu and functions and options to Windows 11 that anybody can get and patch. That's what I did otherwise I wouldn't have been able to use Win 11 because the Explorer became too primitive and difficult to use as it was.

This is most often caused by some VST recently installed that conflicts with Cakewalk DAW. There are two ways I usually fixed that problem. 1. Uninstall the last few VST installed which is the conflicting Cakewalk program. 2. Uninstall Cakewalk program and reinstall the program sometimes untangle the conflicting VST or drivers. In either one of these procedures fixed my almost done hangup 100% of the time. If the program was working, and then stop loading correctly, means a VST program is conflicting. Sometimes you have to uninstall two, three five programs to get to the root cause.

Finally problem solved. So what happen was I installed a new VST that distributed it's own Microsoft runtime libraries into my computer, and i installed this program in both desktop and laptop so i got the exact same corruption on both computers. I let this vst program install it's own Microsoft runtime libraries. And that corrupted my WIn11 OS in both my computers, or either the newly corrupted Cakewalk template from the vst i copied to the laptop may have did it. Either way the corruption carried over to both PCs. Neither would load Cakewalk program template anymore. So I thought since the corruption happened on both computers only using Cakewalk software it must be related to possibly the beta builds. I copied the original OS SSD to another SSD when I tried to reinstall a fresh copy of Cakewalk and still got the same problems so i thought it was related to a build. I found the only thing that worked was a [reset my pc] option in Win11 that added all the missing Microsoft redistributables files that the EXE program couldn't, probably because the corruption was deeply embedded in the OS. and even copying a new OS installed on another SSD couldn't fix. I needed to start from a new OS from scratch. Once i did that the program started back working again. Thanks to everybody who helped with advice here, i tried everything from all of the advice to what I finally discovered in the [reset my pc] option..

When I try to load a Pro-Channel module on a new install I get [ VST Plug-In Error ] The Following Plug-In failed to load: message. What is causing this Pro-Channel error? This error message just started happening and even from a fresh install I still get the VST Plug-In failed error message and won't load a pro-Channel module. Looks like there is some Pro-Channel corruption somewhere. Or maybe the Pro-Channel files aren't being loaded, but a fresh install is rendering the exact same pro-channel error results. I Don't know if my OS has been corrupted or what the problem could be here. Anyone ever experienced this problem before? Corruption could've came in from using a Cakewalk template from another computer, I don't know. But reloading a fresh version of the Cakewalk program seems to get this same corruption error message. Thanks

I installed the last regular version. I think my Cakewalk installation process may be corrupted from loading and unloading some VSTs maybe and possibly corrupted my Cakewalk Pro channel, or maybe the Pro Channel is corrupted so I'm trying to start from scratch with fresh builds and adding pro channels modules to see which one corrupts the Pro Channel rack.

Some I really like and been using for a long time. I think I might be able to pinpoint exactly what's the problem after rebuilding new templates from scratch to identify which pro channel or what may be doing the corruption. I'm getting VST Plug-In failed to load message when trying to load a Pro Channel altogether now. It won't load at all.

Yes, when I load some pro channel modules in multiple channels they default to On position. Like if i load reverb across a few channels and default them all to the off position, and leave the track and then come back one of them the Reverb is back on again. So I'm gonna try cutting off Write Automation to see if that help. But i already sorta fixed it a little bit by building a new template and not adding anything extra and it's not cutting on any extra Pro Channel modules yet. If I try to add some Pro Channel modules it may start to doing that again so I'm adding pro Channel modules and saving each build to pin point what Pro Channel module is doing the error. Now I'm getting VST Plugin-In Error VST Plugin-In failed to load. That may have something to do with the Pro Channel corruption. Thanks for all you help and I'm trying to add more channels until I get the bug to identify where it's coming from.

I give up on this Cakewalk Bandlab, it's shot. It's like Cakewalk with a broken arm, or Cakewalk without a professional Pro Channel because many are defective. I just hope this bug doesn't carry over to their new version since they may never know this issue exist.