Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 650950" data-attributes="member: 10858">There is other, better MS sample code that can be used to verify the driver behavior a bit better (implementation is done with event based mode - just like with the audio renderer now). <a href="http://blogs.msdn.com/b/matthew_van_eerde/archive/2009/04/03/sample-wasapi-exclusive-mode-event-driven-playback-app-including-the-hd-audio-alignment-dance.aspx" target="_blank">Sample - WASAPI exclusive-mode event-driven playback app, including the HD Audio alignment dance - Matthew van Eerde's web log - Site Home - MSDN Blogs</a>Could you check how it behaves? If the glitches aren't happening with that, try to find a longer WAV file that has format the WASAPI device accepts (the sample code doesn't do any conversion, so the sample rate, channel amount etc. must match to the device capabilities).Reclock is most likely using that (ugly) polling based buffer filling since it works with NVIDIA HDMI drivers as well. If it appears that there is huge amount of cards that require the polling option (ugh...) to be used I will consider adding the implementation back as a fail safe registry option (it wont be just copy &amp; paste, but instead requires quite much work to adapt it to coexistent with the event based buffer filling).As extra test (if you are willing) check:1) older renderer versions (the ones that have the polling based code still in use)2) the latest renderer on the different (previously used) audio HW</blockquote>

[QUOTE="tourettes, post: 650950, member: 10858"] There is other, better MS sample code that can be used to verify the driver behavior a bit better (implementation is done with event based mode - just like with the audio renderer now). [url=http://blogs.msdn.com/b/matthew_van_eerde/archive/2009/04/03/sample-wasapi-exclusive-mode-event-driven-playback-app-including-the-hd-audio-alignment-dance.aspx]Sample - WASAPI exclusive-mode event-driven playback app, including the HD Audio alignment dance - Matthew van Eerde's web log - Site Home - MSDN Blogs[/url] Could you check how it behaves? If the glitches aren't happening with that, try to find a longer WAV file that has format the WASAPI device accepts (the sample code doesn't do any conversion, so the sample rate, channel amount etc. must match to the device capabilities). Reclock is most likely using that (ugly) polling based buffer filling since it works with NVIDIA HDMI drivers as well. If it appears that there is huge amount of cards that require the polling option (ugh...) to be used I will consider adding the implementation back as a fail safe registry option (it wont be just copy & paste, but instead requires quite much work to adapt it to coexistent with the event based buffer filling). As extra test (if you are willing) check: 1) older renderer versions (the ones that have the polling based code still in use) 2) the latest renderer on the different (previously used) audio HW [/QUOTE]

Verification