Hi, I have used the SVN icecast-2.1-trunk version in my production system at http://audioserver.nl for 2 months now without problems. The fallbacks work fine as long as you make sure that the format (sampling frequency and bitrate) of the mount and it's fallback match. I have also patched the icecast-2.1-trunk version (patch not published yet, needs work to extract) to enable fallback of mulitple mounts to the same fallback with correct fallback-override. Meaning that if a two clients connected, one to mount1 with fallback to mount3 and one connects to mount2 also with fallback to mount3, then when the mount1 comes online, only the mount1 client would be moved back to mount1 and the same for mount2. I haven't tested the 2.1.0 release, so I don't know how it behaves when you configure multiple mounts to fallback to the same fallback mount. Anyone care to comment? If there is enough interest I am willing to spend some time to graft the 2.1-trunk patch onto the 2.1.0 release. Cheers, Klaas Jan -----Oorspronkelijk bericht----- Van: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org]Namens mark burdett Verzonden: dinsdag 9 november 2004 22:44 Aan: Geoff Shang CC: Icecast@xiph.org Onderwerp: Re: [Icecast] Multi-Level Fallbacks re: fallbacks & moving listeners, i've also seen/heard problems w/ mplayer and other free mp3 players.. i haven't yet done exhaustive testing to figure out which variables cause problems on which clients.. --mark On 07 Nov 2004, at 10:07, Geoff Shang wrote:> Hi: > > Is this an Ogg or MP3 stream? If MP3, do the same streams have the > same format? > > Geoff. > > > -- > Geoff Shang <geoff@hitsandpieces.net> > Phone: +61-418-96-5590 > MSN: geoff@acbradio.org > > Make sure your E-mail can be read by everyone! > http://www.betips.net/etc/evilmail.html > > Please avoid sending me Word or PowerPoint attachments. > See http://www.fsf.org/philosophy/no-word-attachments.html > _______________________________________________ > Icecast mailing list > Icecast@xiph.org > http://lists.xiph.org/mailman/listinfo/icecast_______________________________________________ Icecast mailing list Icecast@xiph.org http://lists.xiph.org/mailman/listinfo/icecast
On Mon, 2004-11-15 at 20:36, Klaas Jan Wierenga wrote:> Hi, > > I have used the SVN icecast-2.1-trunk version in my production system at > http://audioserver.nl for 2 months now without problems. The fallbacks work > fine as long as you make sure that the format (sampling frequency and > bitrate) of the mount and it's fallback match.samplerate and channels are the main ones to keep the same, not all systems can handle those changing mid stream.> I have also patched the icecast-2.1-trunk version (patch not published yet, > needs work to extract) to enable fallback of mulitple mounts to the same > fallback with correct fallback-override. Meaning that if a two clients > connected, one to mount1 with fallback to mount3 and one connects to mount2 > also with fallback to mount3, then when the mount1 comes online, only the > mount1 client would be moved back to mount1 and the same for mount2. > > I haven't tested the 2.1.0 release, so I don't know how it behaves when you > configure multiple mounts to fallback to the same fallback mount. Anyone > care to comment? > > If there is enough interest I am willing to spend some time to graft the > 2.1-trunk patch onto the 2.1.0 release.The easiest way to separate clients based on originating mountpoints is to use local relays /b relays /a /c relays /a /d fallback to /b /e fallback to /c karl.
Do you mean you can relay within a single icecast server instance? So the relay is running on the same icecast process from which it is relaying a stream? KJ -----Oorspronkelijk bericht----- Van: Karl Heyes [mailto:karl@xiph.org] Verzonden: maandag 15 november 2004 22:18 Aan: Klaas Jan Wierenga CC: icecast Onderwerp: Re: FW: [Icecast] Multi-Level Fallbacks On Mon, 2004-11-15 at 20:36, Klaas Jan Wierenga wrote:> Hi, > > I have used the SVN icecast-2.1-trunk version in my production system at > http://audioserver.nl for 2 months now without problems. The fallbackswork> fine as long as you make sure that the format (sampling frequency and > bitrate) of the mount and it's fallback match.samplerate and channels are the main ones to keep the same, not all systems can handle those changing mid stream.> I have also patched the icecast-2.1-trunk version (patch not publishedyet,> needs work to extract) to enable fallback of mulitple mounts to the same > fallback with correct fallback-override. Meaning that if a two clients > connected, one to mount1 with fallback to mount3 and one connects tomount2> also with fallback to mount3, then when the mount1 comes online, only the > mount1 client would be moved back to mount1 and the same for mount2. > > I haven't tested the 2.1.0 release, so I don't know how it behaves whenyou> configure multiple mounts to fallback to the same fallback mount. Anyone > care to comment? > > If there is enough interest I am willing to spend some time to graft the > 2.1-trunk patch onto the 2.1.0 release.The easiest way to separate clients based on originating mountpoints is to use local relays /b relays /a /c relays /a /d fallback to /b /e fallback to /c karl.