From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58696] New: Choppy video playback in VLC with R600g on Radeon HD 6620G
Date: Mon, 24 Dec 2012 02:32:53 +0000 [thread overview]
Message-ID: <bug-58696-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2499 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58696
Priority: medium
Bug ID: 58696
Assignee: dri-devel@lists.freedesktop.org
Summary: Choppy video playback in VLC with R600g on Radeon HD
6620G
Severity: normal
Classification: Unclassified
OS: All
Reporter: runetmember@gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Video playback of almost any typical 10Mbps 1080p BDRip is choppy (many dropped
frames) in VLC if R600g driver is used instead of fglrx on Radeon HD 6620G GPU.
Enabling/disabling composting doesn't make difference (so this issue is not
duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=47776 ).
Enabling/disabling "Suspend desktop effects for fullscreen windows" KWin
options doesn't make difference for fullscreen playback.
There is little difference between xv and OpenGL (GLX) output in VLC - xv
output a little faster but gives choppy playback too.
Issue is not reproducible:
1. in mplayer (SMPlayer is used) with R600g driver,
2. in Firefox (1080p VP8 playback) in Chrome (1080p H.264 playback) and in
Adobe Flash 11.5 plugin (1080p H.264 too) with R600g driver.
3. in VLC with fglrx driver (hardware decoder is not enabled).
Issue happen only in VLC&R600g combination.
VLC always uses indirect rendering instead of direct so I check mplayer
playback with disabled direct rendering and with enabled direct rendering but I
doesn't notice any difference. AFAIK mplayer and VLC drops frames very
differently so I check mplayer with disabled frame drop and with enabled frame
drop but (again) doesn't notice any difference. So I doesn't sure what exactly
is wrong in VLC&R600g combination but choppy video playback happen only in this
combination for sure. In my opinion issues most likely is relevant only for APU
hardware.
Video sample used for testing: http://www.multiupload.nl/56CCVTW42H (most
noticeable slowdown happen since 00:32).
Software:
Linux 3.8rc1
libdrm 2.4.40+git20121123.171666e4
Mesa 9.1~git20121222.a585b8f3
xserver-xorg-video-radeon 7.0.99+git20121207.793e1b0e
Xserver 1.13.0.902+git20121207
VLC 2.0.5 (default settings tested too - no difference)
mplayer 1.0~rc4.dfsg1+svn34540
Kubuntu 12.10 x86_64, Xorg Edgers PPA enabled.
Hardware:
A8-3500M with Radeon HD 6620G.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4000 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 reply other threads:[~2012-12-24 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 2:32 bugzilla-daemon [this message]
2012-12-24 9:14 ` [Bug 58696] Choppy video playback in VLC with R600g on Radeon HD 6620G bugzilla-daemon
2013-05-03 4:22 ` 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-58696-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.