Noel Borthwick

If it isn’t working in WASAPI chances are it wont work in windows and other windows apps either. Ensure that you set the sample rate to 16 bit 44.1, or 16 bit 48K. Pretty much all headsets work at those.

Use WASAPI shared mode which is the preferred format for USB headsets.

Have you raised the same issue with antares? They have a better chance of making it compatible since they wrote the plugin. The crash is in the plugin not the DAW. If you send the dump file to them they will know what the issue is. You can also send us the dump file for analysis.

That is correct

WASAPI Shared mode can run at different sample rates from other applications because Windows internally sample rate converts and mixes the output from all client applications. Even in ASIO mode some drivers can internally handle this by sample rate converting. If youtube is failing its typically because Cakewalk is in ASIO mode and the driver doesn’t handle multi client use well.

Hm I don't know why it would get reassigned unless the preview bus itself was deleted. I assume you don't have a repro for that. I'll take a look and see if I can spot anything obvious.

Its crashing in the plugin not Cakewalk so this isn't something we can investigate. Please contact the vendor and give them the dump file. Unhandled exception at 0x00007FFB4786E5DE (VD-DEEP.dll) in Orme_April_2021_2_04222021_192142.dmp: 0xC0000005: Access violation reading location 0x0000000000000018.

Make sure you set the driver mode in preferences to WASAPI shared mode. And plug in the headset

You are using a workspace that doesn’t show video view. Choose a different workspace like advanced and you will see it.

I don’t think this is new behavior. The data should go away if no actual edits were made.

The key is reporting the problem clearly The preview bus is stored per projects so it's normal for it to change if you have saved it differently.

Thanks for the feedback. They can make it easier to view the dynamics, and yes it looks cool too.

Performance issues at low latency that a few users reported in EA1 have been resolved in this update. Thanks for the feedback.

@Colin Nicholls Thanks dump shows the crash is while processing arrangement sections. Well fix it for the main release.

@Andres Medina can you provide some more information please? What kinds of envelopes are being used and are you sure that its related to this release? Please send a project file for investigation if possible.

Can you provide some more details about the PC setup? Which version of windows are you running etc?

@Jacques Boileau Thanks for checking. Yes if you could send me a link to the cwp file as a start I can take a look. There are no other changes of relevance in this release so its puzzling why you would see a difference.

Are you using the new tempo view or do you have lots of plugin automation envelopes in the project? It's hard to say more without looking at your project file so if you can share it somewhere it might show something. As far as the engine goes there shouldn't be any extra load in this release. However automation rendering is at a higher resolution so it's not impossible that there could be a marginal increase if you have lots of plugin automation. There is a configuration seeing to control the resolution as well if you want to play with it. See the release notes.

Nothing fancy lol, multi-column custom plug-in menus maybe. It’s a rework of the CbB plugin menu layout code that overcomes the Windows menu limitations and adds several customizations. Windows menus don’t support more than about 1100 menu items so this was the primary reason why we did this, but then we went beyond and added scrolling keyboard handling, multi-column support, better categorization, etc.

I’ll look into it. That’s not expected thanks.

We mute uploaded mixdowns if you are also uploading tracks, otherwise you would get doubled audio. If you upload just a full mixdown it shouldn't be muted. Are you seeing that happen? Its possible that there could be tiers for more than 16 tracks but I don't know of any immediate plans. Feel free to contact BandLab support for enquiries or requests. For BandLab specific help you can contact support@bandlab.com

Its most likely because those folders are not sub menus as I explained above. So you need to click them to open a new menu.

I’m not sure what you mean by “manually click on them”. If a plugin folder contains a large number of plugins it pops in a new menu window rather than a sub-menu. That’s previously existing behavior. At some point we may try and remove that behavior but its a relatively minor issue and only affects large lists of plugins. Glad you like the feature.

Today if you import into an existing project its always appended. We could insert at the current track position but it might get confusing if the user didn’t intend it. I’ll take a look about the clip names and see if there is an issue.

This is the same behavior if you create a new project and import or record audio then close before saving.