Ah well, if it can't be put on the player screen it can't. Would have
been the nicestfor a user.

I've looked at my slimserver.log with the new mplayer.sh.

I find one error message that exists even when AlienBBC is working and
mplayer is in the proper place.

Here is a code fragment


Terminal type `unknown' is not defined.
Stream description: Audio Stream
Stream mimetype: audio/x-pn-multirate-realaudio-live
/Users/danco/Library/SlimDevices/bin/mplayer.sh: line 31: line: command
not found
Streaming: Launching mplayer -really-quiet -vc null -vo null -bandwidth
10000000 -cache 128 -af volume=0,resample=44100:0:1,channels=2 -ao
pcm:nowaveheader:file=/dev/fd/3
rtsp://rmlivev8.bbc.net.uk/farm/*/ev7/live24/radio2/live/r2_dsat_g2.ra
2006-04-01 23:16:39.2325 Got sigterm.
2006-04-01 23:16:39.2335 SlimServer cleaning up.
MPlayer dev-CVS-060315-18:00-4.0.1 (C) 2000-2006 MPlayer Team
AltiVec found
CPU: PowerPC

When mplayer is in the wrong place, I don't see the error message you
put in mplayer.sh (probably it goes to a place that isn't easy to see).
But I do get an error message as given below

/Users/danco/Library/SlimDevices/bin/mplayer.sh: line 31: line: command
not found
Streaming: Launching mplayer -really-quiet -vc null -vo null -bandwidth
10000000 -cache 128 -af volume=0,resample=44100:0:1,channels=2 -ao
pcm:nowaveheader:file=/dev/fd/3
rtsp://rmlivev8.bbc.net.uk/farm/*/ev7/live24/radio2/live/r2_dsat_g2.ra
/Users/danco/Library/SlimDevices/bin/mplayer.sh: line 57: mplayer:
command not found
/Users/danco/Library/SlimDevices/bin/mplayer.sh: line 31: line: command
not found
Streaming: Launching mplayer -really-quiet -vc null -vo null -bandwidth
10000000 -cache 128 -af volume=0,resample=44100:0:1,channels=2 -ao
pcm:nowaveheader:file=/dev/fd/3
rtsp://rmlivev8.bbc.net.uk/farm/*/ev7/live24/radio2/live/r2_dsat_g2.ra
/Users/danco/Library/SlimDevices/bin/mplayer.sh: line 57: mplayer:
command not found


As we can't put the error message into the SB, I don't think it matters
that much.

I will check a bit further. The slimserver.log available from the
console is significantly larger than that available from the debugging
page of the Web interface. As far as I can see the latter resets each
time one restarts SlimServer, while the former keeps on getting bigger.


-- 
danco
------------------------------------------------------------------------
danco's Profile: http://forums.slimdevices.com/member.php?userid=210
View this thread: http://forums.slimdevices.com/showthread.php?t=22476

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

Reply via email to