From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71796] Hardware assisted (VDPAU) decoding of MPEG-2 causes GPU lockup - Radeon HD6950
Date: Sun, 08 Dec 2013 21:15:52 +0000 [thread overview]
Message-ID: <bug-71796-502-L9jS9MnovB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71796-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71796
--- Comment #12 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to comment #11)
> I had some dvds laying around and those had no issues and downloaded other
> mpeg2 clips too and those too worked fine with vdpau decoding, but with this
> particular clip vdpau messed stuff up badly.
>
> I found a link for the clip here:
> https://github.com/xbmc/xbmc/pull/399
>
> This is the direct download link, its a mpeg2 clip, around 20MB:
> http://www.mediafire.com/?4dvvwj5aw2esv49
I think this file is exceptional and so it not working is probably unrelated to
whatever issue others are seeing.
It doesn't work because vdpau doesn't support field coded mpeg2. I guess
because it is very rare - other than compliance streams this is the first one
I've seen in the wild, and given it's mpeg2 in mkv with ac3 and the cartoon
content is a mix of progressive and interlaced (maybe from telecine and frame
rate converted) I don't know if it's an amateur creation or something "real".
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2155 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
next prev parent reply other threads:[~2013-12-08 21:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 16:27 [Bug 71796] New: Hardware assisted (VDPAU) decoding of MPEG-2 causes GPU lockup - Radeon HD6950 bugzilla-daemon
2013-11-22 19:13 ` [Bug 71796] " bugzilla-daemon
2013-11-22 19:17 ` bugzilla-daemon
2013-11-23 13:35 ` bugzilla-daemon
2013-11-23 13:36 ` bugzilla-daemon
2013-11-24 1:13 ` bugzilla-daemon
2013-11-24 1:18 ` bugzilla-daemon
2013-11-24 1:20 ` bugzilla-daemon
2013-11-28 15:39 ` bugzilla-daemon
2013-12-02 2:57 ` bugzilla-daemon
2013-12-06 13:15 ` bugzilla-daemon
2013-12-08 15:52 ` bugzilla-daemon
2013-12-08 19:15 ` bugzilla-daemon
2013-12-08 21:15 ` bugzilla-daemon [this message]
2013-12-08 21:24 ` bugzilla-daemon
2013-12-08 21:41 ` bugzilla-daemon
2013-12-08 21:56 ` bugzilla-daemon
2013-12-15 17:54 ` bugzilla-daemon
2019-09-18 19:11 ` 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-71796-502-L9jS9MnovB@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