I extracted it from the rootfs along with a couple of libraries it needed, and it appears to work about as well as the built-in mplayer.If I could get a binary download I'd try it, it seems to be mixed in with the entire angstrom OS image for the beagleboard in their downloads.
On a side note, with my Pandora overclocked to 1050mhz it -almost- plays 1280x720 x264 encoded files with subtitles with the built-in mplayer. It drops some frames on the heavier action scenes.
I extracted it from the rootfs along with a couple of libraries it needed, and it appears to work about as well as the built-in mplayer.If I could get a binary download I'd try it, it seems to be mixed in with the entire angstrom OS image for the beagleboard in their downloads.
On a side note, with my Pandora overclocked to 1050mhz it -almost- plays 1280x720 x264 encoded files with subtitles with the built-in mplayer. It drops some frames on the heavier action scenes.
However, I can't play any 720p file (I get an error that says "Source image dimensions are too high: 1280x720 (maximum is 800x480)".
If I try with -vo omapfb it just gives "[omapfb] Error mmap" and then the usual "FATAL: could not initialize video driver."
I don't know much about mplayer, though, so maybe someone else would have more luck.
http://www.mediafire.com/?be9idnn2d81wgcmCan you upload it somewhere?
How does one use this? I want mplayer version 4.4.4, not 4.3.3 on my Pandora.http://www.mediafire.com/?be9idnn2d81wgcmCan you upload it somewhere?
That's the mplayer binary plus the three libraries it wants on my Pandora.
Oddly, the mplayer binary from the rootfs appears to be the same (MPlayer SVN-r30165-4.3.3) as the native Pandora one. Different build, but same version, anyway.How does one use this? I want mplayer version 4.4.4, not 4.3.3 on my Pandora.
omapfbplay is a player that uses the DSP, it's the same as mplayer -vo omapfb
It won't work unless you reserve memory for it in the kernel (that's the mmap error). The DSP would need 32MB memory reserved.
Not true, it doesn't use DSP and I really doubt 'mplayer -vo omapfb' is the same as omapfbplay.omapfbplay is a player that uses the DSP, it's the same as mplayer -vo omapfb
It's unclear if that is enough, their examples have 128MB reserved..If you don't mind losing 32MB of RAM...
It's unclear if that is enough, their examples have 128MB reserved..If you don't mind losing 32MB of RAM...
Not true, it doesn't use DSP and I really doubt 'mplayer -vo omapfb' is the same as omapfbplay.omapfbplay is a player that uses the DSP, it's the same as mplayer -vo omapfb
mmap is normal system call, it has nothing to do with the DSP. This can be fixed with simple command:Hm, though omapfbplay makes the same error as mplayer (the mmap thing) AFAIR.
ofbset -fb /dev/fb1 -mem 2764800
Yeah that might be possible, there is just no one to do the work for this.I assume it means that 32mb+ would have to be permanently reserved in the OS which is not good. Would it be possible though to allow some kind of choice on bootup as to allocating the desired ram for the player? That way a simple reboot would let you have all system ram available to all progs if you were not going to watch video.