Reply to thread

Message

<blockquote data-quote="davidf" data-source="post: 661597" data-attributes="member: 19484">Just been playing downstairs with the proper HTPC and have found out the obvious.&nbsp; Now that I am looking at the correct figure and have been playing with the forward rewind etc. it is blatantly obvious that the error in the figures is introduced during the first few frames (probably during scrubbing).&nbsp; The stats on the ION don't work particularly well but I've attached the two pictures of first run and after a rewind.&nbsp; In the first the aud sys drift is close to your limit of .95 and increasing slowly and in the second after some playing it is a steady 1.00000000.You can either ignore the first x samples or weight the totalling to give more weight to later samples - this would bring the aud sys drift to it's steady state quite quickly rather than just have it tend towards it as it does now.The figures I was playing with from your earlier post don't seem as graceful as the ones from the ION which makes me think that the GPU and audio are tied by Nvidia (all done on the GPU).Could you send me a longer trace of the stats from your setup and I'll try a few different methods to see if the clock can be quickly corrected - the spreadsheet I was trying on is still in work and it would be interesting to see how much the clocks varied, at the end of your trace it was only a total of 15 nano seconds away but had got way off in the middle which is suspicious.</blockquote>

[QUOTE="davidf, post: 661597, member: 19484"] Just been playing downstairs with the proper HTPC and have found out the obvious. Now that I am looking at the correct figure and have been playing with the forward rewind etc. it is blatantly obvious that the error in the figures is introduced during the first few frames (probably during scrubbing). The stats on the ION don't work particularly well but I've attached the two pictures of first run and after a rewind. In the first the aud sys drift is close to your limit of .95 and increasing slowly and in the second after some playing it is a steady 1.00000000. You can either ignore the first x samples or weight the totalling to give more weight to later samples - this would bring the aud sys drift to it's steady state quite quickly rather than just have it tend towards it as it does now. The figures I was playing with from your earlier post don't seem as graceful as the ones from the ION which makes me think that the GPU and audio are tied by Nvidia (all done on the GPU). Could you send me a longer trace of the stats from your setup and I'll try a few different methods to see if the clock can be quickly corrected - the spreadsheet I was trying on is still in work and it would be interesting to see how much the clocks varied, at the end of your trace it was only a total of 15 nano seconds away but had got way off in the middle which is suspicious. [/QUOTE]

Verification