Cakewalk is not responding

[Johnnyboyy]

So I just recently downloaded Cakewalk and had that same problem. I unchecked the audio inputs and outputs and it fixed it but now I have no idea which one it should be. It was originally set to fl studio for both input and output. Can someone lead me to the right direction? lol 

[Byron Dickens]

Did you even read the replies just prior to yours?

[Dan O'Rourke]

ASIO Drivers were the issue... Problem solved here!

[Will Smith]

I was watching a video to get Cakewalk running the best and the guy said to switch the drivers to ASIO. I had a error message that said my PC wasn't capable of using ASIO so I downloaded ASIO4ALL which was supposed to completely fix my problem, It worked for a while but then after I closed and reopened the app, when I was in the studio if I pressed any button the screen would turn white-ish. It said that Cakewalk wasn't responding and I couldn't do anything. So I deleted ASIO4ALL and switched the driver back to WASAPI exclusive and so far I haven't had any issues. The ASIO4ALL website was very sketchy but I tried it anyway because I found that many people were using it so they could run the ASIO drivers. But drivers seem to be a very detrimental problem.

[Lord Tim]

28 minutes ago, Will Smith said:

I was watching a video to get Cakewalk running the best and the guy said to switch the drivers to ASIO. I had a error message that said my PC wasn't capable of using ASIO so I downloaded ASIO4ALL which was supposed to completely fix my problem, It worked for a while but then after I closed and reopened the app, when I was in the studio if I pressed any button the screen would turn white-ish. It said that Cakewalk wasn't responding and I couldn't do anything. So I deleted ASIO4ALL and switched the driver back to WASAPI exclusive and so far I haven't had any issues. The ASIO4ALL website was very sketchy but I tried it anyway because I found that many people were using it so they could run the ASIO drivers. But drivers seem to be a very detrimental problem.

Just clarifying for anyone reading this, there's a couple of things that aren't quite right in this post.

First: Cakewalk and your PC is definitely able to use ASIO. What it's probably telling you is the ASIO driver you're trying to use is known to be problematic, likely the Realtek ASIO driver, which is known to be broken and will cause stutters and lockups. Do not use that driver at all.

Second: ASIO4ALL is also known to be problematic and can interfere with proper ASIO drivers. This isn't a real driver at all, it's just a wrapper for native Windows WDM, which Cakewalk can use natively, so there's no real advantage of using ASIO4ALL in nearly every situation. Cakewalk will warn you it could be a problem, but won't prevent you from using it, but they recommend against it.

You can only use one ASIO driver at once, so if you do have a professional interface with proper ASIO drivers, make sure you deselect all of the other devices in Preferences > Audio > Devices.

It doesn't sound like you do, however, and you're likely running an internal sound chip like a Realtek. In this case, if your device doesn't have proper (ie: not wrapped virtual ASIO "drivers") manufacturer supplied drivers, use WASAPI - either Shared, or Exclusive.

[Jeremy Oakes]

On 5/4/2021 at 4:29 PM, JohnnyV said:

A few months ago I did some testing while I was making a tutorial on setting up for on Board audio. I used 4 different computers and a bunch of  ASIO interfaces as well as the on board audio. 

I have always advised against on board audio and spouted the same old " Get an Audio interface or you will die " mantra over and over. 

But I was actually converted after running the tests using loopback testing and trying different buffers etc. 

Bottom line is you absolutely need an audio interface if you are actually a real musician and plan on recording audio. Your tracks will not be in sync otherwise unless you take the time to adjust the manual offset. As well as there's no professional audio connectivity to a computer. 

But if you are just a DJ, Producer etc.  and you don't need to record audio there's nothing wrong with a properly set up on board audio system. 

I work for hours on full projects that have a lot of plug ins and tracks using my on board audio in WASAPI shared mode. My Scarlett interface is sitting right there but there's no real reason to turn it on. It doesn't change anything about the work I'm doing. If I actually wanted to record anything I will turn it on then. I can record midi keyboards as well with WASAPI, no latency at all. Just do the usual by pass all effects. 

And please leave asio4all back in the W7 world. It serves absolutely no purpose now we have Windows 10 and  WASAPI modes for on board audio. It was so sketchy I couldn't even run tests with it. And then it causes issues with my ASIO drivers.  The Real Tech ASIO driver as noted above,  is real junk and it failed all loopback testing( when I could get it to work) 

So you only need to know these 2 things

For recording = A proper audio interface with ASIO drivers. 

For editing and midi = On Board audio using either of the WASAPI modes. 

I don.t understand. If you have a « proper audio interface with ASIO drivers » , why bother using On board audio for midi and editing ?

[57Gregy]

On 6/5/2023 at 6:39 PM, Jeremy Oakes said:

I don.t understand. If you have a « proper audio interface with ASIO drivers » , why bother using On board audio for midi and editing ?

Cactus has mentioned often that if all you're doing is mixing and mastering, such as for a musician client. then a stock sound card is usually enough. It's the recording and recording in synch that requires a better interface. I don't think he meant to change from your MOTU to a Realtek when you're finished recording.
 

[John Vere]

People will never get this right so I've stopped even talking about it. But in a nutshell

Working with Cakewalk and on board audio= WASAPI

Working with Cakewalk and a proper audio interface = ASIO. 

Nothing else to know.    Only ASIO can be in sync when overdubbing audio.  So if you are using WASAPI  you can fix it with a loopback test and adjusting the timing offset. 

My office computer does not have an interface connected so I use the Realtek and WASAPI shared. It's connected to a pair of Mackie powered Monitors. I call it Studio B.   I have never noticed any difference in running projects this way but I am not recording audio, just trying and testing  plug ins and  working things out while typing my narrations for videos.  I read these old threads and realize how much I've learned since then. 

Edited June 7, 2023 by JohnnyV

[Jeremy Oakes]

6 hours ago, 57Gregy said:

Cactus has mentioned often that if all you're doing is mixing and mastering, such as for a musician client. then a stock sound card is usually enough. It's the recording and recording in synch that requires a better interface. I don't think he meant to change from your MOTU to a Realtek when you're finished recording.
 

Fair enough, i just don’t trust Realtek. I believe you’ll get better results with a « real » audio device. YMMV

My Soundcraft 22MTK is all i need. Just saying …..

J

Edited June 7, 2023 by Jeremy Oakes