The most important part of flipflip patches is the replacement of two
mplayer files (mp_msg.c is one I think) and the rebuilding of mplayer. 
This will enable STDOUT to be used as an output as all error and banner
messages will then be sent to STDERR.  Flipflip calls his modified
mplayer executable mplayer-stdout just to identify it. 

This change means you must change custom-convert.conf so it does not
use mplayer.sh but flipflips mplayer-stdout directly.  The processing
power of a NAS is usually such that you cannot endocde the output from
mplayer in Flac or MP3 so Flipflips conf files don't modify those
lines. No changes are need to AlienBBC code - just the one conf file.

If the processor does not have a FPU (ewhich I believe to be the case)
you need to modify mplayer's "cook" routines as per this message
http://forums.slimdevices.com/showthread.php?t=34178&highlight=AlienBBC+arm%2A

Bandwidth option only speed up initial load for non live services - it
does not change the bit rate of the stream.

To check whether your unmodified version of mplayer can decode in time
the following command which redirects output to null.
mplayer -cache 128 -ao pcm:file=/dev/null
rtsp://rmlive.bbc.co.uk/bbc-rbs/rmlive/ev7/live24/radio4/live/r4_dsat_g2.ra

This is a live stream so theleft hand clock should run at normal time -
if it is slow (and cache % creeps up) then your mplayer cannot decode in
realtime - it will be able to decode in realtime using fixed point
routines.


-- 
bpa
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=35014

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins

Reply via email to