Jonathan Sasor

This has already been fixed internally and will be in the next CbB update, apologies for the inconvenience!

As far as recent changes go, we made an installer fix related to a Waves component that was causing a component to throw an error when updating Cakewalk, however the core issue with the Waves shell crashing for some users is with the Waves shell itself. They've been working on a fix for this on their end, so hopefully it will be in their next update.

okay, so for this particular file, you're in the "something is blocking this file from being able to register" scenario. This is distinct from the main issue originally in this thread that was a missing dependency from an updated Visual Studio redistributable package. That was resolved in the updated installer. If you see this error for items in the Shared Plugins folder, you should be able to skip that and the rest of the main Cakewalk install will be fine (and if you're updating those files are already registered). The issues with the sndfile.dll and cwauto130.dll are more integral parts of the app. Your issue is likely either an antivirus program or pending Windows update that's preventing the file from being able to successfully register here. Try forcing Windows to finish any updates and/or temporarily disable your antivirus while running the installer and it should ultimately go through. Alternately you could try reinstalling the included redists manually, but I wouldn't expect this to be the necessary case. Something else currently running in Windows is much more likely to be the issue. If there has been an issue with the redists since the last full Cakewalk install, they can be manually downloaded from Microsoft here: VS2019: https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0 VS2013: https://www.microsoft.com/en-us/download/details.aspx?id=40784 VS2010SP1: https://www.microsoft.com/en-us/download/details.aspx?id=13523 VS2005: https://www.microsoft.com/en-us/download/details.aspx?id=26347

Which installer are you trying to run and from where? The current version of the installer should read "Cakewalk_by_BandLab_Update_Setup_27.01.0.098_r3.exe" and should update any valid install from 2020.11 through 2021.01. If you're seeing r1 or r2 for the update setup, please try downloading the installer again from either the Check for Updates option or BandLab Assistant.

I just sanity checked this, but the installer definitely warns about Windows 7 every time, regardless of if it's a new install or running the update from Cakewalk or BandLab Assistant. This dialog box appears:

@Craig Reeves Just taking a look through your videos, and I think there's some workflow steps missing when trying to use AudioSnap. When you demonstrate turning it on, you've already got AudioSnap set to "Clip Follows Project" in the palette which is not an option that's turned on by default. While AudioSnap isn't perfect, you should be able to accomplish what you're trying to do if you follow the right workflow steps (I did this for a project I was working on the other day). You need to make sure that you have the proper average tempo per clips set, then the Clip Follows project option set to Auto-Stretch. If you're having trouble beyond that, I'd need to see your project file to see how it's handling your material specifically, but the core essence of the stretching should work. As shown in your video, I think there's other settings that need to be adjusted. Groove Clip stretching is actually the oldest and least accurate sounding algorithm.

At the moment there's a known issue with routing with patch point/aux tracks in Track Templates. We'll look into a fix for this as time/resources allow. Thanks!

Looks like you might have something a little haywire with your existing Microsoft Visual C++ redistributables. If you go to Add/Remove Programs in Windows, try uninstalling any 2015, 2017, and 2019 entries that you currently see, then restart your system and try the Cakewalk installer again.

We've reached out to AAS for some test versions, and in some initial testing, I was able to get some instability when working with Chromaphone, but not consistently. From what I could tell it appeared to be an issue on the plug-in end rather than on CbB. Based on @ChristopherM's description of the app disappearing, that would also lean in that direction. We'll do some more digging as time allows and also pass our findings to AAS. If you're able to get any additional details or dump files related to the crash, please let us know and we'll take a look.

Once again, thanks to all for their participation. Please now submit any further feedback to the formal 2021.01 release thread. Update 1 build is 27.01.0.098. Thanks!

You might have the "display muted takes in parent track" option disabled. Clip is not actually being deleted, but it's not visible.

Something external is accessing the file. Running the install right after reboot generally should clear it, but if you ran the previous 2021.01 update before, you should be fine if you just skip that file as it's already installed/registered and has not changed. As for the original problem, it sounds like there might be an issue with the project file itself rather than the install. Are you able to create new project files? Likewise if you want to send us a project file I can see if it can open on our end.

2021.01 has now been made public! Thanks for your participation and please refer any additional feedback to the official release thread:

So the fix for your original issue had nothing to do with the bit depth of the file. There was some unusual information encoded into it by the app that created the file that our code was not handling correctly. This was fixed in the Early Access build. If you have other files that are not behaving as expected, please send us other examples to test. At the moment, I just was checking through RX2 and Wave file loops that previously had shipped with SONAR Platinum/expansion packs, and these all work as expected, so if there's another corner case with the files you happen to be working with, we'd need to verify that on our end. Thanks! The Preview at Host option is a project-specific setting. It's off by default in the "Basic" template, but if you save a project with it on, it will persist.

Can you provide a dump file?

This dump file is similar to ones others have sent, it's the Waves shell crashing. You'll need to send this to Waves as unfortunately there's nothing on our end we can do.

Hi Kurt, I'm having trouble being able to reproduce your issue as described. Can you provide a project and/or more specific details as to how you're able to get into that state? At present I'm automating plugins/track parameters and clip gain and the automation is all responding correctly.

Not really. We'd like to make more of the plugins available at some point in one way or another, but exactly how that'll happen remains to be seen.

Yes, BandLab owns all the intellectual property that was under Cakewalk, Inc. We have all the source code for all of the previous plugins, and maintain the authorization back end.

The plugins run additional delay. It's fairly common depending on the plugin. They require extra time to do their processing, so in this case that latency is giving the plugin time to fix those clicks before you hear it. You can either freeze those tracks to record, or temporarily disable them to get around it.

You're in the Basic Workspace, this hides the Navigator pane. If you change that back to "None" you'll have access to it again.

Yeah, I'd wager there's a plugin that's not happy based on the video. As mentioned, opening CbB first, then holding shift when opening the project will open via Safe Mode and you can opt for "No to All" for plugins and see if it loads.

Some people are seeing the crash on load issue(s), but we haven't seen that problem on our end. From what we've seen in the dumps, the crashes are within the Waves shell. We've forwarded some of those dumps to Waves ourselves and encourage others to send them directly too.

If you had SONAR Artist/Prof/Platinum, Session Drummer's x64 version installs with the Artist Instrument Collection. That installer can be run independently after installing CbB as well since it won't change any updated shared components.

We have Waves V12 in house, and I use them every day. That said, we've seen some users experiencing crashes on load, and have sent some customer dump files to Waves ourselves. You definitely should try and follow up with them if you're experiencing problems.