• SONAR
  • [Solved] Super glitchy playback after Bandlab Reinstall?
2018/10/30 18:56:18
seanmichaelrobinson
Hello all!
 
I'm hoping someone might be able to point me in the direction of a solution.
 
I just had a complete reinstall of my OS (Win 10) and Bandlab, and playback is now glitchy and halting. However, the disk reads as 5 percent active and CPU hit at 18 percent. I have a very sizable buffer (1000 ms) and have changed to the high-performance power options etc.
 
Is this likely an OS problem? or is the newest Bandlab update somehow buggy? Anyone have any thoughts or observations? Running a Dell XPS on Win 10 (fully updated), CBBL, Focusrite 18i20.
 
Thanks!!
 
edit: added [Solved] - sc
2018/10/30 19:25:12
seanmichaelrobinson
UPDATE:

It was an issue with the video card. Update those drivers, folks!
2018/10/30 19:33:31
seanmichaelrobinson
Update the second: OOkay, it's back again, and definitely related to video rendering. The mouse slows while it's happening, and all looks herky-jerky simultaneous with the playback glitchiness.
 
Soooo.... still some sort of video card issue? I'm at a loss.
2018/10/30 19:51:15
Studioguy1
Ok, I have found that when I update, most of my preferred settings are adjusted, including my audio drivers.  I have to reset to the values I used in Preferences and generally have to reinstall my audio drivers.  Don't know why, but I will say that once I do that, all works well again with whatever updates they did.  I have now started writing down all my preferences before I update or anything like that, so I know how to get back to where i was.  I reiterate, once I do that everything seems to be solid and work well.
2018/10/30 19:54:27
John
If it is a Nvidia card uninstall the audio drivers for that card or disable them via device manager. Of course make you have the latest driver for it from nvidia. 
2018/10/31 04:59:31
seanmichaelrobinson
John, you're my hero! That was indeed the solution. All is running smoothly now (in fact, much smoother than it was before my full reinstall!)
 
I almost missed the fix, though, because I was looking for the Nvidia driver in the wrong place. I found another random audio driver under Audio Inputs and Outputs, but the Nvidia driver was under Sound, Video and Game Controllers.
 
 
2018/10/31 11:40:55
Tim Flannagin
Man, thanks for this thread. I have a Dell T5400 with dual Xeon E5420 processors running at 2.5 ghz. The machine has 32gb of ram and a M-Audio 1010LT audio / MIDI card running ASIO drivers. This configuration normally runs flawlessly, but after the latest Windows 10 update, I began having the same issue you described. It affected both Cakewalk and REAPER, so I was pretty sure it was a Windows issue. Your experiences have pointed me in the right direction (I think).
2018/10/31 16:00:28
seanmichaelrobinson
FYI to Tim and anyone else reading this with this problem--I reset the computer and immediately had the problem again. DISABLE the Nvidia drivers rather than uninstalling them. Otherwise they'll just come back to life on restart...
2018/11/01 12:14:42
pgw
seanmichaelrobinson
FYI to Tim and anyone else reading this with this problem--I reset the computer and immediately had the problem again. DISABLE the Nvidia drivers rather than uninstalling them. Otherwise they'll just come back to life on restart...


Did you try disabling audio in Nvidia´s Control Panel?
Doing so means it doesn´t even show up in the Device Manager.
Updating the Nvidia drivers (some versions, not all) enables it again.

Also, if you haven´t already, download Sysinternals Autoruns and turn off any unnecessary stuff there, for instance Nvidia´s telemetry.
You only need "nvlddmkm.sys" under "drivers" tab and NVDisplay.ContainerLocalSystem under "services" tab for the GPU, the rest of Nvidia´s services and programs are (usually) redundant in a DAW.
2018/11/01 14:01:25
Tim Flannagin
It turns out that for me, the culprit was my VS20. I installed the drivers with the intent of having another little DAW Controller on the desk. Although the VS20 Audio is disabled in CW, it was enabled in W10. It was also set to be the default communications soundcard. I disabled it in W10, and then also did the .ini hack to handle the spikes I was seeing on Core 1 / Processor 1, and it seems to have fixed me up.
12
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account