Originally posted by benmoran
View Post
I just wanted to add something:
- the UVD hardware decoding engine's frontend (XVBA) used by fglrx is practically useless because no player supports it (xbmc was the only one that did but they canned support for it since radeon/VDPAU appeared). There are no other video players that use it under Linux AFAIK.
- The OSS Radeon driver on the other hand adopted VDPAU (ironically developed by nvidia) as the frontend for the hardware's UVD decoding engine. Since VDPAU is a long supported method by mplayer, xbmc, xine and other players (vlc just added support for it in 2.1/2.2), you can use it out of the box. Also, it works with the flash plugin on a few sites (youtube and a few more) if set up properly in the /etc/adobe/mms.cfg file.
The video playback in fglrx is tearing unless you use opengl for presentation (and that too sometimes). You actually have to enable the "tear-free" option in the driver that increases video memory usage (it triple buffers everything) and sometimes lowers playback framerate.
- Also sometimes the tearing issue appears in games too - the driver's option isnt always respected (this goes for in-game settings too).
- The OSS driver vsyncs by default everything, its much more controllable (prefix the executable with "vblank_mode=1" or 0 to force enable or disable it or set the vblank_mode to 1 or 0 previously by other means).
As per the above, using fglrx you have an advantage in some 3D apps, mainly high end games (others like Source games run perfectly well on radeon, better than on fglrx) and disadvantage in many other areas.
Leave a comment: