Jonathan Sasor

Can you elaborate on the problem? What demo projects are you looking for and where are you trying to find them? There are 2 currently shipping demo projects, "Sophia Jane - Living For Now" and "LORD - Time to Fly". The demo projects installer launched by the Cakewalk web installer places these into your existing Cakewalk Content folder, defaulting to C:\Cakewalk Content\Demo Projects If you turn off sandboxing for the plugin scan does it complete normally?

Demo projects install to C:\Cakewalk Content\Demo Projects by default, and should appear as a separate tab on the Start Page once installed. If you need to reinstall the demo projects, they're available from the Cakewalk Web Installer.

adding "ExceptionHandlingSeverity" into the Initialization File section of the Preferences lets you adjust how aggressive Cakewalk's error handling is. 1 is normal, and 7 is what you'd want to set it to if you're trying to troubleshoot something and it's not catching a dump file already.

This is a setting on the Editing tab of the Preferences: Otherwise it will duplicate the exact clip length on purpose.

If it's crashing, can you please get us a dump file? Try adjusting ExceptionHandlingSeverity in the Initialization File if you're not getting a dump now. It might be a combination of things going on in your template as well. I can't reproduce your problem with Superior Drummer 3 alone.

Can you get us a dump file for the crash?

It seems like there's a focus issue when going through it in the exact steps mentioned. The track view strips aren't getting focused when clicked, thus the Inspector doesn't change from the Mains. Logged this to fix, thanks!

This is likely to be something specific to the project as well, so please send us a version of that project with the audio.

Hi Steve, Can you post a screenshot of what the exact error message you're seeing is? Thanks!

Use the "Cakewalk Installer" link here: https://www.bandlab.com/products/cakewalk

Bindings are working correctly on my end. There haven't been any changes to bindings since the initial Early Access drop, so I'm not sure how you would see this issue now. You can try using the rollback installer to see if it works normally in 2021.12, then possibly rolling forward again if something went wrong during your install.

This sounds like it's likely something specific to Massive X on your system. I just confirmed it loads normally on our end. If deleting a plugin settings folder/file fixes it for you, it's likely something you'll need to address with NI directly.

Alternately reinstall from the separate downloader installer without BA:

Hi Robert, it appears that this is a UI issue (not new to this update). If you show Hardware Outputs in the Console View, you should see it only outputting to the original mono send despite displaying stereo. We'll look into it for the next release. Thanks!

This seems like your audio driver was likely in a bad state. Nothing in the update should have impact your audio performance like this. I'd suggest trying the update again and seeing if the problem persists.

If you run the in-app updates, it does a "silent" install that just shows you the overall progress bar for the update keeping your existing settings.

The latest version of the Web Installer should actually the demo projects available independently from the Studio Instruments installer which is where they are if you download the add-ons from BandLab Assistant.

Apologies, I end up looking at a bunch of projects and it slipped my mind. It did open fine for me in the latest versions, I'm not sure why it would be have any differently in 2021.09 vs 2021.11/12 as there weren't any dramatic changes that would have necessarily impacted that.

If you have a project that fails to open correctly, please send us a copy of it and we can investigate on our end.

Does this happen in every project? For example, if you create a new project, import an audio file, then export just that, does the app shut down?

Something is crashing when you're exporting then. Can you try setting the ExceptionHandlingSeverity to 7 in the Initialization File section of the Preferences and see if you can capture a dump file for when it crashes?

I'm getting messages from multiple other forum users right now, so I don't have anything disabled. If you can PM it to @msmcleod he can pass it along to me as well.

@Herbert Miron Odd... you definitely should be able to send me a PM...

The web installer actually should check for existing installations in its current version. This just changes the default toggle state for the additional installers when you run it. If you already had Studio Instruments installed previously at some point, the box will show as unticked, however if you need to reinstall that, you can simply check it and continue with the installer.

@jkoseattle It seems like something got corrupted in the project file itself. What seems to work to recover it is if you delete the synth instances that tracks 4 and 12 are using from the Synth Rack View. Then the console will open correctly again (and you'll need to re-add the synths.