There was an active discussion about this going on in an NVidia forum; figure we should probably move it back to the ATI/AMD forum so everyone can find it easily.
Current status in a nutshell is that our internal testing (which focuses on the NDA version of the API) indicates that XvBA is working on Evergreen, while end user experience (using gbeauche's VA-API adapter) is that Evergreen support does not work. The problem seems to be related to a specific function call used when running XvBA decode with GL output, which gbeauche apparently identified some time ago.
I don't know if the problem has been reproduced in the multimedia driver team; will try to chase that down next week.
Current status in a nutshell is that our internal testing (which focuses on the NDA version of the API) indicates that XvBA is working on Evergreen, while end user experience (using gbeauche's VA-API adapter) is that Evergreen support does not work. The problem seems to be related to a specific function call used when running XvBA decode with GL output, which gbeauche apparently identified some time ago.
I don't know if the problem has been reproduced in the multimedia driver team; will try to chase that down next week.
Comment