Tweet
Phoronix: XvMC With iDCT Now Working On Gallium3Dhttp://www.phoronix.com/vr.php?view=ODgwOQ
-
-
Good news, we need HW video acceleration for Gallium3d! -
This is very nice. But i have only one little problem.
I have only an grey screen.
Code:Player SVN-r1.0~rc3+svn20090426-4.4.3 (C) 2000-2009 MPlayer Team Playing It's Not My Time.mpg. MPEG-PS file format detected. VIDEO: MPEG2 720x480 (aspect 2) 29.970 fps 6124.8 kbps (765.6 kbyte/s) vo_xvmc: X-Video extension 2.2 vo_xvmc: X-Video MotionCompensation Extension version 1.1 ========================================================================== Forced video codec: ffmpeg12mc Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family [VD_FFMPEG] XVMC accelerated codec. [VD_FFMPEG] XVMC-accelerated MPEG-2. [VD_FFMPEG] XVMC-accelerated MPEG-2. Selected video codec: [ffmpeg12mc] vfm: ffmpeg (FFmpeg MPEG-1/2 (XvMC)) ========================================================================== ========================================================================== Opening audio decoder: [liba52] AC3 decoding with liba52 AUDIO: 48000 Hz, 2 ch, s16le, 448.0 kbit/29.17% (ratio: 56000->192000) Selected audio codec: [a52] afm: liba52 (AC3-liba52) ========================================================================== AO: [pulse] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... a52: CRC check failed! [VD_FFMPEG] Trying pixfmt=0. [VD_FFMPEG] XVMC-accelerated MPEG-2. VDec: vo config request - 720 x 480 (preferred colorspace: MPEG1/2 Motion Compensation and IDCT) vo_xvmc: Found matching surface with id=32315659 on 63 port at 0 adapter VDec: using MPEG1/2 Motion Compensation and IDCT as output csp (no 0) Movie-Aspect is 1.33:1 - prescaling to correct movie aspect. VO: [xvmc] 720x480 => 720x540 MPEG1/2 Motion Compensation and IDCT vo_xvmc: Found matching surface with id=32315659 on 63 port at 0 adapter vo_xvmc: Using Xv Adaptor #0 (Radeon Textured Video) vo_xvmc: Port 63 grabed vo_xvmc: Allocated Direct Context vo_xvmc: data_blocks allocated vo_xvmc: mv_blocks allocated vo_xvmc: Motion Compensation context allocated - 8 surfaces vo_xvmc: idct=1 unsigned_intra=0 vo_xvmc: looking for OSD support [VD_FFMPEG] XVMC-accelerated MPEG-2.
Comment
-
a question that might be silly (you've been warned
)
why it is so important to have vdpau and xvmc as a gallium state trackers????
i mean since vaapi has backends for different stuff (including vdpau) wouldn't it be more reasonable to implement that and gain the support for everything else from the backends??
Comment
-
XvMC is much simpler and a good proof-of-concept test before they start working on the more complicated stuff. For vdpau vs vaapi, i don't think it's really been decided yet which will be done. It sounds like they may go with vaapi because it's more friendly towards a shader based solution, but they'll probably just go with whatever is easier for them to implement.Originally posted by 89c51 View Posta question that might be silly (you've been warned)
why it is so important to have vdpau and xvmc as a gallium state trackers????
i mean since vaapi has backends for different stuff (including vdpau) wouldn't it be more reasonable to implement that and gain the support for everything else from the backends??
Comment
-
While it would certainly be nice to have a vendor independent standard for this, vaapi seems to be a fast moving target. In contrast, vdpau is widely used and proven and would instantly provide a broad user/client base to help testing. The folks over at MythTV should know best.Originally posted by smitty3268 View PostComment
-
i wonder if this site is still up to date
http://www.x.org/wiki/GalliumStatus
and if stuff like video accel and dx11 tracker should be displayed there too, or opengl/cl conformanceComment
-
g3dvl = videoOriginally posted by jakubo View Post
d3d1x = DX10 und DX11
And there is Currently no OpenCL State Tracker so why add it to table is it not exits.Comment
-
oh. ok... sry my faultComment
Comment