http://bugs.freedesktop.org/show_bug.cgi?id=20505
--- Comment #11 from Alex Deucher <[email protected]> 2009-04-17 10:53:29 PST --- (In reply to comment #10) > OK. What about changing the default of the bicubic from auto to no, since it > has this limitation (that also confuses users) and it causes slowdown (and > also > I dislike its smoothing effect)? It's a tough call. A lot of people (myself included) prefer the bicubic filtering. I'm not sure what the best answer is. > > > > 2) with a small video (512x368) I noticed a 8% speedup (with mplayer > > > -benchmark > > > -quiet -nosound filename) no matter XV_SYNC, with a larger video > > > (1280x720) I > > > noticed a slowdown (over 61% and the video is jerkily), unless XV_SYNC is > > > disabled, where I get the same performance. But maybe this is a collateral > > > effect of the XV_SYNC that must paint all the frames and is noticeable > > > only > > > when doing benchmark (i.e. fps > video refresh)? > > > > > > > XV_VSYNC is unrelated to these changes. It will decrease performance in > > benchmark type scenarios because it stalls the engine while it waits for the > > current vline to pass beyond the video. It's used to avoid tearing. Turn > > it > > off for benchmarking. > > OK, thanks for clearing this. The strange thing, however, is that before the > latest xv merge I got the same performance with or without vsync enabled, > while > now I get the previous performance only with the vsync disabled and a large > slowdown with it enabled. Any chance you could bisect and find out the bad commit? None of the texvid rework touched the xv vsync code, so it's probably something prior. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
