Reply to thread

Message: <blockquote data-quote="Scythe42" data-source="post: 508921" data-attributes="member: 95833">I just chose a random small offset here to see if it had any impact. Since my first tries with the scheduler I just took the actual delay and subtracted 5 ms to be sure the thread will never be late. I haven't touched this area since then. Now it's time to revisit this area before finalizing the patch. Current working assumption: because the delay is an integer (if I'm not mistaken) derived out of delta/10000 threads woke up late, because the value is rounded. This introduced and additional lag that build up over time and wasn't compensated properly. Need to check what a trace has to say about this. So far it's just a hunch and can be total BS.Makes sense. It was constant and that's a good thing. Probably some additional latency is accumulating so that after 34 seconds a frame is finally more than 41.66ms late and needs to be dropped to keep audio/video in sync. I need to take a look at the timestamps if there's really a constant drift of roughly 0.2ms in this scenario. 19 frames dropped too much per hour of played video is not acceptable <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />. Microseconds, hours of playback. That's progress. I see. I tested with the original DLL. Rewind seems to be broken there as well. No frames displayed, only when you change the rewind speed. So I won't investigate this any further at the moment. I provide it as soon as I finished my testing scenarios. I probably won't touch the code anymore unless I find a newly introduced issue.From my latest test with the same file as usual:[CODE]13-09-2009 14:02:48.173 [c28]OnClockStart13-09-2009 14:02:48.173 [c28]Flushing: size=013-09-2009 14:08:38.112 [12b4]OnClockPause13-09-2009 14:08:38.118 [12b4]OnClockStop[/CODE]Roughly 6 minutes at the 23.971Hz my GPU reports (I'm still think the driver reports inaccurate or it drifts a bit). No dropped frames. Usually there are some when playback starts, but not always. No clue why (probably frames are already provided but the presenter is not fully ready). But I don't really care at the moment if the first view frames need to be dropped to get in sync. No drift, no late frames. Under the original DLL playback would have drifted already for a few frames by now. Audio was still spot on.It's an onboard 9300. WALL-E, Dark Knight and Eagle Eye are in the mail. Haven't seen them in fully 1080p glory yet. Also it's time for my yearly Godfather I+II double feature. So I'm set for now...</blockquote>

Verification