From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108937] [radeonsi, RX480] VAAPI H.264 decoder produces garbage on YouTube in Chromium with h264ify
Date: Tue, 04 Dec 2018 09:25:13 +0000 [thread overview]
Message-ID: <bug-108937-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1566 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108937
Bug ID: 108937
Summary: [radeonsi, RX480] VAAPI H.264 decoder produces garbage
on YouTube in Chromium with h264ify
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: kode54@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 142707
--> https://bugs.freedesktop.org/attachment.cgi?id=142707&action=edit
Screen shot of YouTube video in Chromium, artifacts
I am attempting to play H.264 video in Chromium, using a fork of the current
beta (v71) that has a VAAPI patch applied. When playing the following video:
https://www.youtube.com/watch?v=oiSn2JuDQSc
I get the resulting video output, attached.
Using:
Description: Ubuntu 18.10
Release: 18.10
chromium-browser 71.0.3578.62-0ubuntu1~ppa1~18.10.1
mesa-va-drivers 19.0~git1812040730.bacf84~oibaf~c
It should be possible to follow those to the patches used, but I don't think
that the Chromium patch is responsible for "misusing" VA-API, so much as the
radeonsi VA-API driver being broken in some way.
The artifact simply goes away if I disable h264ify, since it switches to VP9,
and thus software decoding.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3222 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 reply other threads:[~2018-12-04 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 9:25 bugzilla-daemon [this message]
2018-12-04 9:27 ` [Bug 108937] [radeonsi, RX480] VAAPI H.264 decoder produces garbage on YouTube in Chromium with h264ify bugzilla-daemon
2018-12-04 20:53 ` bugzilla-daemon
2018-12-05 0:26 ` bugzilla-daemon
2018-12-05 7:38 ` bugzilla-daemon
2018-12-05 7:39 ` bugzilla-daemon
2018-12-05 7:41 ` bugzilla-daemon
2018-12-05 8:45 ` bugzilla-daemon
2018-12-05 8:52 ` 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-108937-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox