I got mplayer crashing. Both current svn mplayer and the one provided by script checkout-patch-build.sh.
Gentoo users can try mplayer ebuild from arcon overlay with vaapi USE flag.
Code:Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family [VD_FFMPEG] VA API accelerated codec. [VD_FFMPEG] Trying pixfmt=0. Unsupported PixelFormat -1 Could not find matching colorspace - retrying with -vf scale... Opening video filter: [scale] The selected video_out device is incompatible with this codec. Try appending the scale filter to your filter list, e.g. -vf spp,scale instead of -vf spp. [VD_FFMPEG] Trying pixfmt=1. Unsupported PixelFormat -1 Could not find matching colorspace - retrying with -vf scale... Opening video filter: [scale] The selected video_out device is incompatible with this codec. Try appending the scale filter to your filter list, e.g. -vf spp,scale instead of -vf spp. Unsupported PixelFormat -1 Unsupported PixelFormat -1 Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264) Starting playback... [h264 @ 0x8987120]decoding to PIX_FMT_NONE is not supported. [h264 @ 0x8987120]decode_slice_header error [h264 @ 0x8987120]no frame! Error while decoding frame! [h264 @ 0x8987120]decoding to PIX_FMT_NONE is not supported. [h264 @ 0x8987120]decode_slice_header error [h264 @ 0x8987120]no frame! Error while decoding frame! Too many audio packets in the buffer: (4099 in 4123594 bytes). Maybe you are playing a non-interleaved stream/file or the codec failed? For AVI files, try to force non-interleaved mode with the -ni option. FATAL: Could not initialize video filters (-vf) or video output (-vo).
and of course you have some source to support your claims? Or are you just talking out of your a??
Nvidia is currently tied up in three lawsuits thanks to bumpgate. Ati? How many?
And Apple was so unhappy with ATI that they just bought two complete month of production. Yeah, that spells 'unhappiness'.
Just because PulseAudio is crap (though according to the PA dev's blog, Ubuntu shares half the blame for its reputation), doesn't mean everything like it is. And VA-API isn't even remotely like it.
As with any complex system, sometimes it does take time to iron out the bugs, and sometimes you need to just need to know what you're doing in order to make it work the way you want it to, i.e., PA was missing a lot of the tools needed to make easy configuration changes, and yes, it is quite clear that ubuntu did make some retarded changes to it.
Has anyone been able to install the libamdxvba1.deb package that comes with FGLRX 9.10 on Ubuntu Koala Karmic (9.10)???
There is an unsatisfied dependency on libstdc++5, which does not come with Ubuntu 9.10. Does that mean all new Karmic users will not have video acceleration with ATI? Are there any ways around this issue?
Just fetch the package from jaunty. Maybe I patch the dependency out of the package later.
Mplayer (w/o vaapi): 78% CPU
Mplayer (w vaapi): 8% CPU
This on a dual core Athlon x2 2.3Ghz box using the IGP on my 780G motherboard.
Now, I'm just hoping AMD or SDS adds support for more formats, such as h263 and MPEG2, and gets the Va-api patches integrated into upstream ffmpeg and mplayer!! Then VA-API would become more ubiquitous.
Last edited by gururise; 11-05-2009 at 11:00 AM.
It's not an XvBA limitation but a limitation of the underlying HW. The API won't magically implement something if the underlying HW doesn't support it.
What exactly does that mean? Will MPEG2/4 see any benefit from XvBA in the near term or at all? Most of my use (>95% by percentage of play time) is MPEG2.
As a user I don't care about all of they gray areas and "I know something you don't know" that flies around at Phoronix. I'm just looking for a solution. This is the only place that has any info at all regarding the status of ATI on linux, but nothing real is ever said. I understand NDA but it would be nice to see some type of roadmap for where we are going. But all we get is grey noise. And right now neither ATI or OSS drivers can provide a complete workable solution, with only rumor suggesting it's coming, and only occasional out of the blue progress.
Back to the code itself... Is any effort going into integrating it into project mainlines - libva, FFMPEG, Mplayer, MythTV, VLC etc? I realize acceptance is project dependant but are the sources being marketed to them or is it destined to stay in the SDS tree for some long closed development cycle.