From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108036] VA-API implementation reports support for unsupported endpoints Date: Mon, 24 Sep 2018 10:05:15 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0006871616==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 9AD64895F5 for ; Mon, 24 Sep 2018 10:05:15 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0006871616== Content-Type: multipart/alternative; boundary="15377835150.09C00c93.20465" Content-Transfer-Encoding: 7bit --15377835150.09C00c93.20465 Date: Mon, 24 Sep 2018 10:05:15 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108036 --- Comment #1 from Christian K=C3=B6nig = --- The problem is neither the driver nor the application, but rather the desig= n of VA-API. The hardware supports some high profile features (like CABAC), but unfortunately not all of them (like B-frames or MBAFF). Now the profile selects what the decoder needs to be able to do to handle a certain video, but doesn't tells you anything about the encoder except for selecting the encoding of the headers. We should support the encoding of the headers, so if an application selects high profile it actually gets better compression because of CABAC support. But if the application also tries to use B-frames it will get an invalid stream. Additional to that we currently have a firmware problem which corrupts all streams !=3D baseline. Could be that you are running into that one. Boyuang= is already investigating it and you could try to downgrade your firmware versi= on to test that. --=20 You are receiving this mail because: You are the assignee for the bug.= --15377835150.09C00c93.20465 Date: Mon, 24 Sep 2018 10:05:15 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 1 on bug 10803= 6 from Christian K=C3= =B6nig 
The problem is neither the driver nor the application, but rat=
her the design of
VA-API.

The hardware supports some high profile features (like CABAC), but
unfortunately not all of them (like B-frames or MBAFF).

Now the profile selects what the decoder needs to be able to do to handle a
certain video, but doesn't tells you anything about the encoder except for
selecting the encoding of the headers.

We should support the encoding of the headers, so if an application selects
high profile it actually gets better compression because of CABAC support.

But if the application also tries to use B-frames it will get an invalid
stream.

Additional to that we currently have a firmware problem which corrupts all
streams !=3D baseline. Could be that you are running into that one. Boyuang=
 is
already investigating it and you could try to downgrade your firmware versi=
on
to test that.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15377835150.09C00c93.20465-- --===============0006871616== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0006871616==--