2

About two weeks ago I started to get major lag in my USB sound card. I have no idea why it started. It is happening when the card is being used in Audio Stream Input/Output (ASIO) mode too so this is something more severe than WDM audio modern. About two weeks Windows updated and I installed the latest Nvidia drivers and added a new monitor.

I've tried reinstalling all the various drivers for everything and all I've been able to do is seem to reduce the quickness of it starting to lag.

After some minutes (1-10) the audio starts to lag. It crackles and pops progressively worse for about 30s to 1m then the sound starts working but there is about 1-2 second delay. Everything works fine except for the delay and this also happens in ASIO. This makes it useless to do audio mixing. I have not had this issue for years of using the sound card.

If I change most settings related to the card in some way and sometimes not(some related to Nvidia or Windows) then it will temporarily fix the problem. Also, it seems that sometimes after not using the sound for hours it can fix itself and not have the lag, but then after minutes of use it will lag.

FWIW, I have had this system functioning just fine for about 4 years without issue. Because it is a lag issue in both WMD and ASIO this pretty much proves it is a deeper issue than some superficial fix.

Generally it is exactly like how latency issues work. If one sets the latency issues too low and there is too much of a load on the computer it will crackle and pop. This behaves like that but seems to get progressively worse(as if the CPU is getting more and more loaded, but here the cpu might have near 0 load). But then magically it all starts working fine but with a much longer latency.

It as if Windows added some type of adaptive latency algorithm that attempts to find the best latency but it is fubar'ed. It starts off with a low latency and then thinks it has to increase it and does so then sets it to some max of like 1 second.

This seems to only happen with the USB ASIO sound card and not the internal Realtek. It happens though with WMD and ASIO. It is something more serious than settings because I changed no settings when this started happening except what I mentioned which was totally unrelated.

When it starts lagging it is exactly as if I set a very large buffer size. I have to go change some audio setting, which I guess resets whatever issues is occurring, to get it to function but this lasts only for a minute or so.

I have no idea except to try to reinstall Windows and check it (which I can't do and don't want to do). Either the hardware is failing (such as a clock becoming unstable and not being able to sync at the correct sampling rate and so progressively getting out of sync) or some screwed up driver or setting is causing the issue.

The same problem happens on any sound configuration (16-bit 41.1k, 24-bit 48k) although the precise progression of distortion might change. I did change the USB port that the sound card was plugged in to and it seemed to function better and function longer. This makes me think it might be a problem with the USB port. Not sure if it could be a hardware setting; something in the BIOS such as overclocking, etc… but I did not change anything.


Update: I used a different USB port and plugged it in to the front port and it seemed to increase the time to lag… but the lag lasts several minutes as it builds up before lagging the audio completely. I will try to diagnose it along these lines and if I can't seem to find anything that makes sense I will put it on another computer to see if it is the device or not.

Also, I messed with 2 seemingly unrelated BIOS settings and I so far it ran for 50 minutes without lagging as far as I know (I left for that time). I still think the problem exists but at least it might be manageable and maybe there is a real fix. I do get some pops and clicks here and there tough. I'm wondering if it has something to do with the CPU itself or related settings that is causing timing issues?

Update2: I hooked the device up to another computer and I could not reproduce the issue. So either it is windows or my computer itself. I will install windows on another partition and check. Of course none of this helps determine the issue if it is a problem with windows, which it most likely is.

Update3: After about a month or so I no longer have these problems. I have no idea what I did to fix it. I was messing around a little with cables and such(nothing major) around the same time it started working. All I can think of is that the cable or connection might have short or open that works most of the time.

