Noel Borthwick

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.

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.

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.

@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.

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.

Hi @Art Munson The problem isn't solved its only masked and could happen anytime randomly. This is definitely a crash in the plugin. We got the plugin from the vendor and were able to reproduce the crash. We'll send the details to them to investigate on their end. Its a deep stack that shows the plugin crashing when we load its state. The exception happens always in the debugger for us. With the ExceptionHandlingSeverity set to 5 for us it wont crash (at least outside the debugger) but that is not guaranteed. This is the main reason why we are now flagging these intermittent crashes more deterministically to allow faults to be found and fixed. In this case only the plugin vendor can address the problem. The partial stack for the crash is as below. STACK_TEXT: 00000000`00148380 00007ffa`854111e9 : 00000000`00000000 00000000`00000000 00000000`00000000 00007ffa`00000000 : KERNELBASE!RaiseException+0x69 00000000`00148460 00007ffa`8541121b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : clr!NakedThrowHelper2+0x9 00000000`00148490 00007ffa`85411225 : 00007ffa`2689e75b 00007ffa`26965300 00000000`250a1420 00000000`00000000 : clr!NakedThrowHelper_RspAligned+0x1e 00000000`001489b8 00007ffa`2689e75b : 00007ffa`26965300 00000000`250a1420 00000000`00000000 00007ffa`83e359c0 : clr!NakedThrowHelper_FixRsp+0x5 00000000`001496d0 00007ffa`85416824 : 00000000`00149d30 00000000`00000000 00000000`00149a10 00000000`00000000 : clr!CallDescrWorkerInternal+0x83 00000000`00149710 00007ffa`855874c2 : 00000000`00000000 00000000`00000000 00000000`00149900 00007ffa`26232a08 : clr!CallDescrWorkerWithHandler+0x4e 00000000`00149750 00007ffa`85587935 : 00007ffa`26232a08 00000000`254f46c8 00000000`00000000 00000000`00149a30 : clr!CallDescrWorkerReflectionWrapper+0x1a 00000000`001497a0 00007ffa`843ad884 : 00000000`0014c440 00000000`0014a0f0 00000000`250ae660 00007ffa`8439fe00 : clr!RuntimeMethodHandle::InvokeMethod+0x465 00000000`00149dc0 00007ffa`843c51f2 : 00000000`00000000 00000000`0014a340 00000000`00149f20 00000000`250ae0b8 : mscorlib_ni+0x59d884 00000000`00149e30 00007ffa`2658e15a : 00000000`254f41a8 00000000`0014a230 00000000`0014a500 00000000`0014a340 : mscorlib_ni+0x5b51f2 00000000`00149eb0 00007ffa`85416913 : 00000000`250ae0b8 00000000`250a2478 00000000`254f41a8 00000000`00000000 : 0x00007ffa`2658e15a 00000000`00149f00 00007ffa`85416824 : 00000000`0014a340 00000000`00000000 00000000`00000000 00000000`0014c1e8 : clr!CallDescrWorkerInternal+0x83 00000000`00149f40 00007ffa`85571b27 : 00000000`00000002 00000000`0014c1e8 00000000`0014a230 00000000`00000000 : clr!CallDescrWorkerWithHandler+0x4e 00000000`00149f80 00007ffa`854c09dc : 00000000`0014a340 00000000`0014a128 00000000`0014a448 00000000`0014c1e8 : clr!DispatchCallDebuggerWrapper+0x1f 00000000`00149fe0 00007ffa`854c1899 : 00000000`00000002 00000000`0014a128 00000000`0014a100 00000000`0014c1e8 : clr!DispatchCall+0x79 00000000`0014a0a0 00007ffa`854c3223 : 00000000`00000051 00000000`ffffffff 00000000`00000000 00000000`00000001 : clr!CrossDomainChannel::MarshalAndCall_Wrapper+0x33b 00000000`0014a3c0 00007ffa`854c132a : 00000000`00000000 00000000`132de490 00000000`00000000 00000000`0014a418 : clr!MakeCallWithAppDomainTransition+0xe8 00000000`0014a4b0 00007ffa`854c0d3f : 00000000`12c53430 00000000`12c53430 00000000`00000001 00000000`0014c440 : clr!CrossDomainChannel::MarshalAndCall+0x4e8 00000000`0014c230 00007ffa`854c0cd7 : 00000000`71000000 00000000`12c53430 00000000`00000002 00000000`0014c0dc : clr!CrossDomainChannel::ExecuteCrossDomainCall+0x50 00000000`0014c270 00007ffa`854c0ba5 : 00007ffa`25ff6ac8 00000000`00000000 00000000`254f3e30 00007ffa`83e35dd8 : clr!CrossDomainChannel::CheckCrossDomainCall+0xb7 00000000`0014c2a0 00007ffa`85414b25 : 00000000`1303d5a8 00007ffa`85414835 00000000`0014c2e0 00007ffa`85411028 : clr!TransparentProxyStubWorker+0xc5 00000000`0014c4a0 00007ffa`25ef76da : 00000000`250ae110 00000000`250a2430 00000000`25288a50 00007ffa`83e35dd8 : clr!TransparentProxyStub_CrossContext+0x55 ........ 00000000`0014cc00 00000001`4059d485 : 00000000`00000000 00000000`23f30d10 00000000`0014cd90 00000000`23f2e0c8 : Cakewalk!CPlugWrapper::call_dispatcher+0xaa 00000000`0014cc40 00000001`4058cd6e : 00000000`00000000 00000000`0014cd90 00000000`23f2e0c8 00007ffa`ea3a2980 : Cakewalk!CPlugWrapper::SetChunk+0x45 ...... ...... 00000000`0014f300 00000001`40f80753 : 00000001`41fd5610 00000001`40f80740 00000000`00000000 00000001`41baa290 : Cakewalk!CCakewalkApp::OpenDocumentFile+0x4cb

Are you still using the realtek asio driver? Which version of Cakewalk are you running?

If it's exiting the app with that value set to 5 then the chances are that the same would occur in the previous release and it's a plugin bug. Are you sure this is a new issue?

@David Baay is that new to this release though? FWIW Im not seeing any issue with a punch region starting at time zero. The recorded clip is placed exactly at time zero. Please post a recipe if you are seeing it.

Hi Folks, Here is a new build that fixes the remaining sync issue with punch recording. Please try it and report back. If you can please test cases with normal record, loop record, punch record. With punch record also test combining it with loop record and try variations where the loop region intersects or fully encloses the punch region. Lots of permutations to test @Base 57 @David Baay @DeeringAmps @John Vere@giovannibuchelli

@Art Munson This crash isn't directly in the plugin. I'm making some changes to avoid some of these internal exceptions being caught. For now you can try the build I posted here and follow the instructions to disable the strict checking.

Did you try the fix I posted yesterday in the main feedback thread?

@Steven de Jong Thanks for your report. Its likely sub optimal UI in Omnisphere. Many plugins do very inefficient drawing and depending on the video drivers this can lead to glitches in audio. This is why in my original message I mentioned UI performance. Ableton has a vastly different architecture for its application UI (a cross platform framework) so its not surprising that some problems you see here may not appear in that app. We have observed very similar behavior in another application we are developing. Unfortunately Windows is a crapshoot when it comes to balancing realtime workloads with a busy user interface, esp with all the variances in graphics API's and drivers. So if you remove Omnisphere (or close the UI) does the problem get significantly better?

I've posted a build that has a fix for this and a handful of other issues. Can you all of you affected please try this and report back? Please also verify that punch in recording and loop recording behaves as expected and that audio is aligned. @DeeringAmps @Base 57 @giovannibuchelli