Results 1 to 2 of 2

Thread: With Chrome development choosing vaapi

  1. #1
    Join Date
    Jun 2012

    Default With Chrome development choosing vaapi

    I know that the xvba-vaapi bridge had not be updated since last June (per GIT Log in Anyone can comment whether you are currently still using it? In what kind of application and GPU are you using?

    With Chrome development choosing vaapi as the video acceleration layer someone from AMD should really take this up and make the UVD2 hardware useful in Linux. They could almost immediately gain traction with the large number of applications already supporting vaapi.

  2. #2
    Join Date
    Apr 2012


    Totally agree. Actually everyone should stick to one API and continue evolve around it.

Posting Permissions

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