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 16:09:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1790944464==" 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 0A21C892CF for ; Mon, 24 Sep 2018 16:09:35 +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 --===============1790944464== Content-Type: multipart/alternative; boundary="15378053740.37cC50c.6300" Content-Transfer-Encoding: 7bit --15378053740.37cC50c.6300 Date: Mon, 24 Sep 2018 16:09:34 +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 #3 from Kurt Kartaltepe --- > The hardware supports some high profile features (like CABAC), but > unfortunately not all of them (like B-frames or MBAFF). >=20 > 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. >=20 > We should support the encoding of the headers, so if an application selec= ts > high profile it actually gets better compression because of CABAC support. >=20 > But if the application also tries to use B-frames it will get an invalid > stream. Yes, the issue is that valid settings produce a stream that is invalid. Personally I would be more than ok if the resultant stream on high was with= in constrained baseline specs as long as it returned a valid stream. Because hardware encoders are such black boxes I care very little for the settings i cannot control (such as exact compression techniques) and expect= the ones i can to work. --=20 You are receiving this mail because: You are the assignee for the bug.= --15378053740.37cC50c.6300 Date: Mon, 24 Sep 2018 16:09:34 +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 # 3 on bug 10803= 6 from Kurt Kartaltepe
> The hardware supports some high profile features=
 (like CABAC), but
> unfortunately not all of them (like B-frames or MBAFF).
>=20
> Now the profile selects what the decoder needs to be able to do to han=
dle a
> certain video, but doesn't tells you anything about the encoder except=
 for
> selecting the encoding of the headers.
>=20
> We should support the encoding of the headers, so if an application se=
lects
> high profile it actually gets better compression because of CABAC supp=
ort.
>=20
> But if the application also tries to use B-frames it will get an inval=
id
> stream.

Yes, the issue is that valid settings produce a stream that is invalid.
Personally I would be more than ok if the resultant stream on high was with=
in
constrained baseline specs as long as it returned a valid stream.

 Because hardware encoders are such black boxes I care very little for the
settings i cannot control (such as exact compression techniques) and expect=
 the
ones i can to work.


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