From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39308] New: mplayer -vo vdpau draws incorrectly on rv350
Date: Sun, 17 Jul 2011 10:19:18 -0700 (PDT) [thread overview]
Message-ID: <bug-39308-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=39308
Summary: mplayer -vo vdpau draws incorrectly on rv350
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: aaalmosss@gmail.com
Created an attachment (id=49215)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49215)
screenshot.png
As I understand it, simply running `mplayer -vo vdpau something.mpg` uses vdpau
as an output surface only, without any decoding done via vdpau (and adding -vc
ffmpeg12vdpau enables decoding). In this mode the video is drawn incorrectly,
as the attached screenshot shows.
Tried with this version (latest from debian-multimedia unstable):
MPlayer SVN-r33367 (C) 2000-2010 MPlayer Team
With libvdpau_softpipe.so mplayer segfaults in this mode. It doesn't segfault
when I enable decoding as well, in that case it renders into a smaller area,
just like r300.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-07-17 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 17:19 bugzilla-daemon [this message]
2011-09-17 11:01 ` [Bug 39308] mplayer -vo vdpau draws incorrectly on rv350 bugzilla-daemon
2011-09-21 14:18 ` bugzilla-daemon
2012-12-03 22:44 ` bugzilla-daemon
2012-12-03 23:50 ` bugzilla-daemon
2012-12-04 0:20 ` bugzilla-daemon
2012-12-04 11:10 ` bugzilla-daemon
2013-11-02 22:36 ` 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-39308-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.