Update4: So I rebooted because I had my computer on for several weeks and the problem returned ;/ I did end up installing some USB drivers and other things in that time(and didn't have to reboot) so who knows ;/

5
  • 'simplest' if not cheapest triage would be first rty the interface on another computer & another interface on that computer - hone down where the issue is rooted. As a quick test, if you use something like Cubase, a quick way to reset ASIO is set the DAW to release ASIO in the background. That way, switching from DAW to any other app & back will reset quickly.
    – Tetsujin
    Commented Oct 17, 2020 at 10:03
  • Ah… another thought. Check for Nvidia Audio HD driver & remove if present. Best way to deal with NVidia drivers etc is to get rid of all the "smart" bits, Experience & all that bloatware & just manually install the graphics drivers. the rest of it is a total lag-fest if you need to do real work.
    – Tetsujin
    Commented Oct 17, 2020 at 10:07
  • @Tetsujin I thought about that but I don't have one working right not to do it. Given that I can seem to change the delay when it starts suggests it is not the device(if it was a crystal, for example, it wouldn't care about settings or usb ports, etc). I did remove all of nvidia stuff and disabled and uninstalled the nvidia audio driver and such(Also tried to use nvslimer and completely remove it)... same issues. I uninstalled it completely and same issue. It doesn't seem to be nvidia unless when I installed it the last time it screwed with some unrelated stuff.
    – Stretto
    Commented Oct 18, 2020 at 1:29
  • @Tetsujin If I open the aiso control panel and change any settings it will temporarily fix the issue for a few minutes. [Remember, this is also true if I change windows sound settings such as sample rate/bit depth] It definitely seems something to do with the buffers but it seems to be related to the sound driver. I'm going to install some older ones and see if that fixes it.
    – Stretto
    Commented Oct 18, 2020 at 1:34
  • @Tetsujin Using older drivers didn't work. I tried some other stuff with no luck. I remember before one of the things I did that triggered the windows update was messing with intel virtualization settings and stuff for emulators. I was using an android emulator and it kept crashing so I messed with a few things, but this was weeks before. The emulator then worked after the update and this also is when the issues started happening, so it might be something related to that.
    – Stretto
    Commented Oct 18, 2020 at 3:05

1 Answer 1

2

ASIO is not to be taken lightly. Although ASIO is notorious for having a very small delay, because you can set the buffer really low, misconfiguring this setting due to misunderstanding how things work can cause really bad problems.

To start, there are a few things you need to know.

When using ASIO, your soundcard will interact with your CPU in a low level way in order to make the small delay possible. The lower you set the delay, the more tasking it becomes on the CPU.

If the CPU can't handle it, the core the ASIO driver runs on reaches 100%, your audio will start to crackle.

That said, your soundcard is USB driven, so that adds another layer of complexity. If for example your power management sets the USB device to a lower powerstate, it underperforms which may mean that the same problem happens.

So that said, here are a few guidelines that you should check which should resolve the issue.

  1. Set your buffer (latency) no lower than necessary. Often enough 10-20ms is low enough for what you want to accomplish. Lower should only be done with a powerful pc and integrated soundcard, and even then only when absolutely necessary, as the overhead usually is not worth the performance gain.

  2. If its a laptop, it should be connected to a power outlet, not running on battery.

  3. Power management settings should be set to high-performance to ensure the USB is not running on power efficient setting and thus underperforms.

That said, you should ensure that the audio crackling is not happening because you are playing a song with lots of VST effects and instruments, and your CPU simply maxes out because you think your pc is fast, but it really struggles. Keep in mind that if you run a DAW that has no optimization for multi-threading, all vst's will run on the same core, quickly maxing out that core. The more CPU intensive your song is, the worse it gets over time as a song usually has a build-up. So... it may actually not be your ASIO but just underestimating what you are doing and how CPU intensive it is.

3
  • I know how Asio works, I'm a programmer, I've designed hardware, etc. As I said, the issue is independent of Asio and wdm. If it starts when using wmd then I go in to a daw with asio it's the same problem.
    – Stretto
    Commented Oct 18, 2020 at 1:31
  • I'm sorry but "I know how ASIO works because I'm a programmer" is actually exactly why I said the above, because I know how ASIO works because I'm an Audio Engineer. I play with it so much that I know all the ins and outs of ASIO, including Hardware ASIO and Software ASIO, and these can be beasts if you don't understand them correctly. WDM is not as CPU intensive, but the wrong latency or CPU + VST can still cause the same problems
    – LPChip
    Commented Oct 18, 2020 at 11:22
  • @Stretto - Please be respectful. If you find the answer helpful upvote it otherwise downvote it. It’s not necessary to indicate you believe the statements are “basic” or anyone is claiming you are clueless
    – Ramhound
    Commented Nov 20, 2020 at 21:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .