After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673526 - cluttershare and cluttersink render choppy video with fglrx driver
cluttershare and cluttersink render choppy video with fglrx driver
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-gl
0.10.x
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-04 18:31 UTC by david
Modified: 2012-04-10 14:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description david 2012-04-04 18:31:02 UTC 
I've reported bug here https://bugzilla.gnome.org/show_bug.cgi?id=673383
believing that it is a bug that has to do something with clutter and clutter-gst.

But, I've discovered same result with cluttershare example that, I believe, is same way how cluttersink functions.

I've tested this on three ATI GPU machines, and discovered that on first two I had same result and on the last everything worked fine until I installed fglrx drivers - so I asume that it has to do something with fglrx and gst-gl plugins incompatibility bug.

glimagesink works fine with that setup.

Image displayed with cluttershare or cluttersink is somehow skipping frames, like hardware is week, but it is not.

I've used latest stable releases of everything.

If you need any more information, please ask. I can even provide you with hardware to solve this issue.
Comment 1 david 2012-04-04 22:22:59 UTC 
In case anyone is interested, I've found a workaroud that gives better performance:

1. add this to /etc/enviroment:

export CLUTTER_VBLANK=none


2. in amdcccle disable vsync


3. reboot
Comment 2 Julien Isorce 2012-04-10 14:52:15 UTC 
(In reply to comment #0)
> I've reported bug here https://bugzilla.gnome.org/show_bug.cgi?id=673383

Let's solve bug #673383 first