From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71812] VDPAU: MPEG-4 ASP Garbling/Corruption
Date: Wed, 16 Jul 2014 10:30:36 +0000 [thread overview]
Message-ID: <bug-71812-502-nijmNTo182@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71812-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2192 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71812
--- Comment #10 from Fabrice Bellet <fabrice@bellet.info> ---
Hi!
I also see the same behaviour. I tested it with mplayer -vo vdpau -vc
ffodivxvdpau, using both vdpau decoder render and vdpau presentation
functions. I tested it with vlc --avcodec-hw=vdpau, using decoder render and
video surface get bits functions, and finally with gstreamer vaapidecode and
vaapisink/ximagesink. (using radeonsi/uvd). All these cases have in common the
use of the vdpau decoder render functions. Tested with upstream mesa/xorg, in a
fedora 20 x86_64, [AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 250E].
I made some traces at the libvdpau level (VDPAU_TRACE env vars), that I can
provide if needed. They don't seem to present major differences between
situations with and without corruption. I tried to serialize the vdpau calls
with a mutex without more success, I played with the number of surfaces too, no
difference. libefence didn't help.
I have the feeling that some uninitialized stuff is passed to the hardware
decoder, because I would say the problem probalistically happens more
frequently after a fresh boot. The initial frame is _sometimes_ garbled with
some bad colors (chroma planes ?), and this corruption progates to consecutive
frames, due to the way mpeg compression works. I also have the feeling that
this bug occurs more frequently with gstreamer-vaapi/vdpau-driver than vlc and
mplayer, because of the multithreaded nature of gst, where decoding operation
and rendering operations are less regularily scheduled : in gst, a burst of 4
or 5 vdpau decode render operations can happen on different surfaces, before
the generated data is consumed by the vdpau presentation mode.
Another way this problem occurs is by corrupting other parts of the display,
not limited to the X11 window area where the rendering should happen, like
small black rectangles appearing randomly on the screen. In another case, I
noticed that part of my gnome-terminal transparent background looses some small
rectangular areas that become "more" transparent than they should be.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2974 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:[~2014-07-16 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 21:27 [Bug 71812] New: VDPAU: MPEG-4 ASP Garbling/Corruption bugzilla-daemon
2013-11-19 21:27 ` [Bug 71812] " bugzilla-daemon
2013-11-19 21:28 ` bugzilla-daemon
2013-11-19 21:28 ` bugzilla-daemon
2013-11-19 21:29 ` bugzilla-daemon
2013-11-20 0:51 ` bugzilla-daemon
2013-11-20 14:34 ` bugzilla-daemon
2013-11-25 14:43 ` bugzilla-daemon
2014-04-20 8:18 ` bugzilla-daemon
2014-04-20 8:19 ` bugzilla-daemon
2014-07-16 10:30 ` bugzilla-daemon [this message]
2014-07-16 14:45 ` bugzilla-daemon
2014-07-16 18:57 ` bugzilla-daemon
2014-07-21 18:58 ` bugzilla-daemon
2014-07-21 19:24 ` 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-71812-502-nijmNTo182@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