<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations" href="https://bugs.freedesktop.org/show_bug.cgi?id=76564#c47">Comment # 47</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations" href="https://bugs.freedesktop.org/show_bug.cgi?id=76564">bug 76564</a> from <a class="email" href="mailto:fernetmenta@online.de" title="Rainer Hochecker <fernetmenta@online.de>"> Rainer Hochecker</a> <pre>(In reply to <a href="show_bug.cgi?id=76564#c41">comment #41</a>) > (In reply to <a href="show_bug.cgi?id=76564#c40">comment #40</a>) > > If you set "sync playback to display" in XBMC, an inaccurate clock has no > > impact on dropped or skipped frames. Suppose you only have a 24Hz mode and > > play material which is 23.976. It would slightly speed up playback: every > > vblank interval a frame is rendered. > > If you observe skipped frames, the render thread may have been blocked too > > long or a vertical retrace was missed. > > Hello FernetMenta, > > Thanks for commenting, as you are one of the experts on this subject in XBMC. > > "sync playback to display" is definately enabled on my system and still I am > seeing skipped or missed frames depending on if the clock is too slow or too > fast, respectively. > Also, the patches from Christian already proved that a clock that is closer > to the television display clock DOES have an influence on skipping/missing > frames. If the clock had no impact there wouldn't be a problem in the first > place. > > The posted xrandr logs also show my television does have a 23.976 mode. Again, a wrong speed does NOT have direct influence on dropped or skipped frames. If you see a some kind of relationship you have to look for the missing piece.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>