Hi, On Fri, 2007-09-21 at 10:45 +0200, Thomas Vander Stichele wrote: > Hi, > > > > Seems like you have vsync issues? Are you using the free or proprietary > > > drivers? Pigment supports vsync for the proprietary drivers, right Loïc > > > (Molinari) ? :) > > > > I'm using the proprietary nvidia drivers and have the "Sync to VBlank" > > options checked for "Video Texture Adaptor," "Open GL Settings > > > Sync to VBlank" and "Video Blitter Adaptor" in nvidia-settings. The > > video doesn't tear or anything like that, just gets a bit jerky. > > I have an nvidia as well, and set some of these options. While they > remove tearing, they also increase the CPU load a lot, which would > possibly cause the jerkiness you're seeing. > > Can you: > > a) check your CPU use somehow during playback > b) turn off some of the vblank options and see if it reduces CPU, and > fixes the jerkiness ?
The rendering is done by the OpenGL plugin of Pigment which supports different options regarding vertical syncing. You should have VSync activated by default without tweaking the different options in your ~/.nvidia-settings-rc. Here is a summary of the vertical syncing decision hierarchy in Elisa. First, the plugin tries to guess the best method supported by the hardware it's running on. But this automatic choice made by Pigment can be overloaded, you can for instance choose the VSync method defining the PGM_GL_VBLANK variable in your environment. There are 3 choices: 0- disable all attempts to synchronize to the VBlank. 1- use the GLX_SGI_video_sync extension to synchronize to the VBlank. 2- use the GLX_SGI_swap_control extension to synchronize to the VBlank. The other thing to know is there are environment variables and tools that can overload application decision. The environment variables are __GL_SYNC_TO_VBLANK which is used in the NVIDIA proprietary driver, and vblank_mode which is used by the DRI open source driver architecture. The tool for the NVIDIA proprietary driver is nvidia-settings which write in the ~/.nvidia-settings-rc file, and for the DRI drivers it's driconf which write in the ~/.drirc file. Hope that helps, regards. -- Loïc Molinari <[EMAIL PROTECTED]>
