Announcement

Collapse
No announcement yet.

XvMC With iDCT Now Working On Gallium3D

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • XvMC With iDCT Now Working On Gallium3D

    Phoronix: XvMC With iDCT Now Working On Gallium3D

    A month ago there was the surprising work done by Christian K├Ânig to bring XvMC and VDPAU support to the open-source ATI Radeon "R600g" Gallium3D driver for the Radeon HD 2000/3000/4000/5000 series graphics cards. The XvMC state tracker with Gallium3D began working shortly thereafter for accelerating XvMC using shaders with this ATI Gallium3D driver, however, iDCT support was not implemented. Christian though has now added support for inverse discrete cosine transforms to this X-Video Motion Compensation code for Gallium3D...

    http://www.phoronix.com/vr.php?view=ODgwOQ

  • #2
    Good news, we need HW video acceleration for Gallium3d!

    Comment


    • #3
      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


      • #4
        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


        • #5
          Originally posted by 89c51 View Post
          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??

          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.

          Comment


          • #6
            Originally posted by Nille View Post
            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.
            Nille, take a look here.

            Comment


            • #7
              Originally posted by smitty3268 View Post
              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.
              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.

              Comment


              • #8
                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 conformance

                Comment


                • #9
                  Originally posted by jakubo View Post
                  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 conformance
                  g3dvl = video
                  d3d1x = DX10 und DX11

                  And there is Currently no OpenCL State Tracker so why add it to table is it not exits.

                  Comment


                  • #10
                    oh. ok... sry my fault

                    Comment

                    Working...
                    X