Hello! I'm on fedora 20 with Intel® Haswell Mobile graphics (HD 4600, I suppose). When I play video the screen is chopped. How to enable vertical synchronization with Intel graphics?
Hello! I'm on fedora 20 with Intel® Haswell Mobile graphics (HD 4600, I suppose). When I play video the screen is chopped. How to enable vertical synchronization with Intel graphics?
First off, you should determine if vblanking is turned off or not. A good way to do that is to run the "glxgears" command from a terminal. When the glxgears box comes up with the spinnibg gears, put your mouse curser inside the window, and watch the output in the terminal.
If you're getting something like this:
..then vblanking is turned off. If FPS rate is reported at something very close to 60fps, or whatever your monitor vertical refresh rate actually is, then vblanking is already on. Some programs may actually override the current vblank setting.Code:34864 frames in 5.0 seconds = 6972.768 FPS 37210 frames in 5.0 seconds = 7441.921 FPS 37505 frames in 5.0 seconds = 7500.925 FPS
On my laptop with Intel(R) Core(TM) i5-3210M CPU (IvyBridge), vlanking was on by default so I turned it off with an entry in my ~/.bash_profile file.
If you find vblank if on by default and you want it off, then you can add the same line, but use =1 instead of =0 to turn it on. You can also issue the command at the command line just ahead of launching a program to test things. I think something like this:Code:# User specific environment and startup programs export vblank_mode=0
You could try this. In a terminal:Code:vlblank_mode=1 vlc
Code:export vblank_mode=1
Well, now I'm a bit puzzled as I reset my vblank_mode to 1 (on) to test and glxgears is still reporting the higher frame rates instead of something at the laptops lcd screen refresh rate. Maybe that needed a reboot or re-login.
Thank you for detailed answer. It seems for me that vblank is on (have 60 fps). But why videos are chopped in vlc and totem? Will try running vlc from terminal with vblank_mode=1 later and report the result.![]()
Well, since vblank_mode on your system is already ON, turning it ON again using the environment variable shouldn't make any change. Try turning it OFF (=0) and see if anything changes.Will try running vlc from terminal with vblank_mode=1
And I discovered this morning why I couldn't get my vblank_mode to actually use the ON mode by resetting the vblank_mode variable. I had a file named drirc sitting in the top directory of my $HOME (since moved elsewhere).
It was overriding the environment variable setting, which now explains the warning message glxgears was giving me.Code:$ cat Documents/Files/Fixes/drirc <driconf> <device screen="0" driver="i915"> <application name="all"> <!-- Always synchronize with vertical refresh to avoid tearing --> <option name="vblank_mode" value="0"/> </application> </device> </driconf>
chopped video in both cases with vblank on and offstrange
Then I would have to say that vblank, on or off, isn't the cause of the choppy video.
Sent from my Nexus 7
Video playback is not controlled by the VAAPI thing?
https://01.org/linuxgraphics/community
http://freedesktop.org/wiki/Software/vaapi/
http://www.phoronix.com/scan.php?pag...00_linux&num=1
Model and driver would be useful to lookup stuff.
lspci -k | grep -iA 3 vga
Thanks dobbi. Never heard about VAAPI before (used nvidia graphics before). Here is command output:
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Toshiba America Info Systems Device fa47
Kernel driver in use: i915
Thanks dobby one more time! I fixed it in vlc by adding to /etc/environment:
CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True
Are you sure about the line?I haven't found any up-to-date info on the parameter. Also arch wiki on gnome recommends just the first line.Code:CLUTTER_VBLANK
Some general info:
For older generation of Intel graphics this bollocks started around January 2013. The clutter_paint workaround didn't restore the previosuly excellent, smooth animations. It was supposed to be fixed with the advent of Mesa 10 and DRI3 (Xorg 1.15) but this didn't happen (tested on more fresh distros). So don't hold your breath.
We're most probably stuck with it until Wayland-enabled Gnome gets released (~3.14) because apparently Intel and Gnome guys have little regard for end user experience.