IPB

Welcome Guest ( Log In | Register )

> foobar2000 General Forum Rules

This is NOT a tech support forum.
Tech support questions go to foobar2000 Tech Support forum instead.

See also: Hydrogenaudio Terms of Service.

WASAPI output: glitch just before album ends, after prolonged playback, Split from: WASAPI vs ASIO vs DirectSound, Topic ID: 92280
sshd
post Dec 11 2011, 22:39
Post #1





Group: Members
Posts: 207
Joined: 16-June 03
Member No.: 7218



There is a flaw in foobar2000 WASAPI output. About 1-2 seconds before an album runs out, a quiet glitch is heard, sometimes. The glitch never appears if you seek near the end, player needs to have played for a while. It is amazing that noone one else have heard this. I have experienced it with three different sound cards and my neighbor has same problem. Foobar2000 support forum suggests an increase in playback buffer, but that never helped me.

ASIO however works perfectly. Both native driver from Audiotrack and ESI, ASIO4ALL and ASIO2WASAPI - on all three sound cards.

Could be a conflict with SSRC resampler or Convolver.

It all comes down to implementation...
Go to the top of the page
+Quote Post
 
Start new topic
Replies (1 - 3)
JimH
post Dec 12 2011, 01:19
Post #2





Group: Members
Posts: 149
Joined: 14-July 02
From: Minneapolis
Member No.: 2588



Are you playing to a receiver?
Go to the top of the page
+Quote Post
Peter
post Dec 12 2011, 10:08
Post #3


foobar2000 developer


Group: Admin
Posts: 3276
Joined: 30-September 01
Member No.: 84



QUOTE (sshd @ Dec 11 2011, 22:39) *
There is a flaw in foobar2000 WASAPI output. About 1-2 seconds before an album runs out, a quiet glitch is heard, sometimes. The glitch never appears if you seek near the end, player needs to have played for a while. It is amazing that noone one else have heard this. I have experienced it with three different sound cards and my neighbor has same problem. Foobar2000 support forum suggests an increase in playback buffer, but that never helped me.

ASIO however works perfectly. Both native driver from Audiotrack and ESI, ASIO4ALL and ASIO2WASAPI - on all three sound cards.

Could be a conflict with SSRC resampler or Convolver.

It all comes down to implementation...

There is simply no way that this problem is somehow a foobar2000 bug because like you said, it occurs approximately [buffer length] before the end of playback, and foobar2000 would have to alter data already sent to the driver to perform exactly that. You could have brought it up in our forums (in particular mentioning that the issue is confirmed on cards from different manufacturers) so a special workaround can be added to the WASAPI component (don't let the driver know we're out of data to play, continue to send silence).
Go to the top of the page
+Quote Post
sshd
post Dec 13 2011, 22:59
Post #4





Group: Members
Posts: 207
Joined: 16-June 03
Member No.: 7218



The problem has been experienced on three different computeres and four different sound cards.

The computers something along ASUS/Q6600, Gigabyte/Q9550S and Gigabyte/i5-2400S - all with Windows 7.
The sounds cards: Audiotrak Prodigy HD2, Musical Fidelity V-Link, ESI Juli@, ESI ESP1010e.

I mentioned the glitch back in March, but since there was very little response, I assumed I were the only one in the world with this problem ~must be doing something special. When my neighbor recently told me of the same problem I made a list of what things we do in a special way:
- SSRC resampler to 96.000 Hz in Ultra mode
- Convolver or Convolver gapless - after SSRC resampler
- Default format in Windows CP set to 48.000 Hz, 24 bit.

The major glitch with wasapi and the V-Link went away after a complete windows reinstall.
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 30th August 2014 - 16:30