Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 662776" data-attributes="member: 10858">Well, my math isn't that bad <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" /> The reason why I was wondering that is that we don't want to have QPC - why would we since we can get that also directly by GetCurrentTimestamp(). Of course I could have misunderstood something.But the really weird part is that &quot;*&quot; works for dev PC and HTPC ( &quot;/&quot; works of course for the HTPC as well since it has 0.99999999 as the multiplier so the actual drifting is so minimal that it wont be noticeable. I think HTPC was only having the issue with the lost precission on delta calculation and it is now fixed). But using &quot;*&quot; causes approx one dropped frame on the dev PC per minute (need to reboot to make sure it is not something wierd).As you can see it is quite possible to write broken reference clock code that will behave just good enough on some systems.</blockquote>

[QUOTE="tourettes, post: 662776, member: 10858"] Well, my math isn't that bad :D The reason why I was wondering that is that we don't want to have QPC - why would we since we can get that also directly by GetCurrentTimestamp(). Of course I could have misunderstood something. But the really weird part is that "*" works for dev PC and HTPC ( "/" works of course for the HTPC as well since it has 0.99999999 as the multiplier so the actual drifting is so minimal that it wont be noticeable. I think HTPC was only having the issue with the lost precission on delta calculation and it is now fixed). But using "*" causes approx one dropped frame on the dev PC per minute (need to reboot to make sure it is not something wierd). As you can see it is quite possible to write broken reference clock code that will behave just good enough on some systems. [/QUOTE]

Verification