Noel Borthwick

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

On 10/24/2022 at 12:19 PM, Tez said:

It was temporary, I'll try and recreate it and check if it's consistently behaving as previously described. How do you want it sent?

Update: @Jonathan Sasor  Hi, I messaged you with a project link.

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

10 hours ago, scook said:

Here is a video showing an imported stereo clip imported and what happens when importing the same clip with Import as Mono Tracks enabled

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)

1 hour ago, Tez said:

It was temporary, I'll try and recreate it and check if it's consistently behaving as previously described. How do you want it sent?

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

1 hour ago, GreenLight said:

It did happen with no sustain pedal in use when I played synth parts with Diva as well.

I will continue producing and report back, while also keeping in mind what you wrote above. Thanks!

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

14 hours ago, GreenLight said:

>The MIDI All Notes Off message is no longer sent to VST plugins on transport stop. Since Cakewalk manages all MIDI note on's explicitly, >sending note off messages for just those notes, the All Notes Off message is no longer required.

I updated to 2021.09 yesterday, and first of all - thanks for the bugfixes! 😀

After the update, in just a few hours I've been getting more hanging notes than usual with several of my VSTi:s... it feels like it ought to be directly related to the removed MIDI All Notes Off message?

An idea – if permitted in this thread – would be to make an option under Preferences / Project / MIDI / like "Send MIDI All Notes Off message on transport stop". So that it could be user-enabled in circumstances that require it?

EDIT: Even sustain pedal messages seem to be hanging... (Happened once so far.) Am I the only one experiencing this?

Which VSTs?

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

Yes mine has a vesa mount like other monitors.

12 hours ago, Will. said:

Now the question is: and I'm sorry if this is in the posted in wrong topic - isn't there a way for track 1 to mute behind the scenes and only let the armed track be heard to give the user the actual picture of what is being projected to him through these inputs? 

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.

6 hours ago, Tez said:

Bounce to track bug:

I setup a test project (44.1-16 WASAPI Exclusive) with 2 identical length stereo audio tracks taken from a similar projects rendered audio files, ergo the audio files are 32 bit. The sends of both audio tracks were set to the same aux track which had a couple FX plugs, and the aux track's send was to a hardware out.

All tracks were selected for the range of the audio files. On executing a bounce to tracks for source category tracks the following occurred:

1. Selecting just the aux track not in real-time with the buffer set to "playback" the rendered track was all silence.

2. Selecting just the aux track  in real-time  rendered the track normally.

3. If the track was rendered as per 1. and the immediately followed by a second bounce as per 1. the track  rendered normally.

This is odd behavior,  it feels like some kind of a timing issue, but wadda I know 🙄

Will investigate thanks.

Yes

On 10/17/2022 at 5:09 AM, István Máté said:

Yes. In my use case, I create MIDI multitracks for live use, main (Master) mix is for myself during creation, but each track is sent to a dedicated hardware output (Dante Virtual Soundcard) via Send. I usually send stereo channels, only the Metronome aux (stereo channel) and the Bass (stereo channel) is sent mono to a hardware out L and R. In this version both the Metronome and Bass were present in the hardware out's L and R, while in previous versions I had the Metronome in L and Bass in R. Did notice, that changing the Metronome aux to mono did solve the issue for the metronome, I presume, that changing the Bass channel to mono would have solved it for Bass too, but I did not test it, I rolled back.

I presume, that this is not intended, sends to a mono hardware out (more specifically, to only one channel of a stereo hardware out) from a stereo channel should not creep into the hardware out's other channel.

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

Its, not clear what you were trying to do in the video.  It seems you were confused by the default audio and midi track that are pre created in a new project.
The dialog for insert synth is the advanced dialog that happens when you insert a synth manually from the browser.

There is an easier way to insert an instrument track. Click the big + button at the top of the tracks view. In the instrument tab pick the instrument you want and click Create. Thats it - the synth routing is all set up for you and you can immediately play the synth.

I have the Keystep32 running here and there are no issues with MIDI from the keyboard.
Make sure you have their latest MIDI drivers installed from the MIDI Control center. 

Have you tried record enabling a MIDI track and testing recording from the controller?
BandLab support won't necessarily be able to assist you with configuring third party hardware controllers.