> A status update: as you will have seen from my earlier post, I broke down > and got the CVS version of icecast. Having compiled this up I get a good > stream at home (cable modem) and a seemingly good stream over 100Base-T > local to the machine at work (although winamp still flashes its little red > light at me - odd!)This may sound stupid, but did you set the HTTP streaming buffer high enough ? (I usually put it at about 128 or 256 K). Also, be sure not to to put the pre-load percentage too high; 50 % should do fine. Also, if you use XMMS, I really recommend using xmms-crossfade. Not only does it give you a nice buffer monitor, it also helps tremendously (a lot more than xmms internal buffer) in smoothing out the stream and catching buffer underruns. When using it, you sometimes see XMMS rebuffer, but it has no effect whatsoever on the audio output, which is a very good thing. These days I can let xmms run for 12 hours straight without any problem whatsoever on 128k streams. just some suggestions ... Thomas <-*- -*-> We'll walk right up to the sun hand in hand <-*- thomas@apestaart.org -*-> URGent, the best radio on the Internet - 24/7 ! - http://urgent.rug.ac.be/ --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> I consider icecast as a testing application server. You just cant deploy it > all of a sudden becuse it needs a lot of work still and the UI needs to be > friendlier. Lets wait till the top programmers come up with a centralI don't know why there's lots of problems lately. I assume some small libc implementation changed that icecast must have depended on. I ran icecast on 4 boxes, running 6 server per box, with a straight-out-of-the-box compile for almost a year. We didn't have any stuttering problems. It's true that sock.c did have a bug in it. But several of the proposed patches were _wrong_. The one in CVS should be correct. Saying that icecast is only appropriate for testing is wrong. Many people use it on a daily basis for production work. It looks like there's a legitimate hard-to-find bug in there somewhere, but on the bright side, icecast 2 seems to have _none_ of these problems. We might try all reporing our glibc versions, OS versions and vendors, and system load while broadcasting to see if there are any obvious similarities. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Hi all,>It looks like there's a legitimate hard-to-find bug in there somewhere, >but on the bright side, icecast 2 seems to have _none_ of these >problems. We might try all reporing our glibc versions, OS versions and >vendors, and system load while broadcasting to see if there are any >obvious similarities.Well, just for the record... Linux 2.2.16-3 #1 Mon Jun 19 18:49:25 EDT 2000 i586 unknown glibc-2.1.3-15 glib-1.2.6-3 glibc-devel-2.1.3-15 6:05pm up 117 days, 22:33, 1 user, load average: 0.00, 0.00, 0.00 As you can see, not too up to date, but also very lightly loaded (!) A status update: as you will have seen from my earlier post, I broke down and got the CVS version of icecast. Having compiled this up I get a good stream at home (cable modem) and a seemingly good stream over 100Base-T local to the machine at work (although winamp still flashes its little red light at me - odd!) I'd appreciate any reports if anyone would care to tune in - http://www.59tv.com:8000 I've spent the rest of the day fighting with icedj, and finally gave up. Either it needs a custom version of shout, or I really did configure it wrong! I've had a bit of trouble locating some of the other tools mentioned briefly (hampered by the lack of search facility on the mailing list archives). What are people using in general to feed playlists to ices ?? Only remaining irritation is ices desire to just go away after a while with this error.... Warning: Encountered error while transfering /usr/local/icecast/mp3/mjp01/trk8.mp3. [Libshout reported send error: Libshout socket error.] Libshout communication problem, trying to reconnect to server Failed reconnecting to server 127.0.0.1, error: 3 Ices Exiting... Nothing really amiss in icecast.log (it just says the source has timed out). Restarting ices gets it going again. My ices command line is... /usr/local/icecast/bin/ices -B -b 128 -d "Jazz/Funk/Rock from Films at 59" -F /usr/local/icecast/etc/$1 -g "Jazz/Funk/Rock" -h localhost -m zzzzz -n "Films at 59 Radio (Radio59)" -p nnnn -P xxxx -u "http://www.filmsat59.com/support/radio59.html" $1 is something like 'playlist.txt' Any ideas ??? Cheers, Mike mjp@filmsat59.com http://www.filmsat59.com Films at 59 Ltd, 59 Cotham Hill, Bristol. BS6 6JR ENGLAND +44 117 906 4300 --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Wednesday, 25 July 2001 at 18:15, Mike Prudence wrote:> I've had a bit of trouble locating some of the other tools mentioned > briefly (hampered by the lack of search facility on the mailing list > archives). What are people using in general to feed playlists to ices ??it's got a pretty straightforward scripting interface. I use a python script which gets tracks out of my database.> Only remaining irritation is ices desire to just go away after a while with > this error.... > > Warning: Encountered error while transfering > /usr/local/icecast/mp3/mjp01/trk8.mp3. [Libshout reported send error: > Libshout socket error.] > Libshout communication problem, trying to reconnect to server > Failed reconnecting to server 127.0.0.1, error: 3 > Ices Exiting...Try a newer version of ices. I haven't figured out what causes the socket error, but the latest version of ices try much harder to stay connected, and it seems to work well enough. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
I had this same problem for awhile on Icecast 1.3.10. I moved back to 1.3.0 (I know!) and it went away. At the time (a few months back) I was using CVS Ices. That was on this system: Linux 2.2.19 glibc-2.1.3-15 glib-1.2.6-3 glibc-devel-2.1.3-15 (I think pretty close to Mike's). Hunter> From: Mike Prudence <mjp@filmsat59.com> > Reply-To: icecast@xiph.org > Date: Wed, 25 Jul 2001 18:15:51 +0100 > To: icecast@xiph.org > Subject: Re: [icecast] Sacrilege, but... > > Only remaining irritation is ices desire to just go away after a while with > this error.... > > Warning: Encountered error while transfering > /usr/local/icecast/mp3/mjp01/trk8.mp3. [Libshout reported send error: > Libshout socket error.] > Libshout communication problem, trying to reconnect to server > Failed reconnecting to server 127.0.0.1, error: 3 > Ices Exiting...--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.