similar to: adjsting poll frequency intervals on slave-relay mountpoints

i have two linux b0x's . :: one main web server running icecast2 :: second machine at the studio , running icecast2 the studio machine receives dialup/hispeed.ogg streams locally from ices2 , the main web server is set as a relay for these live streams . if there isn't a live show , the website offers the correct archive for re-broadcast , this is played through the fileserver on main

> > > > MY QUESTiON -- if the main server is a relay for the studio , can i also > > connect local ices2 streams/mountpoints to it ? ? ie. a second, > > differently named set of dialup/hispeed.ogg mountpoints for the timed > > re-broadcasts . > > Yes, you can do that. <p>just lo0king at the ices2 .xml config now , i am (currently) using the /~msmith

Hello List Having great trouble relaying an icecast2 mp3 stream to a shoutcast server. My client program successfully streams to icecast which is listening on port 7000. I can listen to this stream with mozilla and xmms with no problems. I can also stream my client directly to the shoutcast server but it makes the client unstable (which is why i'm attempting a relay). The shoutcast server is

I understand there are two types of relays in icecast2. The master relay which relays everything from a source and a point relay which relays a specific mount point from a source. I have a server which has 3 streams. I want to relay 2 of them. How can I do this? Can I define two relays and two mountpoints within the xml config file? Do i do this in the same relay tag: <relay>

> this all works fine . but i want to set ices2 on the main web server to > actually broadcast the appropriate archives for off-live times , instead > of redirect to the fileserve . ( will this require much resources if the > mp3/ogg files are already encoded to the correct bitrate ? ) No. Without re-encoding, resource usage is very very low. > > > MY QUESTiON -- if the main

On 03/12/2015 09:24 PM, Dean Sauer wrote: > Looking at the documentation for 2.4.1 in regards to master/relay which > seems to outline what I want to do... > > Master = load balance/aribtrator for the relays where the sources connect. > > > The questions: > > 1) Bandwidth - How does the master pass off things to the relays for the > clients??? It's a pure

We found an interesing issue that after a downed publishing point is restored, the fallback relay doesn't stop relaying. We've tried everything, but once /asf2 or /asf3 is envoked for /asf1 fallback reasons, they don't stop relaying their source streams even though the output stream /asf1 has returned to normal. Eventually we end up with /asf2 relaying indefinately with no

I have a question about how the Master-Slave Relay works. Our current setup has an Icecast master running on an AWS EC2 Instance, that feeds its output to a few Icecast Relays on other EC2 instances which in turn connect to clients via an AWS load balancer. To make the system more robust, we have added a second Icecast master which all the Relays can switch to via a change in the Routing Table.

Great Job ! ;) Are you planning to : - correct the metadata problem when you're relaying an icecast v1 server ? (our radio totaly depend on icecast v1...) - add an option to enable backup streams only when the primary one is done ? I mean that if a defined two mountpoint that are relaying different stream (from a primary and a secondary server) and define the backup option to the second

Hi ! Well what I basically want to do is set up a local relay in our company for some popular shoutcast radio streams available on the winamp.com main site. Right now like 10 or 20 ppl here are listening to basically the same two or three streams, so thats quite a waste of bandwith. So I thought there must be some kind of stream relay that would connect as client to the Shoutcast server and be a

I currently have 3 mountpoints, 128, 56 and 24. I'm using darkice as the source and I'm relaying to another server running icecast2. I'm assuming that darkice is using lame for transcoding the bit-rates on the fly and sending 128k/s + 56k/s + 24k/s to the relay host... which is using a lot of bandwidth on the source network (which I don't have much to spare). Is there any

> > > > two ideas : > > - should/could i run 2 instances ices w/ separate .xml files ? > > Yes. i've g0t this working ,, but only w/ .ogg . does ices not support .mp3 for the playlist ? _ i even made a separate .xml for when .mp3 archives come up , and i've tried /64kbpsR AND /64kbpsR.mp3 as mountpoints . , all my archives from before December are mp3 ! gh .,

On Tue, 21 Jan 2003, Adon Irani wrote: > > > i've g0t this working ,, but only w/ .ogg . does ices not support .mp3 for > > > the playlist ? > > > _ i even made a separate .xml for when .mp3 archives come up , and i've > > > tried /64kbpsR AND /64kbpsR.mp3 as mountpoints . , > > > > > > all my archives from before December are mp3 ! gh

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

Ah, ok Satz, I did not know that's right :( Now I am trying: <server>194.232.200.156</server> <port>8000</port> <mount>/listen.pls</mount> <local-mount>/oe3.mp3</local-mount> ... but I do not get the mountpoint "oe3.mp3" in http://186.56.96.133:8200 May be something related with the extension "pls" ?. El mi?, 20-02-2013 a

I've been thinking more about this. It would be really nice if Icecast could add a port to a mountpoint and emulate whatever information Shoutcast requests when it relays a shoutcast stream. This way Shoutcast could relay Icecast streams. Fred _____ From: Fred Black [mailto:fred@batanga.com] Sent: Monday, July 18, 2005 2:36 PM To: 'icecast' Subject: RE: [Icecast]

> On Sun, 2004-02-15 at 19:52, Joern Nettingsmeier wrote: > > Michael Smith wrote: > > > On Thursday 12 February 2004 03:05, v b wrote: > > > > > >>I'm using this on icecat 1.3.12 but it doesn't seem to work with icecast > > >>2.0.0. The relay starts as soon as icecast is started and does not drop, > > >>even if there are no

Hi. <master-server>192.168.1.11</master-server> <master-server-port>8000</master-server-port> <master-update-interval>120</master-update-interval> <master-password>hackme</master-password> I'd like to relay from my icecast2 server to the other Icecast2 server. But I got the below error message. EROR

> > i've g0t this working ,, but only w/ .ogg . does ices not support .mp3 for > > the playlist ? > > _ i even made a separate .xml for when .mp3 archives come up , and i've > > tried /64kbpsR AND /64kbpsR.mp3 as mountpoints . , > > > > all my archives from before December are mp3 ! gh ., > > > > a:/, > > > > ices2 does not (and

One stream should have a mountpoint of /stream1 or something, and the other of /stream2. Then you access a stream like so: http://my.server.com:8000/stream1 or http://my.server.com:8000/stream2 then in the other icecast server, you just: relay pull http://my.server.com:8000/stream1 relay pull http://my.server.com:8000/stream2 that should work. jack. On Fri, Apr 27, 2001 at 03:57:37PM -0700,