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.

 
Reply to this topicStart new topic
WASAPI output does not support pull/event/low-latency mode; why not?, Split from: WASAPI vs ASIO vs DirectSound, Topic ID: 92280
jaro1
post Dec 12 2011, 14:35
Post #1





Group: Members
Posts: 77
Joined: 22-November 08
Member No.: 62952



I wanted to use the opportunity given by a few last comments related to Peter's own wasapi output component to ask a simple question. If a sound driver supports low latency mode (WaveRT, driver pulls the audio data from an application - thence "pull or event" mode), does this component automatically use this mode or only "push" mode (application pushes the data to the driver)? I ask because there are no settings available, thanks.
Go to the top of the page
+Quote Post
JimH
post Dec 12 2011, 15:02
Post #2





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



QUOTE (jaro1 @ Dec 12 2011, 07:35) *
If a sound driver supports low latency mode (WaveRT, driver pulls the audio data from an application - thence "pull or event" mode), does this component automatically use this mode or only "push" mode (application pushes the data to the driver)? I ask because there are no settings available, thanks.

My understanding is that, at least in the case of WASAPI, there are two modes. One in which the driver "pulls" the data from the applicatioin, and the other in which the application "pushes" the data to the driver.

In our application, we provide two WASAPI modes, one for each type of data transfer.
Go to the top of the page
+Quote Post
tpijag
post Dec 12 2011, 15:46
Post #3





Group: Members
Posts: 2352
Joined: 19-May 08
Member No.: 53637



Other than rewording exactly what the previous poster stated, how does this provide insight to his specific question about Peter's component?
Go to the top of the page
+Quote Post
kode54
post Dec 12 2011, 17:01
Post #4





Group: Admin
Posts: 4619
Joined: 15-December 02
Member No.: 4082



Yeah, foobar2000 does not use the event style. I was under the mistaken impression that event style would require callbacks for pulling the data from the application.

I have also heard that event mode is semi-broken in Windows Vista 64-bit, in that 32-bit applications never receive the event triggers. This may not be correct.
Go to the top of the page
+Quote Post
jaro1
post Dec 12 2011, 20:11
Post #5





Group: Members
Posts: 77
Joined: 22-November 08
Member No.: 62952



Thanks, if i understand it right, Peter's own wasapi component doesn't use event mode, even if supported by the driver. What are the reasons behind such a decision? While it is clear, that low latency mode brings advantages mainly for IM or real-time communication apps, but also better skip/glitch resilience for playback apps and audio endpoint thread uses less cpu cycles under event mode.
I hope Peter will create an updated version of this component sometime in the future.
On the other side, i don't understand how could JRMC use event mode under AC'97 or other non WaveRT supporting drivers.
Go to the top of the page
+Quote Post
JimH
post Dec 12 2011, 20:52
Post #6





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



QUOTE (jaro1 @ Dec 12 2011, 13:11) *
Thanks, if i understand it right, Peter's own wasapi component doesn't use event mode, even if supported by the driver.

That was the way we orginally implemented it and it worked for most devices. Peter, if you would like to discuss it, Matt's address is matt at jriver.

Go to the top of the page
+Quote Post
jaro1
post Dec 13 2011, 09:25
Post #7





Group: Members
Posts: 77
Joined: 22-November 08
Member No.: 62952



Its a shame Peter didn't express to the question i asked, so i'll try it once more: what is behind the decision not to support low latency (event) mode in fb2k wasapi component, if supported by the driver? Somehow i don't believe the problem lies in technical difficulty or questionable reliability considering the fact, that W7 audio engine itself supports event mode when supported by the audio driver.
My comment is about reliability under some specific scenario and not about something related to audibility differencies!! Thanks

This post has been edited by jaro1: Dec 13 2011, 09:49
Go to the top of the page
+Quote Post
jaro1
post Dec 13 2011, 17:48
Post #8





Group: Members
Posts: 77
Joined: 22-November 08
Member No.: 62952



QUOTE (db1989 @ Dec 13 2011, 17:45) *
I split the threadjack about foobar2000’s WASAPI output component, and then I split a threadjack-within-a-threadjack. Voilà:
WASAPI output: glitch just before album ends, after prolonged playback
WASAPI output does not support push/event/low-latency mode; why not?


Only small correction: ...pull/event/low-latency mode...
Nevertheless, I doubt Peter will ever answer that question. Anyway, thanks for this.

This post has been edited by jaro1: Dec 13 2011, 17:59
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 September 2014 - 14:30