Noel Borthwick

We have needed registration since the SONAR days. Nothing has changed. It allows us to know how many users we have and keep the software up to date. As of releases this year, activation is completely automatic and once you have signed in to your BandLab account (from within Cakewalk) there is no manual intervention required anymore. It should automatically refresh itself whenever needed without needing any user intervention or the need for BandLab assistant. Most other products require registration or worse, dongles. I think our system is as non intrusive as it gets for modern software. So I'm curious why you perceive this as being risky.

Cakewalk 2021.04 Update 1 Release Candidate [build 170] is now available! Please sanity check this. It contains several new fixes and improvements for recording. Thanks for your assistance so far in helping us make it a stable release. It will go live early next week.

Cakewalk 2021.04 Update 1 Release Candidate [build 170] is now available! Please sanity check this. It contains several new fixes and improvements for recording. Thanks for your assistance so far in helping us make it a stable release. It will go live early next week.

Thanks for the next build I've changed it to default to 1 so it will be opt-in for now. I really don't see why this would make any difference unless some plugins are throwing thousands of exceptions. Its a bit of a shame since in general we want errors to be flagged otherwise they will never get fixed. I recommend running with level 7 for troubleshooting since that is the most strict. We are already finding many previously undetected plugin issues.

Sorry I don't follow. When do you see the difference - loading or playing?

@u-u-u You can upload as a revision to an existing project. Here are two ways to do it: 1. Upload a new project from Cakewalk. Once you have done that any subsequent updates to the SAME project will upload as revisions to the BandLab project. i.e. The Cakewalk project will store a reference to the uploaded BandLab project and tracks changes from that point on. 2. Download a project created on BandLab to create a NEW Cakewalk project. Once you do this any changes to this project will upload as revisions to the ORIGINAL BandLab project. Similar to 1 the Cakewalk project stores a reference to the BandLab project and tracks changes from that point on.

Thanks do you see overhead only when loading the project or when playing it?

@Milton Sica With which plugins specifically? If you can provide a test project for us to verify it will be useful.

As I clarified in my PM there is no one size fits all solution. There are known cases with major vendors where running vst2 and vst3 versions side by side cause crashes. So the default is set to favor VST3 migration. Note that migration ONLY occurs if it is explicitly supported by the vendor so it the vendor doesn't want this to happen they should not allow it. This is not a new behaviour and has been in place since 2013

>>5 - Unhandled errors and heap corruption is detected (Default) @Colin Nicholls What is your exception handling level set to? In 155 it defaults to 5 if you haven’t set it. You can try setting it back to 7 to catch even more unhandled exceptions.

I don’t follow. It is already optional if you uncheck the box…

@Milton Sica Are you sure about this? There is no cost unless of course an error occurs. Have you tried it with a setting of 5 instead of 1? 5 will at least detect heap corruption. Please check and let me know if you can actually demonstrate a slowdown by timing it or posting a video. I’ve not noticed any slowdowns with many plugins.

This is the most likely culprit. Did you recently reformat your hard drive or disable short file names in the file system using some “optimizer”?

Thats not far fetched. We should throw a warning to confirm if export length exceeds some reasonable size.

@Alvaro Diez Cakewalk is not extending the project duration. Some event such as a tempo event or an envelope node got added (likely a bug) as a result of some operation. If you send your cwp file we can tell you what the issue is and how to fix it.

@Skyline_UK you can just send the cwp file. The audio isn't relevant to this issue.

This is unlikely to have anything to do with updating. Have you checked what the duration of the project you are uploading is? The exported region is shown in the dialog title bar. Sometimes projects have an automation node or event far in the future causing it to try and render a very long file.

If it fails to open (or close) capture a dump file from task manager and send us a link. That will show why its hanging. Instructions for capturing a crash dump manually are in the FAQ and my signature.

Its not abnormal for the module to be a different file because a single plugin may reference multiple dlls depending on what operations are done. In the latest update I've improved the reporting so that the main plugin name will be displayed in the crash dialog. The latest release added more extensive error handling which may be why you saw this error.

Sorry that you are having trouble. From your post it would appear that you aren't actually running the Cakewalk by BandLab program which is not a web application. You maybe referring to the BandLab web app which is completely different. To install Cakewalk you have to install it via BandLab assistant from here: After installing the latest version if you still have trouble post here and someone will help you. You can also contact Cakewalk support. It may be clearer if you post some screenshots of your problems. PS: this forum is only for the Desktop application. For help with the web applications please contact BandLab support directly.

Hi Philip, I'm glad that you were able to get your original issue resolved. If there is a bug in the spitfire instruments causing them to crash there isn't much we can do to solve that. You will have to work with them to rectify the issue. In the latest early access release I dialled back some of the stricter error handling. If Cakewalk is closing that means the error is not being trapped. You can turn on the strict error reporting and it should locate the crash and give you an error message. To do that: Open preferences | File | Initialization file and add this: Option: ExceptionHandlingSeverity Value: 7 Set it and restart the app and load the instrument again. If you get a crash message send the details.

@SteenE I PM'ed you a link to a build with some extra information. Can you please check it and PM me your findings.

@SteenE Did it actually upload the project however despite the error message? It looks like you ran into some sort of boundary condition where the back end returned an error we weren't expecting. The fact that you got the toast that it uploaded successfully seems to indicate that we think it was successful but an unexpected status code was returned. Is this happening on any project you try and upload? If so I'll send you a build that reports the status code and we can see why its happening.

Its linked in the error dialog itself. For more information read the problem reporting link in my signature

@greg54 Which version of Waves? Have you tried it with this build? If so please send the dump file.