Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 644098" data-attributes="member: 10858">Anyone having the &quot;famous&quot; error code:Please test the WASAPI driver capabilities with following MS sample code application:<a href="http://blogs.msdn.com/b/matthew_van_eerde/archive/2008/12/10/sample-playing-silence-via-wasapi-event-driven-pull-mode.aspx" target="_blank">Sample - playing silence via WASAPI event-driven (pull) mode - Matthew van Eerde's web log - Site Home - MSDN Blogs</a>First run:silence.exe --list-devicesAnd then silence.exe --device + the name of the audio device listed in the 1st step. Please report what drivers and HW are returning error, since this seems to be a driver limitation <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> WASAPI pull mode is not supported all drivers and I'm not happy if we need to add that push mode (that causes such many pops and clicks for different HW).</blockquote>

[QUOTE="tourettes, post: 644098, member: 10858"] Anyone having the "famous" error code: Please test the WASAPI driver capabilities with following MS sample code application: [url=http://blogs.msdn.com/b/matthew_van_eerde/archive/2008/12/10/sample-playing-silence-via-wasapi-event-driven-pull-mode.aspx]Sample - playing silence via WASAPI event-driven (pull) mode - Matthew van Eerde's web log - Site Home - MSDN Blogs[/url] First run: [b]silence.exe --list-devices[/b] And then [b]silence.exe --device[/b] + the name of the audio device listed in the 1st step. Please report what drivers and HW are returning error, since this seems to be a driver limitation :( WASAPI pull mode is not supported all drivers and I'm not happy if we need to add that push mode (that causes such many pops and clicks for different HW). [/QUOTE]

Verification