Hello, I have a HP 6715b laptop with an ATI x1250 video card. I also use an external 22" monitor connected to the VGA port of my laptop. I have set the screen resolution to 1920x1080 in Gnome Display Settings. The driver I use is the ATI one from the Ubuntu repositories. When I play fullscreen videos with VLC, SMplayer or else, without having Compiz running, it just works flawlessly, without seeming to freeze to calculate the image. But when Compiz is on, fullscreen videos get a lot slower. It is impossible to watch a movie this way. Another thing is that the desktop effects get really slow when it comes to fullscreen windows: menus scroll down rather slowly, the windows "close effects" is not smooth. I have reinstalled Karmic Koala in its RC version and that problem isn't going away... My xorg.conf file is the original one, I have not tweaked it in any way... Hope anyone else could reproduce this bug! Thanks. Chris
Created attachment 31236 [details] [review] Xorg log Added Xorg log.
I can confirm that Flash videos are choppy, no matter Compiz is on or not, but only when they are in full-screen mode in my case. Well, I have made several reinstalls since last week, and the problem won't disappear: when Compiz is activated, fullscreen videos are really slow in VLC, SMPlayer, etc. Compix effects are really slow in larger windows. However I noticed the following thing: if I set the procesor frequency to max through the Gnome req scaling monitor (1800Mhz) while Compiz is on, videos and effects are a lot faster (except for Flash vids). Don't know if this means anything, but it seems to me that the current driver is not really optimized to use composite with my X1250 card... and that it needs the processor to do the calculating job. Correct me if I'm wrong :o) I have the current values in glxgears: >>> with procesor at 800Mhz cristobalin@chris-karmic:~$ glxgears 1518 frames in 5.0 seconds = 303.546 FPS 1367 frames in 5.0 seconds = 273.295 FPS 1455 frames in 5.0 seconds = 290.883 FPS 1458 frames in 5.0 seconds = 291.383 FPS 1427 frames in 5.0 seconds = 285.288 FPS >>> with procesor at 1.80Ghz cristobalin@chris-karmic:~$ glxgears 2958 frames in 5.0 seconds = 591.518 FPS 2919 frames in 5.0 seconds = 583.795 FPS 2847 frames in 5.0 seconds = 569.261 FPS 2940 frames in 5.0 seconds = 587.825 FPS One more remark: I have activated the xorg-edgers repositories, so all of the values come from tests made with the newest releases. If it helps, I have attached my Xorg.0.log. i have not attached my xorg.conf file because I have not tweaked it. Thanks! Chris
The proprietary flash plugin does not currently support any acceleration on the open source drivers.
(In reply to comment #3) > The proprietary flash plugin does not currently support any acceleration on the > open source drivers. > Just to clarify things... this is NOT a flash problem. *Every* video is choppy (regardless of processor frequency). In fullscreen mode the problem becomes more obvious. First time I realized the problem, was around august, when I updated my Xorg drivers straight from upstream git (due to flickering problem with X1250/RS690 chipset; I installed the Xorg edgers PPA). With older Xorg edgers PPAs videos ran seamlessly and smoothly. Only in newer PPAs this new problem occured. And now this problem is built-in in Ubuntu 9.10 :-)
Does disabling bicubic filtering help? xvattr -a XV_BICUBIC -v 0
Hi Alex, As Jens said before, the problem affects fullscreen videos and also the effects in fullscreen windows (such as opening/closing, maximizing...). Everything gets a lot more slower. However if the CPU freq is set to its highest value (1.80GHz for my laptop), I notice that videos and effects speed up but they are still choppy. I'll do what you suggest about deactivating the bicubic filter tomorrow, as I currently have no access to my home pc. Sorry about the second comment I posted, I agree it was a bit confusing just copying and pasting from Launchpad. Btw, the lauchpad bug number is 460505. Thanks.
Xv only accelerates scaling and colorspace conversion. Video decode is still done is software so that part of the pipeline will be dependent on your CPU speed.
Alex, About your question in comment nº5, using xvattr -a XV_BICUBIC -v 0 does help fullscreen videos be faster when Compiz is on, but it is really not as smooth as it should be and as it is when Compiz is off. Regarding the Compiz effects, setting the bicubic filter to 0 does not seem to have any effect. Jens, could you please confirm that? :o) Thanxxxx Chris
Is 'unredirect fullscreen windows' enabled in the compiz configuration?
(In reply to comment #9) > Is 'unredirect fullscreen windows' enabled in the compiz configuration? > Hello, The option "Unredirect fullscreen windows" was disabled. I have activated it, and now fullscreen videos are at full speed AS LONG AS I don't move the mouse if I'm under VLC, SMPlayer, etc... If I move the mouse, the button bar appears and everything goes through composite again... and get slow. It's a nice workaround, though, but really I'd rather stick to "no desktop effects" for the moment, as the Compiz effects are slow in big windows. Furthermore if I have desktop effects activated, I have hard times moving windows that take more than a quarter of my 21.5" screen... Many thanks for the trick. I'm aware that the open-source ati driver is still not complete, but is this something that developers have been notified about? Cheers, Chris...
lefteyexl@gmail.com, Ubuntu 9.10 reached EOL on April 30, 2011. For more on this, please see https://wiki.ubuntu.com/Releases . If this is reproducible on a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.