| Priority | medium |
|---|---|
| Bug ID | 67530 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | Wrong UVD capabilities reported by VDPAU on Brazos |
| Severity | normal |
| Classification | Unclassified |
| OS | Linux (All) |
| Reporter | richard.vdboom@gmail.com |
| Hardware | x86-64 (AMD64) |
| Status | NEW |
| Version | XOrg CVS |
| Component | DRM/Radeon |
| Product | DRI |
The VDPAU collects from VDPAU drivers a certain amount of capabilities that are supposed to allow user space program to check if the decoder is able to decode a particular stream or not. These parameters can be checked by the vdpauinfo tool and the begining of the output on Nvidia hardware looks like this : ****************** display: (null) screen: 0 API version: 0 Information string: Unknown Video surface: name width height types ------------------------------------------- 420 4096 4096 NV12 YV12 422 4096 4096 UYVY YUYV Decoder capabilities: name level ref width height ------------------------------------ MPEG1 0 2 4096 4096 MPEG2_SIMPLE 3 2 4096 4096 MPEG2_MAIN 3 2 4096 4096 H264_MAIN 41 4 4096 4096 H264_HIGH 41 4 4096 4096 ******************* Right now, the output on a Zacate / Brazos E450 system looks like this : ******************* bash-4.2$ 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 422 16384 16384 NV12 444 16384 16384 NV12 Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 16 9216 2048 1152 MPEG2_SIMPLE 16 9216 2048 1152 MPEG2_MAIN 16 9216 2048 1152 H264_BASELINE 16 9216 2048 1152 H264_MAIN 16 9216 2048 1152 H264_HIGH 16 9216 2048 1152 VC1_SIMPLE 16 9216 2048 1152 VC1_MAIN 16 9216 2048 1152 VC1_ADVANCED 16 9216 2048 1152 MPEG4_PART2_SP 16 9216 2048 1152 MPEG4_PART2_ASP 16 9216 2048 1152 ********************* Whatever the codec, the supported level is shown to be 16 (a non-existing level for h264 at least) and the macbs (the number of macroblocks) is always the same. This confuses players like VLC which adress libvdpau directly and get this answer (16) for the supported h264 level. Players like mplayer, which do not check this, play the video using UVD without problem. So there is just an issue with the way VDPAU reports UVD capabilities : it seems to just provide some kind of default.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
