Noel Borthwick

Not use those plugins maybe

Did you get a crash dump generated?

Some plugins internal state must have gone bad and got saved. By deleting and reinserting it probably reset whatever was bad.

Just create a send from the effects bus to an aux track. Arm the aux track and record and you will get the wet output recorded. Simple Instrument track--->BUS [effects]---> MASTER Send | \---------> Aux track Also read this topic: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.13.html#1750199 In particular Capture the performance of guitar effects in real-time Here is the minimal configuration:

Besides bug fixes, @msmcleod has an extra surprise Christmas present feature that we'll be including that should make quite a few people happy

Your video doesn't show a crash or anything actionable. Please make a fresh thread and describe the problem in detail. If you have a crash include the dump file. Also it looks like you are using a custom theme. Switch to the default Tungsten theme and retest.

@Traveler can you do a test. Download process explorer from here: https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer Then launch Cakewalk with MMCSS off. Find cakewalk.exe in process explorer and right click and choose properties From the window that opens switch to the threads tab. Try and find the Apollo ASIO driver thread in the list of threads. The thread will have the driver name in it hopefully. Send a sreenshot showing the ASIO thread details.

@Helene Kolpakova we've finally fixed the load issues with your project - both the crashing problems as well as the case where it would load with the multi-dock and console view being non-functional. It was a complicated issue caused by a bug in the logic auto closing the template while opening the new project. The original bug dates back to 2016 so it's been there awhile. We're glad to finally fix it since it could have been the cause of many user crashes when opening projects, or projects drawing incorrectly after load. Thanks for your diligence in reporting it and spending the time to collect all the dump files and diagnostics I asked for. Much appreciated. I guess some consolation is you got a crash course in Windbg

Have you reported this to celemony?

Which version of Cakewalk are you running? We don't do any telemetry beyond at startup and shutdown for some basic things like session start/end. It can also be turned off in preferences. Does this happen only when opening the app and are you seeing activity past the startup of the app? Not everything is necessarily telemetry. If you are listing general internet output, it could be a variety of things causing it, including plugins checking for sign-in, check for activation, check for updates. All of these are normal activities and won't happen past startup.

@Milton Sica try this build. It should fix the crash deleting tracks with that plugin. https://drive.google.com/file/d/19lMfagiuU4iostxieU9B_705apfsheFv/view?usp=sharing

The engine stopping was just a symptomatic way to isolate it. There was an actual race condition in Cakewalk causing this problem. It's been fixed for the release. We'll post an updated build with that fix.

Great. I have a fix for the crash in your dump file. Will send you a build shortly.

Thanks for troubleshooting. There may be a false alarm. Some ilok plugins cannot run inside a debugger and we'll force the app to terminate. Which makes them very hard to debug of course! Your template that you sect me did not have any plugins as far as I saw. Were you using a different file to test? I'll look at your dump file.

@Mage_et_lent interesting so it was an AV causing the issue? Did the issue start with the 09 release? If so perhaps the signing caused it to somehow incorrectly flag the app slowing it down due to excessive monitoring of file loading.

@Helene Kolpakova Your template file opens fine here. As far as I can see there is no issue with the template. The first error 0xc0000005 is a standard access violation. 41d is an error I haven't encountered. Its description is: // MessageId: STATUS_FATAL_USER_CALLBACK_EXCEPTION // An unhandled exception was encountered during a user callback. #define STATUS_FATAL_USER_CALLBACK_EXCEPTION ((NTSTATUS)0xC000041DL) One cause is a kernel mode to user mode callback crashing. If thats the case here the issue would be your ASIO driver crashing which could explain why there is no dump file. Please try switching out of ASIO mode to WASAPI mode and redo your test. If it doesn't crash now this will isolate the problem to the asio driver.

If the app is disappearing then the exception is not being caught by Cakewalk. In some heap corruption cases or low level crashes this can happen. Does windows event viewer show any status about the crash? You can send a link to the template and we can check if there is a repro. Most likely this is plug-in related.

@Helene Kolpakova do you have crash dump files? Crashes can be the easiest bugs to fix if we have a dump file that shows the cause… Thanks for reporting your issues.

Thanks for doing the test. You should report this to UA support. This looks like some weird incompatibility with their driver when the app is running its threads in MMCSS mode. Other devices don't have this issue and as per this test we aren't changing the driver's configuration in any way. If they have questions, they can contact me.

@GreenLight can you please retest with the new EA build. There is a setting for sending all notes off if needed.

Another EA build has been posted that addresses a few user reported issues.

@HOOK and @Traveler we just posted an EA build that has a new option to enable MMCSS only for ASIO drivers (off by default) This allows you to enable MMCSS mode in Cakewalk but leave it disabled for the ASIO driver. Can you please try this on your machine and report back. I.e Turn on MMCSS but disable the ASIO MMCSS option.

If Cakewalk is crashing it should be producing a dump file. Find it (the crash dialog will link it) and send it to us and we can investigate what caused it.

Lol thats a first. Plugins freezing up the system because they aren’t authorized. Talk about aggressive copy protection

To clarify, its expected that plugin load balancing will result in more CPU use. Load balancing makes the CPU work harder to parallelize the workload by farming out plugin processing to multiple threads. By using more CPU it can finish the processing faster so it can result in fewer glitches with some plugin heavy projects. Another way to look at this is that multiprocessing trades CPU use for faster processing. During playback esp at lower latencies the goal is to finish all processing before the buffer size time, otherwise the audio device will cause clicks and pops.