All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92729] VDPAU: Maybe support H264_CONSTRAINED_BASELINE
Date: Thu, 29 Oct 2015 18:48:35 +0000	[thread overview]
Message-ID: <bug-92729-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2196 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92729

            Bug ID: 92729
           Summary: VDPAU: Maybe support H264_CONSTRAINED_BASELINE
           Product: Mesa
           Version: 11.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: andreaskem@web.de
        QA Contact: dri-devel@lists.freedesktop.org

Hi,

I am not sure if this is the proper place to report this, so feel free to send
me somewhere else and I apologize in advance.

I am on the Mesa 11.0.4 r600 driver with the following device:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Wrestler [Radeon HD 7340]
and Xorg 1.17.3. (Arch Linux with testing repository enabled, everything
up-to-date).

vdpauinfo reports (see attachment) that the H.264 profiles H264_BASELINE,
H264_MAIN, and H264_HIGH are supported for VDPAU hardware acceleration.
However, H264_CONSTRAINED_BASELINE is marked "not supported". Now, if the
Wikipedia article about H.264 profiles is to be believed [1], the constrained
profile only needs a "subset of features that are in common between the
Baseline, Main, and High Profiles." Consequently, I would expect
H264_CONSTRAINED_BASELINE to be supported, as well.

See also the bug report I filed for mpv a few weeks ago [2].

Moreover, H264_PROGRESSIVE_HIGH and H264_CONSTRAINED_HIGH seem to be "Similar
to the High profile, but without support of field coding features." and
"Similar to the Progressive High profile, but without support of B
(bi-predictive) slices." respectively. However, vdpauinfo reports "not
supported" for both.

As I am writing this, I also notice that VC1_ADVANCED is supported, but
VC1_MAIN and VC1_SIMPLE are not. Reading [3], I would expect the same reasoning
to apply.

Is there something I am missing?

[1] https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Profiles
[2] https://github.com/mpv-player/mpv/issues/2347
[3] https://en.wikipedia.org/wiki/VC-1#Profiles

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3732 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-10-29 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 18:48 bugzilla-daemon [this message]
2015-10-29 18:49 ` [Bug 92729] VDPAU: Maybe support H264_CONSTRAINED_BASELINE bugzilla-daemon
2017-05-28 11:34 ` 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-92729-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.