{"id":44,"date":"2006-07-13T21:18:14","date_gmt":"2006-07-13T21:18:14","guid":{"rendered":"https:\/\/www.bishnet.net\/tim\/blog\/2006\/07\/13\/slimp3slave-finally-working\/"},"modified":"2010-11-11T13:01:56","modified_gmt":"2010-11-11T13:01:56","slug":"slimp3slave-finally-working","status":"publish","type":"post","link":"https:\/\/www.bishnet.net\/tim\/blog\/2006\/07\/13\/slimp3slave-finally-working\/","title":{"rendered":"slimp3slave – finally working"},"content":{"rendered":"

In my last post about setting up a slimserver I said that I was having trouble getting slimp3slave<\/a> working:<\/p>\n

Whilst it doesn\u00e2\u20ac\u2122t appear to have any problems, I didn\u00e2\u20ac\u2122t have much success with the players. mpg123 got confused by the stream, and madplay kept skipping the beginnings of tracks when I hit next on the server. This could be a problem with slimp3slave – I\u00e2\u20ac\u2122ll need to investigate.<\/p><\/blockquote>\n

The problem did turn out to be with slimp3slave. I discovered that when skipping a track the stream is restarted which caused slimp3slave to start up a new player. The problem was this is that it did it before the old one had exited, thus causing the new one to die because it couldn’t access the sound device. There’s another bug here – it didn’t notice the new player dying and tried to write to it, which resulted in lots of SIGPIPE messages.<\/p>\n

So I looked at the code for shutting down the player and noticed that it wasn’t using the right close function. This change fixed it:<\/p>\n

RCS file: \/home\/pdw\/vcvs\/repos\/slimp3slave\/slimp3slave.c,v
\nretrieving revision 1.10
\ndiff -u -r1.10 slimp3slave.c
\n— slimp3slave.c 12 Apr 2004 08:04:52 -0000 1.10
\n+++ slimp3slave.c 22 Jun 2006 21:21:31 -0000
\n@@ -394,7 +394,7 @@
\n}<\/p>\n

void output_pipe_close(FILE * f) {
\n– fclose(f);
\n+ pclose(f);
\n}<\/p>\n

unsigned long curses2ir(int key) {<\/p><\/blockquote>\n

I have sent this change to the author, so maybe it’ll get integrated.<\/p>\n

Now I have a working streaming system. The only remaining problem seems to be the wireless networking to the client dropping out from time to time – a wire would fix that one \ud83d\ude42<\/p>\n

And in the past couple of days I’ve even got a client (softsqueeze on Windows this time) running at work that’s streaming the music over my ADSL connection. Very handy!<\/p>\n","protected":false},"excerpt":{"rendered":"

In my last post about setting up a slimserver I said that I was having trouble getting slimp3slave working: Whilst it doesn\u00e2\u20ac\u2122t appear to have any problems, I didn\u00e2\u20ac\u2122t have much success with the players. mpg123 got confused by the stream, and madplay kept skipping the beginnings of tracks when I hit next on the server. This could be a …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-44","post","type-post","status-publish","format-standard","hentry","category-computing"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t