<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [IVB SNA]4kx4k video can't decode with vaapi"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67210#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [IVB SNA]4kx4k video can't decode with vaapi"
href="https://bugs.freedesktop.org/show_bug.cgi?id=67210">bug 67210</a>
from <span class="vcard"><a class="email" href="mailto:gb.devel@gmail.com" title="Gwenole Beauchesne <gb.devel@gmail.com>"> <span class="fn">Gwenole Beauchesne</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=67210#c0">comment #0</a>)
<span class="quote">> System Environment:
> ----------------------------------------
> Platform: IVB
> Kernel_version: 3.10.0-rc2+
> Libdrm:
> (master)libdrm-2.4.46-2-gfea5408098c3c3057958e85ea9d7146f0b08749e
> Mesa: (master)190312949e8ce2c1dc884d4db5d6a44511666641
> Xserver:
> (master)xorg-server-1.14.99.1-137-g74469895e39fa38337f59edd64c4031ab9bb51d8
> Xf86_video_intel:(master)2.21.12-39-g2737aaab77cc6233826077b90d001fe45efc376c
> Cairo: (master)03c81d414d4edb710c91f96ddb7dbf73e5432583
> Libva: (staging)fbd3de9b22491689c6c3e5f1c305d7af76444e45
> Libva_intel_driver:
> (staging)1caf179b1425b13cacaa421c688c6df8369668c6
> OpenCL: (master)75b59f27c0bf403e97925e32b407b4fcb9bcb73f
> Kernel_unstable: (drm-intel-nightly)68c6cd3f1312965698b2af5bb08e15807ce9ae2d
>
> Bug info:
> ----------------------------------------
> 1 xinit&
> 2 mplayer -vo vaapi video.mp4</span >
This command does not involve hardware decoding through VA-API. So, as Haihao
mentioned further on, you are hitting and Xv issue.
The correct command to enable VA-API decoding is mplayer -vo vaapi -va vaapi
... but, it won't succeed on Ivybridge. Ivybridge can support 4K video but only
if a single dimension is 4K. i.e. 4K x 3K or 3K x 3K would work, but not 4K x
4K.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>