Reply With QuoteThe bug about not linking r300/r600 targets with libdrm should be fixed by now, please try again.
Yes, for the XvMC support you need a new DDX (xf86-video-ati).Originally Posted by Nille
Christian.
Senior Member
VDPAU and r300 - over the first hurdle
Once I managed to get the libraries to link correctly:
This is with my RV350; the video playback is recognisable but not quite right yet.Code:VDPAU_DRIVER=r300 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 2048 2048 NV12 YV12 Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 16 16384 2048 2048 MPEG2_SIMPLE 16 16384 2048 2048 MPEG2_MAIN 16 16384 2048 2048 Output surface: name width height nat types ---------------------------------------------------- Bitmap surface: name width height ------------------------------ Video mixer: feature name sup ------------------------------------ DEINTERLACE_TEMPORAL - DEINTERLACE_TEMPORAL_SPATIAL - INVERSE_TELECINE - NOISE_REDUCTION - SHARPNESS - LUMA_KEY - HIGH QUALITY SCALING - L1 - HIGH QUALITY SCALING - L2 - HIGH QUALITY SCALING - L3 - HIGH QUALITY SCALING - L4 - HIGH QUALITY SCALING - L5 - HIGH QUALITY SCALING - L6 - HIGH QUALITY SCALING - L7 - HIGH QUALITY SCALING - L8 - HIGH QUALITY SCALING - L9 - parameter name sup min max ----------------------------------------------------- VIDEO_SURFACE_WIDTH - VIDEO_SURFACE_HEIGHT - CHROMA_TYPE - LAYERS - attribute name sup min max ----------------------------------------------------- BACKGROUND_COLOR - CSC_MATRIX - NOISE_REDUCTION_LEVEL - SHARPNESS_LEVEL - LUMA_KEY_MIN_LUMA - LUMA_KEY_MAX_LUMA -
Last edited by chrisr; 07-14-2011 at 06:36 PM.
Junior Member
The bug about not linking r300/r600 targets with libdrm should be fixed by now, please try again.
Yes, for the XvMC support you need a new DDX (xf86-video-ati).
Christian.
Junior Member
Indeed it is.
mplayer keeps crashing here though.Code:VDPAU_DRIVER=r600 vdpauinfo display: :0.0 screen: 0 API version: 1 Information string: G3DVL VDPAU Driver Shared Library version 1.0 Video surface: name width height types ------------------------------------------- 420 8192 8192 NV12 YV12 Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 16 262144 8192 8192 MPEG2_SIMPLE 16 262144 8192 8192 MPEG2_MAIN 16 262144 8192 8192 Output surface: name width height nat types ---------------------------------------------------- Bitmap surface: name width height ------------------------------ Video mixer: feature name sup ------------------------------------ DEINTERLACE_TEMPORAL - DEINTERLACE_TEMPORAL_SPATIAL - INVERSE_TELECINE - NOISE_REDUCTION - SHARPNESS - LUMA_KEY - HIGH QUALITY SCALING - L1 - HIGH QUALITY SCALING - L2 - HIGH QUALITY SCALING - L3 - HIGH QUALITY SCALING - L4 - HIGH QUALITY SCALING - L5 - HIGH QUALITY SCALING - L6 - HIGH QUALITY SCALING - L7 - HIGH QUALITY SCALING - L8 - HIGH QUALITY SCALING - L9 - parameter name sup min max ----------------------------------------------------- VIDEO_SURFACE_WIDTH - VIDEO_SURFACE_HEIGHT - CHROMA_TYPE - LAYERS - attribute name sup min max ----------------------------------------------------- BACKGROUND_COLOR - CSC_MATRIX - NOISE_REDUCTION_LEVEL - SHARPNESS_LEVEL - LUMA_KEY_MIN_LUMA - LUMA_KEY_MAX_LUMA -
Code:VO: [vdpau] 624x352 => 624x352 Planar YV12 [vdpau] Error when calling vdp_presentation_queue_get_time: No backend implementation could be loaded. FATAL: Cannot initialize video driver.
Senior Member
It's already in the x11 overlay mesa ebuild!
Senior Member
What exactly does the "g3dvl" USE flag do? I see it's independent of the "vdpau", "vaapi" and "xvmc" flags. The description says:
"Enable video decode acceleration support for Gallium3D."
But what exactly does that mean, since it seems I can enable vdpau/vaapi/xvmc without it?
Junior Member
When you enable vdpau/vaapi/xvmc independly configure will fail if any of the needed development packages aren't found.
If you just specify "--enable-galium-g3dvl" it looks for the development packages and enables only those installed on the system.
Christian.
Senior Member
It 'works' for me with the following observations.
- There are artifacts in the picture
- CPU usage is quite a bit lower compared to -vo xv and -vo gl
- Playback is slower compared to -vo xv (a 50 sec clip takes a little over a minute with -vo vdpau)
Tested with 720p mpeg2 clip on 780G IGP.
So looks like the GPU is the bottleneck here. I wonder if this can be fixed in code, perhaps IGP has not enough shader processing power to decode HD content, period...
Last edited by monraaf; 07-15-2011 at 10:14 AM.
Senior Member
Thanks. It looks like this is a bad idea to have it in Gentoo as a USE flag, since "automagic" deps are pretty evil in source-based distros.
Senior Member
Don't be so quick in conclusions. I am sure FOSS vdpau will get some optimizations + r600g doesn't have optimizing shader compiler, yet. Once we get there, you can draw your conclusions.
Period
Junior Member
Could you please post a picture of the artifacts?
And which mpeg you are trying to play?
Try this: export R600_TILING=1
Without tilling my R710 can play a 1080p roughly over 37fps, with tilling it beats the 50fps mark.
Posting Permissions