All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71812] New: VDPAU: MPEG-4 ASP Garbling/Corruption
Date: Tue, 19 Nov 2013 21:27:23 +0000	[thread overview]
Message-ID: <bug-71812-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2090 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=71812

          Priority: medium
            Bug ID: 71812
          Assignee: dri-devel@lists.freedesktop.org
           Summary: VDPAU: MPEG-4 ASP Garbling/Corruption
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: adam@aphirst.karoo.co.uk
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 9.2
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 89489
  --> https://bugs.freedesktop.org/attachment.cgi?id=89489&action=edit
Playback log from mpv-player

I initially reported this over at the FFmpeg Trac, so just in case I
accidentally omit to mention something I've already considered (or just for
reference), that's over at https://ffmpeg.org/trac/ffmpeg/ticket/3138

== Relevant Software / Hardware: ==
* AMD E2-1800 APU (/w Radeon HD 7340), i.e. PALM
* Linux 3.12 (Distro: Arch)
* FFmpeg 2.1
* mesa, mesa-libgl & ati-dri 9.2.3
* mplayer r36498, mpv 0.2.3 & VLC 2.1.1

== Summary: ==
Some files encoded into "MPEG-4 part 2" (seemingly, those using GMC, if zgreg's
hunch on #radeon is anything to go by) render/decode incorrectly using VDPAU
hardware-decoding on my AMD chipset. The files work fine using software
decoding, and worked fine back when using Catalyst & VA-API (which should mean
that the files and the hardware are fine).

By "incorrectly", I don't mean complete garbage. About half of the image
renders fine, it's just that between reference frames it progressively garbles
into a bright-green mess in heavily-updated areas. I'll try to catch a decent
screenshot demonstrating this when I can. In the meantime, I've put a sample
affected file up on my Dropbox account:
https://dl.dropboxusercontent.com/u/3219541/harlock-ep20.mkv

I'll re-attach here some mplayer/mpv logs, and some output from vdpauinfo and
ffprobe; and I'll also attach output from glxinfo. If there's anything extra I
ought to provide, please say so :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3694 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

             reply	other threads:[~2013-11-19 21:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 21:27 bugzilla-daemon [this message]
2013-11-19 21:27 ` [Bug 71812] VDPAU: MPEG-4 ASP Garbling/Corruption 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
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@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.