<div dir="ltr">Some additional info: according to "<a href="https://developer.gnome.org/clutter/1.12/running-clutter.html">running clutter</a>" page, other possible values for CLUTTER_VBLANK are "glx" and "dri". I just tested and "glx" also seems to work fine for me (NVidia driver with sync to vblank set to true).<div>
<br></div><div style>Regards,</div><div style><br></div><div style>Andre</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 21, 2013 at 1:10 PM, Andre Costa <span dir="ltr"><<a href="mailto:blueser@gmail.com" target="_blank">blueser@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Some follow up on this: found on <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1064095/comments/8" target="_blank">this thread</a> that setting<div>
<br></div><div>CLUTTER_VBLANK=none<br></div><div><br>
</div><div>makes it a *whole* lot better. In fact, AFAICS the problem is gone -- even if NVidia driver is still set to sync to vblank. Other performance problems which were also very noticeable on GNOME 3.6 (eg. moving windows around) are also gone.</div>
<div><br></div><div>Not sure if this is a GNOME or a NVidia bug (or both), will dive deeper into it later.</div><div><br></div><div>Regards,</div><div><br></div><div>Andre</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Feb 6, 2013 at 9:20 PM, Andre Costa <span dir="ltr"><<a href="mailto:blueser@gmail.com" target="_blank">blueser@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div>On Wed, Feb 6, 2013 at 5:03 PM, Joe Zeff <span dir="ltr"><<a href="mailto:joe@zeff.us" target="_blank">joe@zeff.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 02/06/2013 04:26 AM, Andre Costa wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Quite the contrary: this is a 8-core i7 desktop with a GeForce GT9800.<br>
It should handle any videos just fine ;-) (as it always has done until<br>
F18). There's clearly something wrong, I just don't know exactly what it<br>
is. CPU usage doesn't spike too much while watching videos<br>
</blockquote>
<br></div>
Have you tried running top in a terminal while this is going on? It can't hurt to know what process is using most of your CPU time when the videos slow down.</blockquote><div><br></div></div><div>Thks Joe, I'll try that. But it doesn't look like it's a high CPU usage issue, it looks as if video decoding is buggy.</div>
<div><br></div><div>I just tested getting rid of totem-mozplugin and installing gecko-mediaplayer (which uses MPlayer). Firefox is now able to play videos just fine, so it does seem to be some issue with Totem (or, more specifically, GStreamer?). However, gecko-mediaplayer doesn't get along well with Chrome, it simply can't load the plugin. So, either I switch back to Firefox or I use it only when I want to watch Quicktime movies.</div>
<div><br></div><div>Damn :-/</div></div></div></div>
</blockquote></div><br></div></div>
</blockquote></div><br></div>