Skip to main content

Topic: foobar, audioengine d1 dac and wasapi (Read 5804 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • elik_r
  • [*]
foobar, audioengine d1 dac and wasapi
I've recently purchased the said DAC.

Sound quality is great, but there are stuttering issues with foobar. Apparently this is known from audioengine's perspective, and they've specifically stated in their manual that one should set the buffer setting to a minimum.

Unfortunately, this doesn't solve the problem, and I can get occasional glitches on random (and more when opening/closing programs and the like).

Is this issue going to be addressed? I've tested a trial copy of J River and had no glitches, which led me to believe that this might be a software problem. I've also tried out MusicBee, and it also suffers from this, although a bit less.

Is this something general about USB dacs? or is it limited to the audioengine D1 alone? Has anyone found a way around this?

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
foobar, audioengine d1 dac and wasapi
Reply #1
they've specifically stated in their manual that one should set the buffer setting to a minimum.

Unfortunately, this doesn't solve the problem, and I can get occasional glitches on random (and more when opening/closing programs and the like).

Are you absolutely sure that the recommendation is to decrease the buffer size? Dropouts and stutters can be normally avoided by increasing it. You might want to try the default DirectSound output engine, too.
It's only audiophile if it's inconvenient.

  • elik_r
  • [*]
foobar, audioengine d1 dac and wasapi
Reply #2
they've specifically stated in their manual that one should set the buffer setting to a minimum.

Unfortunately, this doesn't solve the problem, and I can get occasional glitches on random (and more when opening/closing programs and the like).

Are you absolutely sure that the recommendation is to decrease the buffer size? Dropouts and stutters can be normally avoided by increasing it. You might want to try the default DirectSound output engine, too.


yep, this is from the D1 FAQ on audioengine's website (http://audioengineusa.com/about/audioengine-d1-faq):

I'm having trouble using my D1 with Foobar in WASAPI and KS mode. What do I do?

In the Foobar control panel, under Preferences->Output, set the buffer length to minimum. A few customers have mentioned that WASAPI mode is more stable when used under WinAmp, so try that as well.



Using direct sound wouldn't solve my problem since I want a bit perfect output (that's the reason to use wasapi in the first place).

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
foobar, audioengine d1 dac and wasapi
Reply #3
I'm having trouble using my D1 with Foobar in WASAPI and KS mode. What do I do?

I don't really know anything about that DAC, but is ASIO an option?

In the Foobar control panel, under Preferences->Output, set the buffer length to minimum. A few customers have mentioned that WASAPI mode is more stable when used under WinAmp, so try that as well.

Did you try increasing the buffer? The notion of having a short or no buffer to improve audio quality or whatever is an audiophile myth. The point of having a buffer is to actually defeat glitches and dropouts.

Using direct sound wouldn't solve my problem since I want a bit perfect output (that's the reason to use wasapi in the first place).

I understand, but please try it to help us confirm whether this is a WASAPI problem, a general foobar2000 problem, or a problem of your DAC.
  • Last Edit: 04 May, 2012, 02:36:32 PM by Kohlrabi
It's only audiophile if it's inconvenient.

  • elik_r
  • [*]
foobar, audioengine d1 dac and wasapi
Reply #4
Asio isn't an option, neither is kernel streaming - both exhibit the same problems.

Increasing the buffer prevents playback from working. I'd say that the more you increase the buffer, the worse it gets. And 1000ms is a threshold which when crossed - breaks playback altogether.

DS doesn't suffer from any problems for all I've noticed (apart from reduced sound quality).

  • Andreasvb
  • [*][*][*][*][*]
foobar, audioengine d1 dac and wasapi
Reply #5
Asio isn't an option, neither is kernel streaming - both exhibit the same problems.

Increasing the buffer prevents playback from working. I'd say that the more you increase the buffer, the worse it gets. And 1000ms is a threshold which when crossed - breaks playback altogether.

DS doesn't suffer from any problems for all I've noticed (apart from reduced sound quality).

There's no reduced sound quality, unless proven: http://www.hydrogenaudio.org/forums/index....974#entry149481
Windows 10 Pro x64 // foobar2000 1.3.10

  • Kohlrabi
  • [*][*][*][*][*]
  • Global Moderator
foobar, audioengine d1 dac and wasapi
Reply #6
Increasing the buffer prevents playback from working. I'd say that the more you increase the buffer, the worse it gets. And 1000ms is a threshold which when crossed - breaks playback altogether.

What are you referring to in your second sentence, how can it get worse than "not working"? Also, WASAPI output in foobar2000 works with buffer sizes of up to 2000ms. Sounds like the driver for your DAC is seriously broken, try to contact Audioengine about it. In the meantime you should stick to DirectSound output, since...
DS doesn't suffer from any problems for all I've noticed
  • Last Edit: 05 May, 2012, 09:51:23 AM by Kohlrabi
It's only audiophile if it's inconvenient.

foobar, audioengine d1 dac and wasapi
Reply #7
I recently bought an Audioengine D1 (amazing little DAC btw) and suffered from the same clicking/popping issues when using WASAPI. In foobar2000, with the buffer set at 500ms, the audio cut in and out and was extremely crackly. Reducing the buffer helped a little, but it didn't solve the problem. Increasing it made the problem even worse, as elik stated.

Then I switched to Jriver media center, which fared much better. Using WASAPI-Event Style with the default buffer of 100ms, there was still occasional popping/clicking. As with foobar, increasing the buffer oddly led to more popping. Believe it or not, setting it at the minimum 10ms solved the problem. Still heard a few infrequent pops now and then; setting Jriver to high process priority (in task manager > processes) seems to have gotten rid of the rest of them. Haven't had a problem since. *fingers crossed*

As an aside I'd also highly recommend Jriver, after having used it for a couple weeks. Despite being feature-packed it's incredibly fast, much more so than iTunes, and much more user-friendly than foobar2000.