Created attachment 109070 [details]
See attached photo
Video clip downloaded from https://www.youtube.com/watch?v=ceX18O9pvLs and played back with VLC
Original Youtube clip shows a lot more obvious tearing, probably due to Flash)
Clip is a sequence of frames with a white vertical bar, no motion blur or any other effects, as far as I can tell.
Perceptual effect in VLC is a slanted vertical bar, like "/" moving to the right or "\" moving to the left with a small piece at the top getting cut off and trailing the rest of the bar
Created attachment 109071 [details]
P.S. photo taken with cellphone camera. Obviously not perfect and may be a merge of several frames.. but the tearing is visible
Tearing is expected whenever the application does request vsync, or the application is submitting frames too slow and requests that the frame be shown immediately rather than wait for the next vblank.
So you're saying this is a VLC bug?
Probably. Not enough information is exposed at default debug levels to identify the culprit, but the spec is clear that if an application requests immediate display of a buffer and misses its target vblank/frame, that buffer should be presented immediately. Also note that if you are using a compositor, it can also prevent synchronisation of updates to vblank.
from VLC bug (https://trac.videolan.org/vlc/ticket/12752):
"""The application cannot do vertical sync. That´s something between the compositor or display manager and the display driver.
Without further infos, I have to assume the problem is not the player."""
So... who should I file a bug against?
If you have a compositor, then the compositor should be using vsync. If you don't have a compositor, the application is responsible for controlling vsync.
If you want to force vsync irrespective of the application/display manager/compositor, use Option "TearFree".
No compositor, just plain Xorg with XFCE desktop
You seem to be saying that the app could set vsync, but the VLC dev seems to be saying they can't..??
*** Bug 88472 has been marked as a duplicate of this bug. ***