Jonathan Sasor

I can repro this one Keni, we'll look at it for the next update. Thanks!

The track Gain control is your signal level before FX and the fader is after FX.

This is correct. When we first implemented the feature in Cakewalk, the V4 trial would still allow the conversion to work under the hood without a full license. Version 5 does not allow this.

Melodyne is required to be installed to do Audio to MIDI conversion.

@Jeremy Oakes @scook I got a repro on our end, including one from well before this Early Access, so not a new issue, but it's logged for the next update. Thanks!

This is already fixed internally. We'll have an update for this release with this fix soon.

You can send me a PM with a dump

It's a different team that handles the development for BandLab Assistant as opposed to the Cakewalk app itself. The download page for Cakewalk now offers the Web Installer directly so a user would not need to have BandLab Assistant at all.

Is every project save slow or a particular one you're working in? Try creating a new project with a few things in it and save that.

I believe you've found yourself in the wrong place. This forum is dedicated to the Cakewalk by BandLab app for PC. If you're experiencing problems with the BandLab app for web/mobile, https://help.bandlab.com/ is where you need to go.

Thanks, when you send along the log we'll do some investigating.

The scan process runs independently from your project being loaded, so that shouldn't make any difference. If you could try the update again and see if it remains slower, we'll take a look into it. Thanks!

If you can get us a project where it's readily reproducible, we'll take a look into it and see where the problem is. Thanks!

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.