Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 662713" data-attributes="member: 10858">What you were using to calculate the total and calculated adjustment? Could we have the formula for calculating those, it would help on the debugging since we could see from 5 minute sample already how much the audio is drifting (of course it would require the calculated / approximated adjustment need to be known as well).Usually that HTPC shows only 0.9999999 as the multiplier - also the value from [code]pClockData-&gt;driftHWvsSystem = (m_dDurationHW - m_dDurationSystem) / 10000;[/code]Is quite close to zero, much smaller than on dev PC. Maybe it was still in the beginning of the sampled data where the fluctuations happened? Can you see that easialy with Excel? By hand it will be impossible to tell <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />No, I don¨t have Xonar and I wont be planning to buy such in the future either.Could be.</blockquote>

[QUOTE="tourettes, post: 662713, member: 10858"] What you were using to calculate the total and calculated adjustment? Could we have the formula for calculating those, it would help on the debugging since we could see from 5 minute sample already how much the audio is drifting (of course it would require the calculated / approximated adjustment need to be known as well). Usually that HTPC shows only 0.9999999 as the multiplier - also the value from [code] pClockData->driftHWvsSystem = (m_dDurationHW - m_dDurationSystem) / 10000; [/code] Is quite close to zero, much smaller than on dev PC. Maybe it was still in the beginning of the sampled data where the fluctuations happened? Can you see that easialy with Excel? By hand it will be impossible to tell :) No, I don¨t have Xonar and I wont be planning to buy such in the future either. Could be. [/QUOTE]

Verification