Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 638482" data-attributes="member: 10858">Things are progressing quite nicely, event driven mode is already implemented but I'm now having few deadlocks with sample handling (new thread was added that is playing around with the sample queues...).Hopefully those few usecases that cause deadlock (stop &amp; seeking <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />)) can be solved quickly and then we might have much better WASAPI support for different kind of audio HW (at least here the audio renderer is now really glitch resistant and even high CPU spikes from different applications that are hogging the CPU is not causing po(o)ps or glitches). There could be some really old WaveRT drivers that doesn't support event driven WASAPI mode (at least there were when Vista was released). For such audio HW people can use directsound mode.</blockquote>

[QUOTE="tourettes, post: 638482, member: 10858"] Things are progressing quite nicely, event driven mode is already implemented but I'm now having few deadlocks with sample handling (new thread was added that is playing around with the sample queues...). Hopefully those few usecases that cause deadlock (stop & seeking :D)) can be solved quickly and then we might have much better WASAPI support for different kind of audio HW (at least here the audio renderer is now really glitch resistant and even high CPU spikes from different applications that are hogging the CPU is not causing po(o)ps or glitches). There could be some really old WaveRT drivers that doesn't support event driven WASAPI mode (at least there were when Vista was released). For such audio HW people can use directsound mode. [/QUOTE]

Verification