dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73457] mpeg4 through vdpau randomly either correct or garbled (on same file!)
Date: Sun, 20 Jul 2014 23:17:23 +0000	[thread overview]
Message-ID: <bug-73457-502-0qID4XeJLU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73457-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from joaoboia@outlook.com ---
I can reproduce this very easily. 

I not sure when it actually started happening.
Play a mpeg4/h264 file on VLC, the video most of the times starts correctly, a
few times is just black, but when you try to seek the video there's always a
the chance the video will start either displaying green artefacts or the video
will  glitching and jumping frames back and forth. You can just keep seeking
until it resumes normally.

Sometimes it also triggered by heavy disk/cpu activity, and you will get green
artefacts this happens.

Strangely enough, it doesn't happen with XBMC (though there are other bugs
there).

Tends to happen less often with recent updates, but the issue is still there.

Ati HD4770
Arch Linux 3.15.5
Mesa 10.2.4
xf86-video-ati 7.4.0
VLC 2.1.5
XBMC 13.1

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

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

  parent reply	other threads:[~2014-07-20 23:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 22:41 [Bug 73457] New: mpeg4 through vdpau randomly either correct or garbled (on same file!) bugzilla-daemon
2014-01-09 22:42 ` [Bug 73457] " 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 [this message]
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-0qID4XeJLU@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