From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93760] radeonsi vaapi mpeg2 decode slightly corrupt or asserts.
Date: Mon, 16 Jan 2017 14:48:37 +0000 [thread overview]
Message-ID: <bug-93760-502-loYbKzS5n6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93760-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 766 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93760
--- Comment #6 from Nayan Deshmukh <nayan26deshmukh@gmail.com> ---
(In reply to Christian König from comment #3)
> Sorry totally missed that bug.
>
> The problem is most likely that GStreamer sends multiple slices in one
> request to VA-API and we can't handle that in the state tracker.
>
> Should be easy to fix actually, but we need somebody to look into it and
> reproduce this.
>
What changes do we need to make to handle multiple slices?
The video plays fine with vdpau. Can you point me to the code where vdpau
handles multiple slices as both of them share similar code path.
> Another task for Nayan maybe?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1691 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:[~2017-01-16 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 16:41 [Bug 93760] radeonsi vaapi mpeg2 decode slightly corrupt or asserts bugzilla-daemon
2016-01-18 16:42 ` bugzilla-daemon
2017-01-13 15:16 ` bugzilla-daemon
2017-01-13 16:17 ` bugzilla-daemon
2017-01-13 17:34 ` bugzilla-daemon
2017-01-13 17:50 ` bugzilla-daemon
2017-01-13 17:51 ` bugzilla-daemon
2017-01-16 14:48 ` bugzilla-daemon [this message]
2017-01-16 15:11 ` bugzilla-daemon
2017-01-17 6:05 ` 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-93760-502-loYbKzS5n6@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;
as well as URLs for NNTP newsgroup(s).