From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69889] New: WMV3/VC-1 garbled output with VDPAU
Date: Fri, 27 Sep 2013 18:29:03 +0000 [thread overview]
Message-ID: <bug-69889-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69889
Priority: medium
Bug ID: 69889
Assignee: dri-devel@lists.freedesktop.org
Summary: WMV3/VC-1 garbled output with VDPAU
Severity: normal
Classification: Unclassified
OS: All
Reporter: pierre-bugzilla@ossman.eu
Hardware: Other
Status: NEW
Version: 9.2
Component: Drivers/DRI/R600
Product: Mesa
I've been trying out the new VDPAU support for Radeon cards, and it works fine
except for two issues:
1. Occasional system lockup (haven't found what triggers this yet)
2. No WMV3/VC-1 files will play whatsoever.
For every file I get the same thing, mostly black with a few lines of
green/purple junk at the top.
mesa-libGL-9.2-1.20130919.fc19.x86_64
libvdpau-0.7-1.fc19.x86_64
kernel-3.11.1-200.fc19.x86_64
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Turks PRO [Radeon HD 6570/7570] [1002:6759]
Is it possible to get the driver to stop claiming VC-1 support so that I can
enjoy the H.264 acceleration until a fix is in place?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2520 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 reply other threads:[~2013-09-27 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 18:29 bugzilla-daemon [this message]
2013-09-27 18:50 ` [Bug 69889] WMV3/VC-1 garbled output with VDPAU 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-69889-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.