Audio dropouts making Cakewalk unusable.

[kevmsmith81]

Is anyone else getting this problem with the last update?  It's error code 4

Audio dropouts are getting to the point where I cannot use this DAW anymore.  Just to try the least demanding thing I could think of, I tried doing a single vocal take over a karaoke  backing track, and I'm still getting it.

I've tried switching from my interface's custom drivers to Asio4all, and it still happens.

For reference, I can have exactly the same things open in Reaper, with the same plugins using the same driver settings and I do not get dropouts in that - so I'm confident it's not my computer that's the issue, but Cakewalk.

I prefer to use Cakewalk, as I'm more confident in my way around it, but if this doesn't stop I will need to start learning Reaper properly!

 

EDIT:  Just for reference, my machine is a laptop running Windows 10 with a Ryzen 5 2500U CPU and 16GB RAM, so it's a fairly decent system.  It has a mechanical HDD rather than a SSD, but even so Cakewalk was fine before the last couple of updates.

Edited February 27, 2020 by kevmsmith81

[Feral State Sound]

1 hour ago, kevmsmith81 said:

Is anyone else getting this problem with the last update?  It's error code 4

Audio dropouts are getting to the point where I cannot use this DAW anymore.  Just to try the least demanding thing I could think of, I tried doing a single vocal take over a karaoke  backing track, and I'm still getting it.

I've tried switching from my interface's custom drivers to Asio4all, and it still happens.

For reference, I can have exactly the same things open in Reaper, with the same plugins using the same driver settings and I do not get dropouts in that - so I'm confident it's not my computer that's the issue, but Cakewalk.

I prefer to use Cakewalk, as I'm more confident in my way around it, but if this doesn't stop I will need to start learning Reaper properly!

 

EDIT:  Just for reference, my machine is a laptop running Windows 10 with a Ryzen 5 2500U CPU and 16GB RAM, so it's a fairly decent system.  It has a mechanical HDD rather than a SSD, but even so Cakewalk was fine before the last couple of updates.

Same here. I can't even try the free Full Bucket plugs like the "Tricent mk III" because I get an instant dropout (using Wasapi shared mode and Win 10).

In REAPER is all working perfectly fine. I like the Cakewalk layout much more but I am guessing that it needs a serious rewrite of the code.

[kevmsmith81]

4 minutes ago, Feral State Sound said:

Same here. I can't even try the free Full Bucket plugs like the "Tricent mk III" because I get an instant dropout (using Wasapi shared mode and Win 10).

In REAPER is all working perfectly fine. I like the Cakewalk layout much more but I am guessing that it needs a serious rewrite of the code.

Glad it's not just me.  As I said, I'm confident it's not my computer, as Cakewalk was working fine on this machine, and another one with a considerably weaker CPU, until recent updates.  Kinda sucks, as I know my way around it and  there's some old third party Plugins that I like, which will only work with Cakewalk due to authorisation.

But, at this point if I can't even track a vocal track over a karaoke backing track (one of the least demanding recording tasks given only two tracks in the DAW are being used), then I'm going to have to quit with Cakewalk and get to know Reaper instead.

[gustabo]

Uninstall ASIO4ALL, use native ASIO drivers and adjust buffers.

[kevmsmith81]

 

13 minutes ago, pwalpwal said:

(op already " tried switching from my interface's custom drivers to Asio4all, and it still happens.")

is there a dropout code? devs can use that

 

Yes - number 4, as per OP.  The guide states this is a buffering issue, but I can have the exact same tracks in another DAW (Reaper, or Mixbus 32c - take your pick), with the same plugins and not get dropouts in either of those.

 

4

WDM/MME/WASAPI output buffer not available for delivery to audio device.

Increase the Buffers in Playback Queue value in Edit > Preferences > Audio - Driver Settings.

 

As per:

https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=AudioPerformance.24.html

Edited February 27, 2020 by kevmsmith81

[kevmsmith81]

1 minute ago, pwalpwal said:

so when you use your "interface's custom drivers" (not WDM/MME/WASAPI/ASIO4ALL), what code do you get?

Same code for both.

I'm using a Presonus Audiobox 96, if that makes any difference.

Edited February 27, 2020 by kevmsmith81

[kevmsmith81]

11 minutes ago, pwalpwal said:

are you running the latest universal control drivers? https://www.presonus.com/products/AudioBox-USB-96/downloads

did you update that recently? can you try a previous version?

I will have to check - I believe it is set to update automatically, but I will look into that.  And, yes it is ASIO drivers!

Thanks

Edited February 27, 2020 by kevmsmith81

[lapasoa]

Consider that Presonus Audiobox 96 is a very cheap audio interface.

In any case you have to download the Asio factory driver for Windows.

After the download, adjust the buffer.

[kevmsmith81]

1 minute ago, lapasoa said:

Consider that Presonus Audiobox 96 is a very cheap audio interface.

In any case you have to download the Asio factory driver for Windows.

After the download, adjust the buffer.

It may not be a massively expensive interface, but it was working fine until the most recent Cakewalk updates.  And, as stated I don't get these issues in the other DAWs I've tried on the same computer, which suggests that the issue lies with Cakewalk and not the interface.

[Feral State Sound]

37 minutes ago, kevmsmith81 said:

It may not be a massively expensive interface, but it was working fine until the most recent Cakewalk updates.  And, as stated I don't get these issues in the other DAWs I've tried on the same computer, which suggests that the issue lies with Cakewalk and not the interface.

