Jonathan Sasor

If the crash is caught, it should prompt you about it, but they should go to C:\Users\YOUR_USER_NAME\AppData\Roaming\cakewalk\cakewalk core\MiniDumps.

That's always how it goes. A further quick note for the exception handling, just bear in mind that you'll ultimately want to remove that once you've captured your dump because it can also catch some other things that are benign. It's very handy for when you're trying to troubleshoot a particular scenario to get more details on a problem, but you'll want to turn that off when you don't need it.

Also, if you're not getting a crash dump initially, try increasing the exception handling severity in the preferences to capture a dump to send to us. Just go to the Initialization File section and add this option/value:

Note: The installer in the original post has been updated to version 1.0.0.015. This version now allows for the install of add-ons on top of an existing up-to-date Cakewalk installation. It also runs the full installer in silent mode when updating an existing Cakewalk installation prior to the previous update.

Because for years people have asked us for a system where they were confused by inconsistent third party driver names and how they were labeled only as left, right, and stereo. The port numbers actually will show you input port 1 on your device. It's beyond our control that Roland wrote a driver that put "mic/line 1" as input 5. Obviously it's not perfect for everyone at the moment, but the amount of work required to renumber the driver ports exceeded the scope of this update. @Noel Borthwick can give you more specifics.

The VS-700 system is a bit less common in that it has those extra ports that are listed before mic/line inputs 1-8 as you mentioned. As the driver goes, they are technically starting at ports 5 and 6. I get what you're saying though, but the new system is clearer for most other devices that have the analog 1-8 inputs listed first. The other driver names or friendly names are still there though, so aside from getting acclimated to the prefixes you're not losing anything.

Likely something weird going on with your Visual Studio redists in Windows. I'd check to make sure you've got Windows updated first, and if that doesn't resolve it, try manually uninstalling the redists, and then running the Cakewalk installer (which will then replace them). I'd start with the VS2019 redistributable first if you uninstall them, but Cakewalk installs the 2019 (which includes 2015 and 2017 revisions) and then 2013 and 2010 as well.

yes, can you please upload either the .cwp or a link to the project via dropbox/google drive, etc. You can also PM Noel and/or myself with the link with the details if you don't want to attach to the public thread.

Based on what I can glean out of your dump file, it's crashing in the kernelbase after doing a bunch of stuff related to the WD Desktop App. I'm guessing that's what's likely having an issue. Also, make sure you get the latest Cakewalk build (175) as that has had some changes to the error handling that are not as aggressive as the previous release (build 144).

If the sample rate is getting flipped while you're in the app, I'm guessing something else is trying to access the driver while you're using it in Cakewalk. Make sure you're running in ASIO, check what your default audio device in Windows is and what the sample rate is set there if you're using the PreSonus for Windows playback too.

Shared should also work, you just can't manually adjust the latency. WASAPI Shared is what Windows is using for the OS, so no reason that shouldn't work for your integrated card assuming you hear anything at all from the machine.

You want MME for the audio driver on the Playback and Recording tab of the Audio category.

Setting the driver mode to MME should work for an onboard card.

Some updates just require a little more time in the oven. ?

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.

@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!

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.

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.

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.