Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 667446" data-attributes="member: 10858">Fact is that we need to make constantly workarounds for broken drivers. Currently Nvidia has acted quite nicely and fixed almost all the issues on WASAPI side (maybe they did see the nagging I did post <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).2nd fact is that the Xonar has completely broken drivers what comes to the audio clock. It is almost impossible to create any sane workaround for that kind of issue. Just think about a stopwatch that would behave the same way. First it runs too fast and then it almost stalls for a brief period of time to let the universe to catch it.Attached graph shows the own realm where Xonar's drivers live and how the time line is twisted. Red is the performance counter value that the driver gives (real time) and the blue is the playback position. As you can see it will &quot;play&quot; faster speed than the clock and then it will stall to slower speed to allow the correct stream time to be catched (I'm 101% sure that this is not the reality how HW works, but instead it is just lazy driver developers who haven't implemented the WaveRT drivers properly - after all the audio doesn't act weird with Xonar when the polling based mode is used).</blockquote>

[QUOTE="tourettes, post: 667446, member: 10858"] Fact is that we need to make constantly workarounds for broken drivers. Currently Nvidia has acted quite nicely and fixed almost all the issues on WASAPI side (maybe they did see the nagging I did post :)). 2nd fact is that the Xonar has completely broken drivers what comes to the audio clock. It is almost impossible to create any sane workaround for that kind of issue. Just think about a stopwatch that would behave the same way. First it runs too fast and then it almost stalls for a brief period of time to let the universe to catch it. Attached graph shows the own realm where Xonar's drivers live and how the time line is twisted. Red is the performance counter value that the driver gives (real time) and the blue is the playback position. As you can see it will "play" faster speed than the clock and then it will stall to slower speed to allow the correct stream time to be catched (I'm 101% sure that this is not the reality how HW works, but instead it is just lazy driver developers who haven't implemented the WaveRT drivers properly - after all the audio doesn't act weird with Xonar when the polling based mode is used). [/QUOTE]

Verification