On Mon, Apr 2, 2012 at 08:30, Oliver Seitz wrote:
>
> Video tearing in windows is a known issue on SandyBridge
>>
>
> And also on IvyBridge, I presume. Then I'll try to be patient until
> there's a new implementation of vsynced update logic in the driver :-)
>
There are some improvements on the
Video tearing in windows is a known issue on SandyBridge
And also on IvyBridge, I presume. Then I'll try to be patient until
there's a new implementation of vsynced update logic in the driver :-)
Thanks for the explanations and all the good work!
Kiste
_
On Mon, Apr 2, 2012 at 12:40, Oliver Seitz wrote:
>
>> The only workaround is [...] to only use fullscreen DRI video
>> applications
>>
>> (OpenGL or libva decoders) that use SwapBuffers.
>
>
> Yes, works perfectly while only one screen is connected. That means, this
> definition of "fullscreen"
The only workaround is [...] to only use fullscreen DRI video applications
(OpenGL or libva decoders) that use SwapBuffers.
Yes, works perfectly while only one screen is connected. That means,
this definition of "fullscreen" is "the whole framebuffer", and not "the
content of one display"?
On Sat, 31 Mar 2012 19:52:09 +0200, Oliver Seitz wrote:
[snip]
> If, however, two screens are next to or on top of each other, playing
> video on one of the screens can show some tearing. It is not always seen
> with normal video, a special test pattern is helpful. Also, it does only
> tear in
Hello,
I'm running vaapi-mplayer on debian wheezy, which has fairly up-to-date
intel drivers. (Right now i965-va-driver is outdated, so I use the sid
package of that.)
I do not have any window manager, only X and an xterm. (Really, not even
twm. It is only a test installation.)
Both output
