Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 509125" data-attributes="member: 10858">Yesterday evening I did notice that the current GetCurrentTimestamp() method is not accurate! (Same applies to the MPC-HC as they are sharing the same code <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />). It will lose some precision. It should be enough precise to be in ms range, but maybe it could as well lead into some minor drifting during hours? (I noticed this as I wasn't able to time code execution time properly. multiple GetCurrentTimestamp() calls are providing the same timestamp when QueryPerformanceCounter() is not ever going to be producing same tick count as the method itself has a slight overhead... so the GetCurrenttimestamp() needs to be fixed. I'll try to do it this evening).Ok, then it is most likely some other bug (some users have reported it) but on my HTPC &amp; dev PCs seeking is working fine.I'm already waiting for the patch <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />It's an onboard 9300.</blockquote>ok, that might be as well not fully supported. At least it is produced after 8xxx series (I guess it is based on the 9xxx GPUs).[/QUOTE]

[QUOTE="tourettes, post: 509125, member: 10858"] Yesterday evening I did notice that the current GetCurrentTimestamp() method is not accurate! (Same applies to the MPC-HC as they are sharing the same code :)). It will lose some precision. It should be enough precise to be in ms range, but maybe it could as well lead into some minor drifting during hours? (I noticed this as I wasn't able to time code execution time properly. multiple GetCurrentTimestamp() calls are providing the same timestamp when QueryPerformanceCounter() is not ever going to be producing same tick count as the method itself has a slight overhead... so the GetCurrenttimestamp() needs to be fixed. I'll try to do it this evening). Ok, then it is most likely some other bug (some users have reported it) but on my HTPC & dev PCs seeking is working fine. I'm already waiting for the patch :) It's an onboard 9300.[/QUOTE] ok, that might be as well not fully supported. At least it is produced after 8xxx series (I guess it is based on the 9xxx GPUs). [/QUOTE]

Verification