It's behaving as it is meant to: if a listen client gets too far behind, Icecast2 server is kicking them off. error.log says, "INFO source/source.c Client 120 (xxx.xxx.xxx.xxx) has fallen too far behind, removing" I don't see a setting in icecast.xml that sets the value for "too far behind". I'm guessing it's related to <queue-size>. I wish Icecast could dump the buffer and bring the listen-client back up to date instead of dumping the client. The reason being that when network congestion causes Icecast to kick my listen-client off, the client application just gives up. And this is a listen-client I'd like to have running 24/7 so I can monitor the station's backroom server when we are doing all-day music remotes. I haven't found a media/url player that attempts re-connect when kicked off. At least under Linux. On Windows a player called AIMP3 works great: if it is disconnected from the server, it tries to reconnect. Over and over and over. I like that behavior. -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics
Simply use VLC and put it on repeat. If a connection is lost during playback, it will reconnect and pick up in the current live position, like you have suggested, without stopping. If it cannot reconnect after 3 times, it goes to the next playlist item. If the playlist is on repeat, it runs indefinitely. Brad Isbell brad at musatcha.com http://www.musatcha.com On Wed, Apr 26, 2017 at 1:58 PM, Jack Elliott <thatjackelliott at kpov.org> wrote:> It's behaving as it is meant to: if a listen client gets too far behind, > Icecast2 server is kicking them off. > > error.log says, > > "INFO source/source.c Client 120 (xxx.xxx.xxx.xxx) has fallen too far > behind, removing" > > I don't see a setting in icecast.xml that sets the value for "too far > behind". I'm guessing it's related to <queue-size>. > > I wish Icecast could dump the buffer and bring the listen-client back up > to date instead of dumping the client. The reason being that when network > congestion causes Icecast to kick my listen-client off, the client > application just gives up. And this is a listen-client I'd like to have > running 24/7 so I can monitor the station's backroom server when we are > doing all-day music remotes. > > I haven't found a media/url player that attempts re-connect when kicked > off. At least under Linux. On Windows a player called AIMP3 works great: if > it is disconnected from the server, it tries to reconnect. Over and over > and over. I like that behavior. > > -- > That Jack Elliott > (541) 848 7021 > KPOV 88.9 FM High Desert Community radio > Producer, The Wednesday Point > Host, The Sunday Classics > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170426/824d4427/attachment.html>
Thanks, Brad -- I first turned to VLC but my stream-client device is a Raspberry Pi 3, and there doesn't seem to be a build for the device. That said, I just stumbled across mpg123, a command-line mp3/stream player that has audio buffer and timeout setting which so far looks quite robust. For Icecast2 content, when Icecast kicks a client off for being "too far behind" -- what is "too far"? -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 04/26/2017 08:10 PM, Brad Isbell wrote:> Simply use VLC and put it on repeat. If a connection is lost during > playback, it will reconnect and pick up in the current live position, > like you have suggested, without stopping. If it cannot reconnect > after 3 times, it goes to the next playlist item. If the playlist is > on repeat, it runs indefinitely. > > Brad Isbell > brad at musatcha.com <mailto:brad at musatcha.com> > http://www.musatcha.com > > On Wed, Apr 26, 2017 at 1:58 PM, Jack Elliott > <thatjackelliott at kpov.org <mailto:thatjackelliott at kpov.org>> wrote: > > It's behaving as it is meant to: if a listen client gets too far > behind, Icecast2 server is kicking them off. > > error.log says, > > "INFO source/source.c Client 120 (xxx.xxx.xxx.xxx) has fallen too > far behind, removing" > > I don't see a setting in icecast.xml that sets the value for "too > far behind". I'm guessing it's related to <queue-size>. > > I wish Icecast could dump the buffer and bring the listen-client > back up to date instead of dumping the client. The reason being > that when network congestion causes Icecast to kick my > listen-client off, the client application just gives up. And this > is a listen-client I'd like to have running 24/7 so I can monitor > the station's backroom server when we are doing all-day music remotes. > > I haven't found a media/url player that attempts re-connect when > kicked off. At least under Linux. On Windows a player called AIMP3 > works great: if it is disconnected from the server, it tries to > reconnect. Over and over and over. I like that behavior. > > -- > That Jack Elliott > (541) 848 7021 <tel:%28541%29%20848%207021> > KPOV 88.9 FM High Desert Community radio > Producer, The Wednesday Point > Host, The Sunday Classics > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org <mailto:Icecast at xiph.org> > http://lists.xiph.org/mailman/listinfo/icecast > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170426/e50446cf/attachment.html>