Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 608351" data-attributes="member: 83973">From the render stats it looks like you are using ReClock to play 24fps material at 25/50fps (I do this too), so I think the problem is that the frame rate ratio detection is deciding to turn off the vsync correction sometimes.In the next version I'll widen the detection limits (it's currently within 2%, I'll take it to maybe 4%) to see if that helps. I don't want to enable it always because it will probably make frame drops/stuttering worse when the refresh rates don't match.mrmojo666 - it uses extra CPU &amp; rendering time to calculate and draw the stats on screen, so this might cause problems if the CPU is already heavily loaded. When the render stats are not displayed I also disable some of the internal stats calculations as well.TonyThe jumpy yellow line (which is basically the raster position when PresentImage(...) returns) is because it's hovering around the end/beginning of the raster - the 'SOP line:' number is the scanline when 'painting' starts after the vsync correction delay, 'EOP line:' is the scanline when it finishes - when PresentImage() returns.Tony</blockquote>

[QUOTE="Owlsroost, post: 608351, member: 83973"] From the render stats it looks like you are using ReClock to play 24fps material at 25/50fps (I do this too), so I think the problem is that the frame rate ratio detection is deciding to turn off the vsync correction sometimes. In the next version I'll widen the detection limits (it's currently within 2%, I'll take it to maybe 4%) to see if that helps. I don't want to enable it always because it will probably make frame drops/stuttering worse when the refresh rates don't match. mrmojo666 - it uses extra CPU & rendering time to calculate and draw the stats on screen, so this might cause problems if the CPU is already heavily loaded. When the render stats are not displayed I also disable some of the internal stats calculations as well. Tony The jumpy yellow line (which is basically the raster position when PresentImage(...) returns) is because it's hovering around the end/beginning of the raster - the 'SOP line:' number is the scanline when 'painting' starts after the vsync correction delay, 'EOP line:' is the scanline when it finishes - when PresentImage() returns. Tony [/QUOTE]

Verification