Page 1 of 5 123 ... LastLast
Results 1 to 10 of 46

Thread: A New Release Of The AMD XvBA Back-End To VA-API

  1. #1
    Join Date
    Jan 2007
    Posts
    15,625

    Default A New Release Of The AMD XvBA Back-End To VA-API

    Phoronix: A New Release Of The AMD XvBA Back-End To VA-API

    Splitted Desktop Systems has updated their closed-source library that provides an XvBA back-end to a VA-API front-end so that those running the ATI Catalyst Linux driver are able to take advantage of the UVD2 video engine on newer Radeon HD graphics cards...

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

  2. #2
    Join Date
    Aug 2008
    Posts
    116

    Default

    All I can say about this is "Meh". This software is about as useful to Radeon owners as MS-DOS is to a Linux user.

  3. #3
    Join Date
    Oct 2009
    Posts
    101

    Default

    Quote Originally Posted by JeanPaul145 View Post
    All I can say about this is "Meh". This software is about as useful to Radeon owners as MS-DOS is to a Linux user.
    Not necessarily. There are Radeon-based netbooks that can't otherwise manage HD video. That said, I won't use it, since the open-source drivers do a better job of satisfying my needs. I really want to know when we can expect a VA-API state tracker for Gallium.

  4. #4

    Default

    Anyone know if it finally has support for profiles L@5.1?

  5. #5
    Join Date
    Aug 2008
    Posts
    116

    Default

    Quote Originally Posted by waucka View Post
    Not necessarily. There are Radeon-based netbooks that can't otherwise manage HD video. That said, I won't use it, since the open-source drivers do a better job of satisfying my needs. I really want to know when we can expect a VA-API state tracker for Gallium.
    By the time there are usable radeon Gallium drivers, VA-API will be completely obsolete, since there is a WIP VDPAU state stracker.

  6. #6
    Join Date
    Sep 2008
    Location
    Seattle, WA, US
    Posts
    121

    Default

    Quote Originally Posted by JeanPaul145 View Post
    By the time there are usable radeon Gallium drivers, VA-API will be completely obsolete, since there is a WIP VDPAU state stracker.
    I really couldn't care less about an nvidia technology like VDPAU.

  7. #7
    Join Date
    Oct 2008
    Posts
    3,242

    Default

    Most of the work to create a VDPAU state tracker would be in the video decoding routines. Once someone's written the shaders and SSE code required, it should be relatively simple to wrap it up in either VDPAU or a VAAPI state tracker.

  8. #8

    Default

    In ArchLinux with the new version i have this error
    vainfo
    libva: libva version 0.31.0-sds6
    Xlib: extension "XFree86-DRI" missing on display ":0.0".
    libva: va_getDriverName() returns 0
    libva: Trying to open /usr/lib/va/drivers/fglrx_drv_video.so
    Violación de segmento

    xvba-video 0.6.11 works ok.

  9. #9
    Join Date
    Jan 2007
    Location
    Germany
    Posts
    2,175

    Default

    Quote Originally Posted by Cory View Post
    In ArchLinux with the new version i have this error
    vainfo
    libva: libva version 0.31.0-sds6
    Xlib: extension "XFree86-DRI" missing on display ":0.0".
    libva: va_getDriverName() returns 0
    libva: Trying to open /usr/lib/va/drivers/fglrx_drv_video.so
    Violación de segmento

    xvba-video 0.6.11 works ok.
    Update libva.

  10. #10
    Join Date
    Sep 2006
    Posts
    714

    Default

    Quote Originally Posted by KellyClowers View Post
    I really couldn't care less about an nvidia technology like VDPAU.
    It really does not matter. VDPAU is designed to be a open API.

    VA-API is designed to be a generic API that can be backed by VDPAU or whatever.

    But if a VDPAU state tracker exists then that may just end up being a cleaner solution for everybody to use regardless of the video card.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •