We have a large number of users running our packages on an everyday basis. The latest testing builds also include VDPAU support, so Nvidia users that seek more performance and other improvements can easily test the latest master branch changes.
Many dedicated community members build packages for Opensuse, Arch linux, Debian and others. One of our early adopters was Openelec. Openelec 2.0 with its large user base will be released with an Xvba implementation directly based on our latest code.
In only five to six months sparetime work, we created a stable and to date unmatched experience for all AMD htpc users out there. Sounds too good to be true? Yeah, kind of as the future is totally unclear.
Let's continue with the dark side. What is not working for now? Basically everything we are awaiting from AMD since mid December. AMD did not update their xvba-sdk and there were no driver improvements regarding video decoding, e.g. faster decoding times. Therefore, feature wise we are exactly at the point we started from. Currently only standard files(e.g. Bluray) up to H264@High Level 4.1 are supported, that means: no more than 4 reframes at a resolution of 1920x1080 are decoded correctly. If you want to decode files with a higher level (5.0 or 5.1) and a large number of reframes you only see some kind of pixel mash. This is something we get complaints about at least twice a week. Most users cannot believe that in 2012 such a feature is just missing within a driver. In a nutshell, AMDs hardware platform is still held back on linux by its driver and API support.
Everytime we try to get into official contact, we are told that AMD was working on it and everything was nearly done. We are hearing this for approximately half a year now from AMD, but were never given a timeline. We are still waiting for H264@High Level 5.1 and Mpeg-2 Bitstream support, which is really important for DVB users, as a lot of live TV content is currently transmitted in this format. While we are at it - how about Mpeg-4/Divx support? In short: The same features available on Microsoft Windows for years.
Our sources say that these features are implemented in fglrx since a long time, but simply not activated within the driver. Nobody seems to know why.
But, we also have good news from AMD. We got into contact with a fglrx beta tester, that was willing to test our xvba implementation with early AMD Beta drivers. Some bugs reported directly to him got fixed within the latest 12.6 Beta release of fglrx, namely some ASIC hangs and the HDMI audio issue, which was a big showstopper for general Linux htpc users. But this situation is also not as fine as it could be. There are no plans on release cycles, there are no changelogs, there is no active bugtracker. Also dropping driver support for older hardware - which you can still buy everywhere - has not improved users trust in AMD.
We are looking forward to get Mpeg-2 support implemented and hope that AMD will give public news on how to enable the H264 Level 5.1 Profile. After this, we will push Xvba support into the offical xbmc repository (great review time). When our ffmpeg changes are accepted into XBMC mainline, we can send them upstream (ffmpeg itself) to help enable Xvba hardware support in all other movie players within the OSS world. All the other improvements developed and improved during our Xvba testings are pushed to upstream at the moment.
We are often asked about what hardware users should buy. The answer is not that easy. We came into contact with many AMD Fusion users with mostly E-350 and E-450. But yeah, if you see all the stuff that is not working and no one other than AMD can do something about it, it is a difficult decision. If you only look at the features available now and you want to invest into a power saving X86, small and highly integrated htpc at a reasonable price, nvidia with their approx 3 years old ION-2 is still the better choice on Linux platforms. Another choice is VAAPI on Intel Hardware that made a lot of progress in the past months, it is a pretty good alternative now. We really hope that AMD fixes these outstanding issues - for now it is like the famous novel of Samuel Beckett - Waiting For Godot. We hope that AMD Xvba is coming to another end.
Complete Xvba Implementing Team
Update: For those not familiar with the state of Linux video acceleration, read this article.
Discuss this article in our forums, IRC channel, or email the author. You can also follow our content via RSS and on social networks like Facebook, Identi.ca, and Twitter (@Phoronix and @MichaelLarabel). Subscribe to Phoronix Premium to view our content without advertisements, view entire articles on a single page, and experience other benefits.