[maemo-developers] Python and GStreamer
From: Jesse Guardiani jesse at guardiani.usDate: Fri Aug 31 16:33:58 EEST 2007
- Previous message: Python and GStreamer
- Next message: Python and GStreamer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Austin Che wrote: > Koen Kooi <koen at dominion.kabel.utwente.nl> wrote: > > >> Jesse Guardiani schreef: >> >> >>>> And the related question is: given an existing program that sends >>>> stuff out to ALSA and doesn't use gstreamer, how difficult is it >>>> generally to port it so that it works properly? >>>> >>> No porting necessary, really. mplayer comes with a decoder called >>> libmp3. It's not optimized for ARM or anything, and it compiles without >>> any problems. We don't use it in Kagu for A2DP though because there is >>> another decoder out there called ffmp3 which doesn't use floating point >>> math, so it's a little more efficient on ARM. >>> >> use libmad (-ac mad), that works great on arm and x86. >> > > Ok thanks. So I went ahead and ported mpd and mpg321 to maemo. In > case anyone else wants these packages as I couldn't find them > already out there: http://austin.mit.edu/maemo > > mpd uses about 10% of the cpu and mpg321 uses about 20% of the CPU > even though they should be both using libmad. mpg321 seems to skip > a bit just switching apps but renicing it a bit appeared to get > rid of the skipping. I'm not sure why mpd seemed to do better in > general. Also, for some reason, using alsa output with mpd didn't > work (apparently segfaults) while libao output worked fine. > Is that on the n800 or 770? My experience has been that mplayer with ffmp3 typically gets about 16% CPU during playback on an n800 while playing back a very high quality VBR mp3. -- Jesse Guardiani Programmer/Sys Admin jesse at guardiani.us
- Previous message: Python and GStreamer
- Next message: Python and GStreamer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]