Noel Borthwick

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

If turning off MMCSS in Cakewalk fixed the glitches this is most likely a driver bug. We’ve seen drivers that don’t properly error handle cases where MMCSS is already enabled by the host. A similar issue happened with the Lynx driver which we reported to them and was subsequently fixed. Drivers should handle the host setting threads to MMCSS.

How many cores does your CPU have? Setting Mix thread count to 6 tells cakewalk to limit audio engine worker threads to 6 irrespective of how many cores your PC has. This will use less CPU resources for mixing but will also not load balance a project with many tracks as well so you could get overload earlier. A max of 6 tracks or buses will be processed in parallel with that setting. By default cakewalk uses one thread per core. If it works better after limiting the threads to me thats indicative that the driver is relying on some processing in user mode and being starved. Cakewalk switches all its threads to time critical mode and uses MMCSS by default. Have you tried disabling MMCSS and plugin load balancing?

@Mage_et_lent are you still seeing the problem? If so send the project file and we can try it on Win 7 here.

Its possible that its exposing issues with certain plugins. See if you can try and narrow it down

@PJH We aren’t aware of artifacts with elastique. If you have a demonstrable problem send a zip of the project that exhibits the issue. If its a problem with elastique we can forward it to the developers.

@Tez Thanks for sending the project. We've identified and fixed the issue. For the record it wasn’t a timing issue but a bug where under certain conditions it would not determine the dependencies of the aux track. So it would render the bounce as if there was nothing sourcing the aux track, leading to silence.

Yes it splits off the left and right channels into separate mono tracks and hard pans the tracks left and right. If its a multichannel wave file it will extract each mono channel but won’t change the pan. With a surround file it will attempt to set the corresponding surround channel if there is a surround bus (IIRC)

You can upload it to a file share and PM it to me and Jon

@GreenLight are you only getting stuck notes with notes played from the keyboard or is it also playback of notes from the track that are sticking. Is it simple track and keyboard controller playback or are you also using generative effects/synths etc. Are you sure that this is specific to the 09 release? i.e. if you roll back do you still see this?

Which VSTs?

Look at this video around 6:15. Read about audio snap.

Yes mine has a vesa mount like other monitors.

No because as far as routing goes an input on a track from a patch point behaves the same as a hardware input. Arming a track shouldn’t impact what you hear from other tracks. If you are feeding one tracks input from other tracks you will need to manually solo to hear just that track.

Will investigate thanks.

Yes

@István Máté this is fixed in the early access release we just posted above

@Kvancho there is a build with a fix for this issue.

We just release an early access build that we plan to release on Monday. It has a few fixes to reported problems. Please check it out.

This is unlikely to be related to your project file. Meters going into the red are a sign of the plugins generating garbage floating point data or denormals. Most likely caused by bugs or corrupt data in the plugins themselves. Some plugins also intermittently misbehave when the double precision engine is enabled or with Plugin load balancing active so you can experiment with disabling those options. If the issue persists contact the respective plugin vendor to troubleshoot further since its not a host problem.