[SOLVED] Screen tearing with VLC only

Daedra · 08-27-2014, 02:21 PM

Hi guys,

I haven't been very active on the forums lately, and with Slackware in general because of school. But I was trying to watch a video with VLC last night and I was getting awful screen tearing. I investigated further and I have found that this is only happening with VLC. Screensavers, games, compiz, etc all work fine. I have tried KDE, XFCE, and Blackbox and it happens with all the DE and WM I try. I am using Alien Bob's VLC build and the nivdia binary drivers.

Any clues/help is appreciated thanks.

GazL · 08-27-2014, 02:29 PM

What version of the nvidia blob are you using? I found that any later than 320.xx result in 'xv' video tearing. I decided to go back to the 304.xx drivers which don't tear.

I wasn't using vlc though. it was "mplayer -vo xv" that had problems.

Daedra · 08-27-2014, 02:31 PM

Hey GazL

, I'm currently using 340.24. I'll roll back later today and see if that fixes it. I have a GTX-460 which is supported in both the legacy driver and the current driver. I wonder if the legacy driver also has this problem.

GazL · 08-27-2014, 02:41 PM

I was using 319.82 happily, but something they did after that broke things so I went back to the legacy driver even though my card is technically still supported by the newer ones.

Another thing you might want to try is to see if you can use another sort of video output. I don't know about vlc, but mplayer and xine both let you choose between 'xv', 'gl', 'x11' and some others.

Daedra · 08-27-2014, 04:36 PM

I just installed the 304 legacy driver at SBo.org and so far its fixed. I'll run some more test to confirm but I think that got it. Thanks again.

Just out of curiosity though, do you know why COMPAT32 is not supported with the legacy driver?

GazL · 08-27-2014, 07:37 PM

I have both lib and lib64 libraries, but I used the NIVIDIA*run installer, not the slackbuild.

Code:

gazl@ws1:~$ locate libGL
/usr/lib64/libGL.so
/usr/lib64/libGLEW.so.1.9
/usr/lib64/libGLEW.so
/usr/lib64/libGL.so.304.123
/usr/lib64/libGL.so.1
/usr/lib64/libGLU.la
/usr/lib64/libGLU.so.1.3.1
/usr/lib64/libGLU.so
/usr/lib64/libGLEW.so.1.9.0
/usr/lib64/libGLEW.a
/usr/lib64/libGL.la
/usr/lib64/libGLU.so.1
/usr/lib/libGL.so
/usr/lib/libGL.so.304.123
/usr/lib/libGL.so.1
/usr/lib/libGL.la

but then I don't run multilib anyway, so they're just taking up space.

There's no libEGL though... I think NVIDIA added that later on than 304.xx!

Daedra · 08-27-2014, 08:26 PM

Ok so the Nvidia-Legacy driver did fix the problem, but upon further investigation I did find a fix for the current 340 driver. Adding these lines to your xorg.conf fixes the problem also...

Option "nvidiaXineramaInfoOrder" "DFP-1"
Option "metamodes" "nvidia-auto-select +0+0{ ForceFullCompositionPipeline = On }"
#Option "metamodes" "nvidia-auto-select +0+0"

I guess if the 2nd option does not work, then try the 3rd. However this worked for me. I am now running the 340 driver again.