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: Thu, 09 Jan 2014 22:57:52 +0000 [thread overview]
Message-ID: <bug-73457-502-VNufBGrxFW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73457-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1055 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73457
--- Comment #5 from Adam Hirst <adam@aphirst.karoo.co.uk> ---
Here are two trimmed file segments which behave in the curious way I've
described.
https://dl.dropboxusercontent.com/u/3219541/ppgz.avi
https://dl.dropboxusercontent.com/u/3219541/zillion.avi
Sometimes you have to be persistent; repeated attempts can be met with failure,
and then the next time just *works*, so I'm pretty sure this isn't the fault of
the files. Having another video playing using vdpau at the same time as trying
to open an mpeg4 file doesn't seem to affect whether the issue occurs. It also
occurs whether I'm on the laptop's LVDS screen, or over HDMI.
Also, a clarification about the mpv logs. The logs were generated using
vo_opengl, and hardware-decoding using vdpau uses the vdpau/opengl interop.
However, the same behaviour does occur when using plain vo_vdpau, with a
similar complete lack of difference between verbose logs generated.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2010 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-01-09 22:57 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 [this message]
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-VNufBGrxFW@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