From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106038] visual corruption and stuttery playback of VC-1 interlaced video with VAAPI and Polaris
Date: Fri, 13 Apr 2018 21:16:44 +0000 [thread overview]
Message-ID: <bug-106038-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106038
Bug ID: 106038
Summary: visual corruption and stuttery playback of VC-1
interlaced video with VAAPI and Polaris
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: tempel.julian@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
I initially reported the issue on the ffmpeg bugtracker:
https://trac.ffmpeg.org/ticket/7103
Since Intel works with VAAPI, it probably is an issue of Mesa's VAAPI driver
for Radeons. Please see the linked bugtracker entry for more details.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2378 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-04-13 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 21:16 bugzilla-daemon [this message]
2018-11-29 10:57 ` [Bug 106038] visual corruption and stuttery playback of VC-1 interlaced video with VAAPI and Polaris bugzilla-daemon
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-106038-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.