[Bug 84255] New: UVD / VDPAU not working on kaveri with VLC
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Sep 23 10:43:10 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=84255
Priority: medium
Bug ID: 84255
Assignee: xorg-driver-ati at lists.x.org
Summary: UVD / VDPAU not working on kaveri with VLC
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: rvdb at cryptolab.net
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Driver/Radeon
Product: xorg
I'm running several AMD-based systems, including two with Kabini E-350 chips
and one with a Kaveri A10-7700 one.
All runs a Slackware64 system, with custom built 3.16.3 kernel and libdrm,
glamor, mesa and xf86-video-ati built from git pulls, dated on the 20th of
september, with exact same options.
Libvdpau 0.8 is installed on all systems, compiled with the same options.
vdpauinfo 0.1 is also installed, as well as x264, ffmpeg and vlc, all compiled
from git pulls, dated from the same 20th of september, with the same options on
all platforms.
The only differing options during compiles is that I use "-march=bdver3
-mtune=bdver3" on Kaveri while I use "-march=btver1 -mtune=btver1" on Kabini.
On Kaveri, vdpauinfo shows the following (only the begining):
**********
bash-4.3$ vdpauinfo -h
display: :0 screen: 0
API version: 1
Information string: G3DVL VDPAU Driver Shared Library version 1.0
Video surface:
name width height types
-------------------------------------------
420 16384 16384 NV12 YV12
422 16384 16384 UYVY YUYV
444 16384 16384 Y8U8V8A8 V8U8Y8A8
Decoder capabilities:
name level macbs width height
-------------------------------------------
MPEG1 0 9216 2048 1152
MPEG2_SIMPLE 3 9216 2048 1152
MPEG2_MAIN 3 9216 2048 1152
H264_BASELINE 41 9216 2048 1152
H264_MAIN 41 9216 2048 1152
H264_HIGH 41 9216 2048 1152
VC1_ADVANCED 4 9216 2048 1152
MPEG4_PART2_SP 3 9216 2048 1152
MPEG4_PART2_ASP 5 9216 2048 1152
(snip)
******************
On Kabini, I have the following output :
******************
bash-4.3$ vdpauinfo
display: :0 screen: 0
API version: 1
Information string: G3DVL VDPAU Driver Shared Library version 1.0
Video surface:
name width height types
-------------------------------------------
420 16384 16384 NV12 YV12
422 16384 16384 UYVY YUYV
444 16384 16384 Y8U8V8A8 V8U8Y8A8
Decoder capabilities:
name level macbs width height
-------------------------------------------
MPEG1 0 9216 2048 1152
MPEG2_SIMPLE 3 9216 2048 1152
MPEG2_MAIN 3 9216 2048 1152
H264_BASELINE 41 9216 2048 1152
H264_MAIN 41 9216 2048 1152
H264_HIGH 41 9216 2048 1152
VC1_ADVANCED 4 9216 2048 1152
MPEG4_PART2_SP 3 9216 2048 1152
MPEG4_PART2_ASP 5 9216 2048 1152
*****************
So far so good, the capabilities of both systems seem to be identical.
I have several H264 HD1080p videos with High Main profiles, and 41 levels.
They properly play on Kabini using VLC with VDPAU. The CPU usage is low for a
HD file and I can see in the vlc logs the following output :
****************
[00007f5954044cd8] vdpau_avcodec generic debug: video surface limits:
16384x16384
[00007f5954044cd8] vdpau_avcodec generic debug: decoder profile limits: level
41 mb 9216 2048x1152
[00007f5954044cd8] core generic debug: using hw decoder module "vdpau_avcodec"
[00007f5970d42768] avcodec decoder: Using G3DVL VDPAU Driver Shared Library
version 1.0 for hardware decoding.
[00007f5970d42768] avcodec decoder debug: available hardware decoder output
format 109 (vdpau)
[00007f5970d42768] avcodec decoder debug: available software decoder output
format 0 (yuv420p)
[00007f5954044cd8] core generic debug: looking for hw decoder module matching
"any": 2 candidates
[00007f5954044cd8] vdpau_avcodec generic debug: video surface limits:
16384x16384
[00007f5954044cd8] vdpau_avcodec generic debug: decoder profile limits: level
41 mb 9216 2048x1152
[00007f5954044cd8] core generic debug: using hw decoder module "vdpau_avcodec"
[00007f5970d42768] avcodec decoder: Using G3DVL VDPAU Driver Shared Library
version 1.0 for hardware decoding.
****************
On Kaveri, this does not work. CPU usage is high and no hardware decoding seems
to be used.
How is possible to debug this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-driver-ati/attachments/20140923/d97f8d1a/attachment.html>
More information about the xorg-driver-ati
mailing list