Weird lag when hitting play and record

[Ivy Lew]

Hi, I have a weird microphone issue in Cakewalk by Bandlab.

I connected my mic (M70 Pro X by beyerdynamic, wired) to Cakewalk and it detects audio just fine, but every time I hit record or play it causes the program to load for a very long time. Since the microphone is in that track with record enabled, the software almost crashes when I ask it to do something like recording or just playing. 

I attached a screenshot to this post. Imagine I put the grey cursor/line thingy before my audio, then I hit play, the window freezes, gets smaller (fullscreen to the size you can see) and the cursor jumps forward a bit. Then, give it like three seconds, it starts playing/recordings like normal at the time I set before hitting play/record. It never really does crash. It doesn't get better the more I click and with record disabled, the lags/freezing is gone. The "keine Rückmeldung" in the upper left corner is German for like "no reply", I don't know what it'd say in English exactly.  My device manager lists the event "Geräteeinstellungen wurden nicht migriert" (device's settings weren't adopted). 

I remember setting the microphone latency to 0 somewhere in my computer settings (not cakewalk settings), but I don't remember where. I use version 29.9.0.125 with the latest drivers. Do you have any ideas?

Ivy

[John Vere]

If this is a USB Mike they are known to not work well. Some do have an ASIO driver which is the only driver that won’t have latency. Next best choice is WASAPI exclusive mode. 
For proper recording with any Daw an audio interface is required. One that comes with ASIO drivers. 
 

 

[mettelus]

There can be a lot of variables at play that can cause this (other apps, plugins, driver settings, audio buffers, graphics, system settings, etc.). The best place to start is to download and run LatencyMon, which will give insight into the processes running on your machine (tab on the top of LatencyMon). Run that in tandem with CbB, and if you are getting crashes while recording, you can also try simple playback of the project to see what the results are. Run LatencyMon for a few minutes, then stop it and look through the tabs at the top (specifically "Stats" and "Processes"). You can order the columns when reading that by clicking on the very top of each column, and you specifically want to find what processes have the highest values.