Reply to thread

Message: <blockquote data-quote="tourettes" data-source="post: 508794" data-attributes="member: 10858">Sounds like you have made good progress on improving the scheduling algorithm. About that 5 ms, that propably needs to be calculated based on the refresh rate? btw. do we know what would be the optimal time for painting the frame? How much early to v-sync we should be? (We could calculate some average based on the time it takes to render the frame on D3D and adjust the 5 ms sync spot with it). Of course this will be the fine tuning phase, and doesn't have to be done for 1.1.0 release (but well see how the testing & implementing goes.)That is the problem domain I'm currently working on (playing video stutter free on non-matching Hz/fps or GPU & audio clocks drifting away from each other) It won't allow 24 fps to be played on 25 / 50 Hz like ReClock does, but those small inaccuraties like display or GPU not capable for 23.976. So, at least you don't currently have to worry about that juddering / stuttering you are seeing with 41.66 s intervals.Theoretical 41.66 second interval turning into 34 second interval could be maybe explained with for example that we cannot present the frame on exactly the same time as v-sync happens. I'm not sure how much safe zone there is (time to try to Google it, but I guess it will be hard to find any good answers...). Mabe there is also similar safe zone after the page has been flipped? I'm really newbie when it comes to the DirectX <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />But sill, I'm quite sure that the juddering on 34 second interval you are seeing is definitely caused by the 23.976 vs. 24 difference.Normaly there would be the SetRate( or was it something else, don't have the source codes at the moment) call to the presenter, but unfortunately there is no audio renderer that supports > 2.0x speeds so MP has to fake the REW/FWD with seek + play loopping. Currently I have no idea how you could detect the REW/FWD (I'll let you know if I figure something out).Yep, sounds like the root cause is pin pointed and fixing is already progressing nicely. Next step would be to provide a dshowhelper.dll for our user base to be tested. If you provide the patch for the source codes I'll arrange a new thread for testing purposes so that we can get more test coverage (not just the people who have issues with 24 Hz playback.)Too bad that you are having issues with PowerStrip, as it is pretty accurate (more accurate than DirectX itself) when it comes to reporting refresh rates. By any change do you have NVidia 8xxx/9xxx/2xx series GPU? Those aren't fully supported by PowerStrip as Nvidia hasn't released needed documentation of their chips.Testing sync issues is a bit boring stuff, unless you happen to buy a really good movie <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" /></blockquote>

Verification