From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108036] VA-API implementation reports support for unsupported endpoints
Date: Mon, 24 Sep 2018 16:09:35 +0000 [thread overview]
Message-ID: <bug-108036-502-KytFUsy4yi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108036-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1181 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108036
--- Comment #3 from Kurt Kartaltepe <notkurufu@cock.li> ---
> 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.
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 within
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.
[-- Attachment #1.2: Type: text/html, Size: 2057 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-24 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 3:05 [Bug 108036] VA-API implementation reports support for unsupported endpoints bugzilla-daemon
2018-09-24 10:05 ` bugzilla-daemon
2018-09-24 15:44 ` bugzilla-daemon
2018-09-24 16:09 ` bugzilla-daemon [this message]
2019-09-25 18:09 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108036-502-KytFUsy4yi@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox