All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73457] New: mpeg4 through vdpau randomly either correct or garbled (on same file!)
Date: Thu, 09 Jan 2014 22:41:45 +0000	[thread overview]
Message-ID: <bug-73457-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 73457
          Assignee: dri-devel@lists.freedesktop.org
           Summary: mpeg4 through vdpau randomly either correct or garbled
                    (on same file!)
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: adam@aphirst.karoo.co.uk
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 10.0
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 91790
  --> https://bugs.freedesktop.org/attachment.cgi?id=91790&action=edit
mpv verbose log, when video decodes successfully

This is somewhat difficult to explain.

* AMD PALM E2-1800 APU
* Arch Linux x86_64
* Kernel 3.12.6-ck (also with vanilla 3.12.6)
* mesa 10.0.1, xf86-video-ati 7.2.0

One of the following three situations occurs, seemingly at random, when opening
an mpeg4 video file using any player which supports vdpau hardware-decoding
(e.g. mplayer r36498, VLC 2.1.2, mpv 0.3.2)

1. The video decodes and plays just fine
2. The video decodes incorrectly, with bright-green garbling, and general
smearing
3. The video decodes and plays fine, BUT with a couple of small artefacts
either in the player window, or anywhere on the screen (the artefacts are
little black squares, inside which are a few fluorescent-coloured pixels
flickering)

The interesting point is that, on the same file, you can close and re-open the
video player and receive a different random outcome each time. I'm in the habit
of trying a few times to open my .avi videos until it "just works".

This is not the same as the mpeg4 ASP garbling issue which I reported a month
or so ago, which was 100% consistent on the affected files. For this bug, the
files which display *this* problem are 'normal' mpeg4 videos, and whether or
not decoding succeeds appears to be completely random.

Frustratingly, neither the video player's verbose logs, nor the DPM messages in
dmesg, indicate anything *at all* different between successful and unsuccessful
attempts.

I'll upload to this report a couple of log files, including the outputs of
ffmpeg -i on a selection of affected files.

I'll also upload some video samples, bear with me.

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

[-- Attachment #1.2: Type: text/html, Size: 3857 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:[~2014-01-09 22:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 22:41 bugzilla-daemon [this message]
2014-01-09 22:42 ` [Bug 73457] mpeg4 through vdpau randomly either correct or garbled (on same file!) bugzilla-daemon
2014-01-09 22:42 ` bugzilla-daemon
2014-01-09 22:43 ` bugzilla-daemon
2014-01-09 22:44 ` bugzilla-daemon
2014-01-09 22:57 ` bugzilla-daemon
2014-01-09 23:00 ` bugzilla-daemon
2014-01-09 23:05 ` bugzilla-daemon
2014-01-09 23:17 ` bugzilla-daemon
2014-01-09 23:22 ` bugzilla-daemon
2014-01-09 23:25 ` bugzilla-daemon
2014-01-09 23:26 ` bugzilla-daemon
2014-04-20  8:18 ` bugzilla-daemon
2014-04-20  8:19 ` bugzilla-daemon
2014-07-16 19:29 ` bugzilla-daemon
2014-07-17 15:26 ` bugzilla-daemon
2014-07-20 23:17 ` bugzilla-daemon
2019-09-18 19:12 ` 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-73457-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.