Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 667033" data-attributes="member: 10858">Should it be:In any case 1,0024541 is really alarming - it would mean that the audio and system clocks are running on really different speeds (other is 1,0024541 times faster than the other). This could be caused by few things:1) motheboard and HW really has those different running clocks - unlikely since the HWBasedRefClock=0 case works without drifting2) bug in audio renderer code related to the multiplier calculation - this could be related to the Xonar buffer size oddityPlease check how the multiplier behaves directly after starting the playback and then how (if at all) it changes during the playback.If te multiplier is stable from the start (and wotn for example slide from 1.02 to the 1.002 during few minutes) I'll provide one test binary that has the infamous * / change <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="tourettes, post: 667033, member: 10858"] Should it be: In any case 1,0024541 is really alarming - it would mean that the audio and system clocks are running on really different speeds (other is 1,0024541 times faster than the other). This could be caused by few things: 1) motheboard and HW really has those different running clocks - unlikely since the HWBasedRefClock=0 case works without drifting 2) bug in audio renderer code related to the multiplier calculation - this could be related to the Xonar buffer size oddity Please check how the multiplier behaves directly after starting the playback and then how (if at all) it changes during the playback. If te multiplier is stable from the start (and wotn for example slide from 1.02 to the 1.002 during few minutes) I'll provide one test binary that has the infamous * / change :) [/QUOTE]

Verification