Noel Borthwick

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.

Perhaps you should contact iZotope about performance issues with their plugins. We can't solve those.

@Thomas Roller Where did you get this information from EastWest?

John ASIO is not an option when using USB input only devices. It should be fine to use WASAPI in this scenario. If there is a problem we need to fix it not work around it.

@immrama technically the issue is masked Only Motu would be able to actually fix the underlying problem which was flagged with the higher ExceptionHandlingSeverity. But its good that the problem is resolved for you.

@Fabio Rubato please try the build we posted yesterday that has relaxed some of the error checking. This should resolve your issue if it worked in the prior release. This doesnt fix the crash which is in the iZotope code but will mask the error most likely. You should send them the dump file for them to analyze. Insight crash: Unhandled exception at 0x00007FFA685E5AD1 (kernel32.dll) in Untitled_05062021_154914.dmp: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF. > kernel32.dll!IsBadReadPtr() Unknown Non-user code. Symbols loaded. [Frames may be missing, no binary loaded for iZInsight.dll] Annotated Frame iZInsight.dll!000000003892251a() Unknown Non-user code. No matching binary found. The waves error is also similar. I will pass this on to them for debugging. Unhandled exception at 0x00007FFA685E5AD1 (kernel32.dll) in Untitled_05062021_155320.dmp: 0xC0000005: Access violation reading location 0x0000000000000130. > kernel32.dll!IsBadReadPtr() Unknown Non-user code. Symbols loaded. [Frames may be missing, no binary loaded for WavesLib3.105_10.0_Win64.dll] Annotated Frame WavesLib3.105_10.0_Win64.dll!00007ffa23d27335() Unknown Non-user code. No matching binary found.

@M CTo clarify, in WASAPI shared you can use a completely different audio device as input from the audio output device. This is one of the advantages of WASAPI mode. However we don’t support using multiple different output devices at the same time. Let me know what specific combinations are not allowed. If you post a screenshot of your audio settings it will be clearer.

@DescendingIntoVertigo while that is a legitimate crash please try the new version scook linked to. The 2021.01 release had better crash detection and its possible that it is catching issues that you may not have seen earlier. In Update 1 I have changed this to be opt in so some issues may not get reported. Let me know if this changes anything.

@Nilo777 we’ll have to work with you collect some information. Ben has sent you a PM so please follow up since we need to understand what is different on your system leading to this issue. You can also run MSINFO32 and collect a log of your system configuration and send it to us.

The FXRack menus use similar UI to the arranger so that part is not surprising. Did you report this issue previously? Anything customized differently in Windows with fonts etc that you are aware of? Finally have you tried the early access update 1 build posted today yet?

Hi @Nilo777 what language are you using and what version of Windows are you running?

Thanks for reporting it. Yes the notes were not being read properly. Its fixed for the main release now. Note that these are the project notes read from the revision description and Not the lyrics from within the revision editor itself. While I can read the lyrics in BandLab, they are stored at the song level unlike Cakewalk that stores lyrics at the track level. So there is no easy way to map lyrics going back and forth.

The latest early access build should fix the menu display issues

Which module was crashing can you send the crash dump?

Thanks to @David Baay for helping isolate the punch issues. We have fixed all reported issues in the early access Update 1 released today. We'd appreciate anyone who had the punch and record compensation issues to retest and check if they are solved.

Try this build that we posted. Post feedback in the main 2021.04 feedback thread instead of making new threads.

Please try the latest early access Update 1 preview that we posted and report back. Please post feedback in the main 2021.04 comments thread instead of making new threads.

Did you open the project or Import it? The notes are transferred to the Project Info that you can find in the Browser. Not lyrics - notes are not lyrics.

Hi all, We just posted a early access build for 2021 Update 1 that we plan to release next week. We'd appreciate it if you could try this build and let us know if it fixes any of the listed issues you may have encountered. Thanks for all your help in reporting issues.

Well everything is a workaround depending on who’s perspective it is :) The whole idea of parameter changes being tightly coupled with the process call is a terrible design that leads to problems like this. In VST2 there was no such dependency. While it makes sense to send parameter queues during the process call there should have been a clean independent API to set parameters independent of processing. Instead they hacked that into a “dummy” process call. This is why so many issues arise. I had crashes from day one where plugins were crashing when we passed null pointers even though the spec says its OK to do that. In fact I asked Steinberg to add this as a unit test to their VST3 plugin validator, but of course many developers don’t test with that :-/