From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105277] ffmpeg using radeonsi vaapi on Polaris21 RX560 creates h264 steams not playable by gstreamer & hw players
Date: Wed, 28 Feb 2018 02:07:27 +0000 [thread overview]
Message-ID: <bug-105277-502-aZ2bvqS3Ua@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105277-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 623 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105277
--- Comment #7 from Luke McKee <hojuruku@gmail.com> ---
Final note before I wash my hands of this matter and leave it to the devs to
fix.
I also just tried this with the new main / high profile options and cabac
enabled that is now available in the more bleeding edge amd kernels / mesa /
libva / ffmpeg.
The breakage on the hardware player and gstermer qtdemux still applies.
new h265 vaapi support is dangerous too.
https://bugs.freedesktop.org/show_bug.cgi?id=103953#c7
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1679 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-02-28 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 20:20 [Bug 105277] ffmpeg using radeonsi vaapi on Polaris21 RX560 creates h264 steams not playable by gstreamer & hw players bugzilla-daemon
2018-02-27 20:28 ` bugzilla-daemon
2018-02-27 20:48 ` bugzilla-daemon
2018-02-27 20:56 ` bugzilla-daemon
2018-02-27 21:04 ` bugzilla-daemon
2018-02-27 21:36 ` bugzilla-daemon
2018-02-27 21:40 ` bugzilla-daemon
2018-02-27 22:53 ` bugzilla-daemon
2018-02-28 2:07 ` bugzilla-daemon [this message]
2019-09-25 18:03 ` 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-105277-502-aZ2bvqS3Ua@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.