Don't worry, it seems that Cakewalk never has a problem here. All the DAW working perfect with the same VST, interface and settings, but Cakewalk has no problems ?

[Robert Bone]

When you use and its ASIO driver mode in Cakewalk, and the Universal Control ASIO drivers, can you please list:

1) Project Sampling Rate

2) ASIO Buffer Size (check it by going to Edit > Preferences > Audio > Driver Settings, in the Mixing Latency section - it should show 'number of samples' or something like that - might be 32 samples, 64 samples, 128 samples, etc... up to possibly 2048)

3) If you are trying to track/record, you should avoid having certain types of effects, such as convolution reverb or Linear Phase types, because they need huge ASIO buffer sizes in order to work properly.  You also, when recording, should keep your ASIO Buffer Size set at maybe 128 samples or a bit less, so that things sync properly.  When mixing, go ahead and throw in a convolution reverb, or a linear-phase EQ, etc., but now you should alter your ASIO Buffer Size up to either 1024 or even 2048.  SO - please list the plugins loaded into this particular project.

 

[kevmsmith81]

4 minutes ago, Robert Bone said:

When you use and its ASIO driver mode in Cakewalk, and the Universal Control ASIO drivers, can you please list:

1) Project Sampling Rate

2) ASIO Buffer Size (check it by going to Edit > Preferences > Audio > Driver Settings, in the Mixing Latency section - it should show 'number of samples' or something like that - might be 32 samples, 64 samples, 128 samples, etc... up to possibly 2048)

3) If you are trying to track/record, you should avoid having certain types of effects, such as convolution reverb or Linear Phase types, because they need huge ASIO buffer sizes in order to work properly.  You also, when recording, should keep your ASIO Buffer Size set at maybe 128 samples or a bit less, so that things sync properly.  When mixing, go ahead and throw in a convolution reverb, or a linear-phase EQ, etc., but now you should alter your ASIO Buffer Size up to either 1024 or even 2048.  SO - please list the plugins loaded into this particular project.

 

1) I think was set to 44.1, but I'd need to check when back at my laptop.  (I'm at work at the moment).  Was either that or 48, but I'm 95% sure it's 44.1.

2) It was set to 256 samples, but I increased to 512 when the dropouts started and it didn't help.

3) The only effect I ever have active when recording vocals is the Sonitus reverb as the CPU load seems to be low and I find having a gentle reverb helps when tracking vocals.  I'll have Waves GTR3 or TH3 active when recording guitar, depending on which sound I want.   All other effects get added once everything is recorded and I start mixing.

Edited February 27, 2020 by kevmsmith81

[Robert Bone]

What happens at 128 samples?

[kevmsmith81]

1 minute ago, Robert Bone said:

What happens at 128 samples?

I'll need to try and get back to you.

[Robert Bone]

I am off to doc, wll check back in 3-4 hours

[kevmsmith81]

39 minutes ago, Robert Bone said:

I am off to doc, wll check back in 3-4 hours

I won't be able to try until much later.  I won't be at my computer for at least another 6 hours or so. 

[David Baay]

1 hour ago, kevmsmith81 said:

it was working fine until the most recent Cakewalk updates. 

<begin lecture>

While it's possible something directly related to the update precipitated the problem, I feel compelled to point out that since Cakewalk is updated every month, the last update is pretty much always "recent".  And there have been numerous of users attibuting a problem to a Cakewalk update, and then eventually discovering something else changed in their system or Cakewalk or project configuration. Back when SONAR was updated anually, the incidence of 'was working fine until today' being reported randomly between updates was not significantly lower than it is now. Also, just because a performance issue isn't reproducible in another DAW doesn't rule out that the root of the problem is in the environment or a setting in Cakewalk that's been changed independently of an update. 

<end lecture>

Since dropouts are very often related to DPC spikes, I would start by running a DPC latency check:  https://www.resplendence.com/latencymon

If that checks out, try clicking the Reset Config button under Preferences > Audio > Configuration File. Cakewalk will archive a backup of the current AUD.INI, and replace it with a default. If performance improves, you can compare the default to the backup to see what changed.

[kevmsmith81]

22 minutes ago, pwalpwal said:

the op did state that the same driver settings and similar project in another daw did not show these issues ?

That said, the link provided in David's post is something I was not aware of and could be a useful tool.

However, given I could import the same stems into Reaper, stick the same plugins on and would not get dropouts.  I've also done the same with Harrison Mixbus 32c, which has EQ's, compressors etc running by default all the time due to the way that is set up and also not get dropouts, so I can't help but think that the issue very much lies with Cakewalk.

I should also point out that I am not trying to claim Cakewalk is bad, seeing how some people have been very quick to leap to its defence and assume it must be user error.  I repeat, I want to use Cakewalk - I was a SONAR user for a good few years before Gibson binned it off and  have always been very happy with the workflow.  However, these issues are currently making Cakewalk unusable for me.  I cannot complete a 4 minute vocal take or guitar take without getting a dropout.

[bitflipper]

If nothing has changed other than the executable's replacement, then it's perfectly reasonable to assume the problem lies there.

However, it's very common for users to assume nothing else has changed and be wrong about that. If you're recording a new project, then lots of things have changed. Do previous projects play without dropouts? Or does the problem only appear while recording new audio?

To answer the original question, no, I have not experienced any dropouts over the past 20 or so (including beta releases) updates. However, I keep my ASIO buffer size at 2048 and almost never change it, so I'm pretty much immune to buffer underruns under normal circumstances.

[Gswitz]

Io?

Does it drop-out with a new project?