Jack Elliott
2017-Apr-19 23:33 UTC
[Icecast] Using Icecast relay function with dynamic IP at remote source end
/I made an error, I swapped two diagrams, it should be this:/ Here's how I've been doing it: BUTT ===> WAN ===> Icecast server I thought I might try this instead: BUTT --> localhost Icecast server ===> WAN ===> Icecast server -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 4/19/2017 4:00 PM, Jack Elliott wrote:> > Hi David, I don't think we will necessarily be on wifi, I'm sorry if I > implied that. There are a couple of events each year when we have to > use wifi, but for those I have a dedicated access point running at > close to 1 watt connected directly to our ISP's network. > > Okay, I was told over on the Darkice listserv that using Darkice > WAN > > Icecast is not very reliable, and my testing supported that > statement. They said that Darkice is an encoder, and Icecast is a > transporter. Icecast, they said, is very reliable, Darkice is a good > encoder but not too great as a transporter. > > I've been using BUTT as the encoder at the remote (audio source) end, > and sending the stream over the WAN to the Icecast server at the > station building. BUTT, I found, is more reliable than Darkice at the > encoding end. > > Here's how I've been doing it: > > BUTT --> localhost Icecast server ===> WAN ===> Icecast server > > I thought I might try this instead: > > BUTT ===> WAN ===> Icecast server > > Now here I want to avoid using incorrect terminology. The way I am > using the word "remote" is how it is used in broadcast: if a crew > leaves the building to broadcast an event occurring outside the > station somewhere, they are doing a remote. > > So in my case, the "remote" is at the music festival - my audio source. > > So when you write, "The relay easiest to configured in a pull > configuration. Where the setting are setup on the remote server." -- > is it correct for me to interpret that to mean that I can leave the > settings on the station computer's server alone, just set up the > server in my remote kit to "pull" from the station's server? > > I am puzzled by "pull," since I am wanting to send audio from me to > the station, but that's pulling? > > -- > That Jack Elliott > (541) 848 7021 > KPOV 88.9 FM High Desert Community radio > Producer, The Wednesday Point > Host, The Sunday Classics > On 4/19/2017 10:26 AM, David Saunders wrote: >> Hey, >> >> The relay easiest to configured in a pull configuration. Where the >> setting are setup on the remote server. >> >> Since the client is on WiFi, you will have lots of issues >> streaming due to the ever changing wifi environment. My suggestion is >> source the stream at the lowest settings for encoding you can live >> with, This will keep the bandwidth down and less likely burp on you. >> >> We do have clients who use WiFi and set the the encoding to >> smallest size for the content being recorded. Most of the time since >> its voice content we really don't have to go super high on the encoding. >> >> I have set up the relay to supplement our bandwidth when we think it >> will be over the limit. Just remember you need to give the listeners >> the remote server connection info not the local server. >> >> Why it would be better? not sure why, but if the icecast server is >> set with a larger buffer, it will buffer thru the disconnects of the >> source. >> >> David. >> >> On Wed, Apr 19, 2017 at 11:02 AM, Marvin Scholz <epirat07 at gmail.com >> <mailto:epirat07 at gmail.com>> wrote: >> >> >> >> On 19 Apr 2017, at 16:20, Jack Elliott wrote: >> >> For our community radio station's live music festivals >> broadcasts, we set up a small broadcast studio at the >> festival's venue, and use B.U.T.T. to send a stream to an >> Icecast server located at the radio station's building. >> >> REMOTE LOCATION STATION BUILDING >> B.U.T.T. ======= WAN =======>> ICECAST SERVER >> >> It's pretty reliable, though BUTT does sometimes lose >> connection, probably due to network congestion. >> >> The folks on the Darkice listserv claim that using Icecast to >> do the sending provides a more reliable connection. So I want >> to try this idea: >> >> REMOTE LOCATION STATION BUILDING >> B.U.T.T. --> Icecast on localhost ==== WAN ====>> ICECAST SERVER >> >> >> I am not sure how this could be more reliable than BUTT alone. >> >> >> I'm finding the terminology for setting up a relay (on >> http://icecast.org/docs/icecast-2.4.0/config-file.html#relay >> <http://icecast.org/docs/icecast-2.4.0/config-file.html#relay>) >> to be a bit confusing and could use some help. >> >> I believe I want to set up a Specific Mountpoint Relay. It's >> where the IP addresses get plugged in that I need some >> clarification. The IP address for the building is static, but >> the IP address for the remote server is unknown before every >> festival, and may be dynamic. >> >> The documentation says that for the <relay> section of the >> xml, we have a <server>127.0.0.1</server> setting. And that >> is described as "This is the IP for the server which contains >> the mountpoint to be relayed." >> >> I can't tell whether the <relay? section is on the remote >> server, in which case we only need to put the static IP of >> the building in the <server> section, or whether the <relay> >> section is on the building's server, in which case we need to >> know ahead of time what our remote IP will be, and hope it >> doesn't change during the festival. >> >> I hope this question makes sense. My confusion is clearly >> because I am unclear which server (remote or building) the >> <relay> section applies to. >> >> -- >> 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 >> <http://lists.xiph.org/mailman/listinfo/icecast> >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org <mailto:Icecast at xiph.org> >> http://lists.xiph.org/mailman/listinfo/icecast >> <http://lists.xiph.org/mailman/listinfo/icecast> >> >> >> >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > > > _______________________________________________ > 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/20170419/c50a63d1/attachment.html>
David Saunders
2017-Apr-20 03:47 UTC
[Icecast] Using Icecast relay function with dynamic IP at remote source end
ok let see if I can translate it to broadcaster terms for ya :) A icecast server can be set up to accept direct source connection. ie dark ice( which i do agree runs better on the machine where icecast server is. ) I do use it to trans-code the mount to different encoding. THe icecast server can also set up as a relay, where it pulls in from the another server. Primary used to pull the stream from a icecast server. Then make it available to be acceded by clients from it mounts. But, BUTT is designed to stream to an icecast server, and does very well. http://icecast.org/docs/icecast-2.4.1/relaying.html Master is the source server (where the source comes from) ad Slave is the relay. THe connection is initiated by the slave to the master. BUTT ---MASTER ========= SLAVE ===== Clients --- can be local host or lan or wan private or public == is public connections wans/lans/... If you need more bandwidth you can setup/rent other SLAVEs on other networks to augment you bandwidth. It lot easier to have 1 master and bunch of slaves to spreading the bandwidth out, It easier to maintain a single master with many mounts + it easy to trace problems down with sources going to a common Master. I tend to diverge from your question a bit. But, your encoder should work find with broadcaster to the icecast server by itself. I have had it done for the past 10 years. The only real issue s when you encode the stream higher then what he bandwidth can handle. remember the source clients use the UPLOAD speed of you connection and the client use the UPLOAD speeds. In the USA it no uncommon to have uploads speeds to be far slower then you can download. Also I am talking about how fast the connection is not how much data you have in a month. It get really confusing when you talk about bandwidth, since they call both bandwidths.One is how big your pipe is and other how much you get through the pipe in a given time. Lot of the extra above fore those reading this and nee d a little more clarity :) David SLAVE looks a the master waiting for something to do. When it sees the mount it relays it. On Wed, Apr 19, 2017 at 7:33 PM, Jack Elliott <thatjackelliott at kpov.org> wrote:> *I made an error, I swapped two diagrams, it should be this:* > > Here's how I've been doing it: > > BUTT ===> WAN ===> Icecast server > > I thought I might try this instead: > > BUTT --> localhost Icecast server ===> WAN ===> Icecast server > > -- > That Jack Elliott(541) 848 7021 <(541)%20848-7021> > KPOV 88.9 FM High Desert Community radio > Producer, The Wednesday Point > Host, The Sunday Classics > > On 4/19/2017 4:00 PM, Jack Elliott wrote: > > Hi David, I don't think we will necessarily be on wifi, I'm sorry if I > implied that. There are a couple of events each year when we have to use > wifi, but for those I have a dedicated access point running at close to 1 > watt connected directly to our ISP's network. > > Okay, I was told over on the Darkice listserv that using Darkice > WAN > > Icecast is not very reliable, and my testing supported that statement. They > said that Darkice is an encoder, and Icecast is a transporter. Icecast, > they said, is very reliable, Darkice is a good encoder but not too great as > a transporter. > > I've been using BUTT as the encoder at the remote (audio source) end, and > sending the stream over the WAN to the Icecast server at the station > building. BUTT, I found, is more reliable than Darkice at the encoding end. > > Here's how I've been doing it: > > BUTT --> localhost Icecast server ===> WAN ===> Icecast server > > I thought I might try this instead: > > BUTT ===> WAN ===> Icecast server > > Now here I want to avoid using incorrect terminology. The way I am using > the word "remote" is how it is used in broadcast: if a crew leaves the > building to broadcast an event occurring outside the station somewhere, > they are doing a remote. > > So in my case, the "remote" is at the music festival - my audio source. > > So when you write, "The relay easiest to configured in a pull > configuration. Where the setting are setup on the remote server." -- is it > correct for me to interpret that to mean that I can leave the settings on > the station computer's server alone, just set up the server in my remote > kit to "pull" from the station's server? > > I am puzzled by "pull," since I am wanting to send audio from me to the > station, but that's pulling? > > -- > That Jack Elliott(541) 848 7021 <(541)%20848-7021> > KPOV 88.9 FM High Desert Community radio > Producer, The Wednesday Point > Host, The Sunday Classics > > On 4/19/2017 10:26 AM, David Saunders wrote: > > Hey, > > The relay easiest to configured in a pull configuration. Where the > setting are setup on the remote server. > > Since the client is on WiFi, you will have lots of issues streaming due > to the ever changing wifi environment. My suggestion is source the stream > at the lowest settings for encoding you can live with, This will keep the > bandwidth down and less likely burp on you. > > We do have clients who use WiFi and set the the encoding to smallest > size for the content being recorded. Most of the time since its voice > content we really don't have to go super high on the encoding. > > I have set up the relay to supplement our bandwidth when we think it will > be over the limit. Just remember you need to give the listeners the remote > server connection info not the local server. > > Why it would be better? not sure why, but if the icecast server is set > with a larger buffer, it will buffer thru the disconnects of the source. > > David. > > On Wed, Apr 19, 2017 at 11:02 AM, Marvin Scholz <epirat07 at gmail.com> > wrote: > >> >> >> On 19 Apr 2017, at 16:20, Jack Elliott wrote: >> >> For our community radio station's live music festivals broadcasts, we set >>> up a small broadcast studio at the festival's venue, and use B.U.T.T. to >>> send a stream to an Icecast server located at the radio station's building. >>> >>> REMOTE LOCATION STATION BUILDING >>> B.U.T.T. ======= WAN =======>> ICECAST SERVER >>> >>> It's pretty reliable, though BUTT does sometimes lose connection, >>> probably due to network congestion. >>> >>> The folks on the Darkice listserv claim that using Icecast to do the >>> sending provides a more reliable connection. So I want to try this idea: >>> >>> REMOTE LOCATION STATION BUILDING >>> B.U.T.T. --> Icecast on localhost ==== WAN ====>> ICECAST SERVER >>> >> >> I am not sure how this could be more reliable than BUTT alone. >> >> >>> I'm finding the terminology for setting up a relay (on >>> http://icecast.org/docs/icecast-2.4.0/config-file.html#relay) to be a >>> bit confusing and could use some help. >>> >>> I believe I want to set up a Specific Mountpoint Relay. It's where the >>> IP addresses get plugged in that I need some clarification. The IP address >>> for the building is static, but the IP address for the remote server is >>> unknown before every festival, and may be dynamic. >>> >>> The documentation says that for the <relay> section of the xml, we have >>> a <server>127.0.0.1</server> setting. And that is described as "This is the >>> IP for the server which contains the mountpoint to be relayed." >>> >>> I can't tell whether the <relay? section is on the remote server, in >>> which case we only need to put the static IP of the building in the >>> <server> section, or whether the <relay> section is on the building's >>> server, in which case we need to know ahead of time what our remote IP will >>> be, and hope it doesn't change during the festival. >>> >>> I hope this question makes sense. My confusion is clearly because I am >>> unclear which server (remote or building) the <relay> section applies to. >>> >>> -- >>> 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 >>> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > > > > _______________________________________________ > Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast > > > > > _______________________________________________ > Icecast mailing listIcecast at xiph.orghttp://lists.xiph.org/mailman/listinfo/icecast > > > > _______________________________________________ > 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/20170419/9a7d4b81/attachment-0001.html>
Jack Elliott
2017-Apr-20 23:05 UTC
[Icecast] Using Icecast relay function with dynamic IP at remote source end
Ha! Terms even a broadcaster can understand! Many many thanks. If BUTT is considered to be as good a transporter as Icecast, then I will stick with what I'm doing, if for no other reason than, "Master is the source server (where the source comes from) and Slave is the relay. THe connection is initiated by the slave to the master." Slave may not know where the Master is. Master (on a table in front of me at a remote music event) may be at unknown/dynamic IP address. I'd have to find my IP address, Teamview into the server computer at the station, stop the Icecast service, edit icecast.xml with my current IP address, and re-start the Icecast service. Is there any way to "push" a connection from Master to Slave? Slave is at a fixed IP address. -- That Jack Elliott (541) 848 7021 KPOV 88.9 FM High Desert Community radio Producer, The Wednesday Point Host, The Sunday Classics On 4/19/2017 8:47 PM, David Saunders wrote:> ok let see if I can translate it to broadcaster terms for ya :) > > A icecast server can be set up to accept direct source connection. ie > dark ice( which i do agree runs better on the machine where icecast > server is. ) I do use it to trans-code the mount to different encoding. > > THe icecast server can also set up as a relay, where it pulls in from > the another server. Primary used to pull the stream from a icecast > server. Then make it available to be acceded by clients from it mounts. > > But, BUTT is designed to stream to an icecast server, and does very well. > > > http://icecast.org/docs/icecast-2.4.1/relaying.html > > Master is the source server (where the source comes from) ad Slave is > the relay. THe connection is initiated by the slave to the master. > > BUTT ---MASTER ========= SLAVE ===== Clients > --- can be local host or lan or wan private or public > > == is public connections wans/lans/... > > If you need more bandwidth you can setup/rent other SLAVEs on other > networks to augment you bandwidth. > > It lot easier to have 1 master and bunch of slaves to spreading the > bandwidth out, It easier to maintain a single master with many mounts > + it easy to trace problems down with sources going to a common Master. > > I tend to diverge from your question a bit. But, your encoder should > work find with broadcaster to the icecast server by itself. I have had > it done for the past 10 years. The only real issue s when you encode > the stream higher then what he bandwidth can handle. remember the > source clients use the UPLOAD speed of you connection and the client > use the UPLOAD speeds. In the USA it no uncommon to have uploads > speeds to be far slower then you can download. Also I am talking about > how fast the connection is not how much data you have in a month. It > get really confusing when you talk about bandwidth, since they call > both bandwidths.One is how big your pipe is and other how much you get > through the pipe in a given time. > > Lot of the extra above fore those reading this and nee d a little more > clarity :) > David > > > SLAVE looks a the master waiting for something to do. When it sees the > mount it relays it. > > > > On Wed, Apr 19, 2017 at 7:33 PM, Jack Elliott > <thatjackelliott at kpov.org <mailto:thatjackelliott at kpov.org>> wrote: > > /I made an error, I swapped two diagrams, it should be this:/ > > Here's how I've been doing it: > > BUTT ===> WAN ===> Icecast server > > I thought I might try this instead: > > BUTT --> localhost Icecast server ===> WAN ===> Icecast server > > -- > That Jack Elliott > (541) 848 7021 <tel:%28541%29%20848-7021> > KPOV 88.9 FM High Desert Community radio > Producer, The Wednesday Point > Host, The Sunday Classics > > On 4/19/2017 4:00 PM, Jack Elliott wrote: >> >> Hi David, I don't think we will necessarily be on wifi, I'm sorry >> if I implied that. There are a couple of events each year when we >> have to use wifi, but for those I have a dedicated access point >> running at close to 1 watt connected directly to our ISP's network. >> >> Okay, I was told over on the Darkice listserv that using Darkice >> > WAN > Icecast is not very reliable, and my testing supported >> that statement. They said that Darkice is an encoder, and Icecast >> is a transporter. Icecast, they said, is very reliable, Darkice >> is a good encoder but not too great as a transporter. >> >> I've been using BUTT as the encoder at the remote (audio source) >> end, and sending the stream over the WAN to the Icecast server at >> the station building. BUTT, I found, is more reliable than >> Darkice at the encoding end. >> >> Here's how I've been doing it: >> >> BUTT --> localhost Icecast server ===> WAN ===> Icecast server >> >> I thought I might try this instead: >> >> BUTT ===> WAN ===> Icecast server >> >> Now here I want to avoid using incorrect terminology. The way I >> am using the word "remote" is how it is used in broadcast: if a >> crew leaves the building to broadcast an event occurring outside >> the station somewhere, they are doing a remote. >> >> So in my case, the "remote" is at the music festival - my audio >> source. >> >> So when you write, "The relay easiest to configured in a pull >> configuration. Where the setting are setup on the remote server." >> -- is it correct for me to interpret that to mean that I can >> leave the settings on the station computer's server alone, just >> set up the server in my remote kit to "pull" from the station's >> server? >> >> I am puzzled by "pull," since I am wanting to send audio from me >> to the station, but that's pulling? >> >> -- >> That Jack Elliott >> (541) 848 7021 <tel:%28541%29%20848-7021> >> KPOV 88.9 FM High Desert Community radio >> Producer, The Wednesday Point >> Host, The Sunday Classics >> On 4/19/2017 10:26 AM, David Saunders wrote: >>> Hey, >>> >>> The relay easiest to configured in a pull configuration. Where >>> the setting are setup on the remote server. >>> >>> Since the client is on WiFi, you will have lots of issues >>> streaming due to the ever changing wifi environment. My >>> suggestion is source the stream at the lowest settings for >>> encoding you can live with, This will keep the bandwidth down >>> and less likely burp on you. >>> >>> We do have clients who use WiFi and set the the encoding to >>> smallest size for the content being recorded. Most of the time >>> since its voice content we really don't have to go super high on >>> the encoding. >>> >>> I have set up the relay to supplement our bandwidth when we >>> think it will be over the limit. Just remember you need to give >>> the listeners the remote server connection info not the local >>> server. >>> >>> Why it would be better? not sure why, but if the icecast >>> server is set with a larger buffer, it will buffer thru the >>> disconnects of the source. >>> >>> David. >>> >>> On Wed, Apr 19, 2017 at 11:02 AM, Marvin Scholz >>> <epirat07 at gmail.com <mailto:epirat07 at gmail.com>> wrote: >>> >>> >>> >>> On 19 Apr 2017, at 16:20, Jack Elliott wrote: >>> >>> For our community radio station's live music festivals >>> broadcasts, we set up a small broadcast studio at the >>> festival's venue, and use B.U.T.T. to send a stream to >>> an Icecast server located at the radio station's building. >>> >>> REMOTE LOCATION STATION BUILDING >>> B.U.T.T. ======= WAN =======>> ICECAST SERVER >>> >>> It's pretty reliable, though BUTT does sometimes lose >>> connection, probably due to network congestion. >>> >>> The folks on the Darkice listserv claim that using >>> Icecast to do the sending provides a more reliable >>> connection. So I want to try this idea: >>> >>> REMOTE LOCATION STATION BUILDING >>> B.U.T.T. --> Icecast on localhost ==== WAN ====>> >>> ICECAST SERVER >>> >>> >>> I am not sure how this could be more reliable than BUTT alone. >>> >>> >>> I'm finding the terminology for setting up a relay (on >>> http://icecast.org/docs/icecast-2.4.0/config-file.html#relay >>> <http://icecast.org/docs/icecast-2.4.0/config-file.html#relay>) >>> to be a bit confusing and could use some help. >>> >>> I believe I want to set up a Specific Mountpoint Relay. >>> It's where the IP addresses get plugged in that I need >>> some clarification. The IP address for the building is >>> static, but the IP address for the remote server is >>> unknown before every festival, and may be dynamic. >>> >>> The documentation says that for the <relay> section of >>> the xml, we have a <server>127.0.0.1</server> setting. >>> And that is described as "This is the IP for the server >>> which contains the mountpoint to be relayed." >>> >>> I can't tell whether the <relay? section is on the >>> remote server, in which case we only need to put the >>> static IP of the building in the <server> section, or >>> whether the <relay> section is on the building's server, >>> in which case we need to know ahead of time what our >>> remote IP will be, and hope it doesn't change during the >>> festival. >>> >>> I hope this question makes sense. My confusion is >>> clearly because I am unclear which server (remote or >>> building) the <relay> section applies to. >>> >>> -- >>> 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 >>> <http://lists.xiph.org/mailman/listinfo/icecast> >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org <mailto:Icecast at xiph.org> >>> http://lists.xiph.org/mailman/listinfo/icecast >>> <http://lists.xiph.org/mailman/listinfo/icecast> >>> >>> >>> >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org <mailto:Icecast at xiph.org> >>> http://lists.xiph.org/mailman/listinfo/icecast >>> <http://lists.xiph.org/mailman/listinfo/icecast> >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org <mailto:Icecast at xiph.org> >> http://lists.xiph.org/mailman/listinfo/icecast >> <http://lists.xiph.org/mailman/listinfo/icecast> > _______________________________________________ Icecast mailing > list Icecast at xiph.org <mailto:Icecast at xiph.org> > http://lists.xiph.org/mailman/listinfo/icecast > <http://lists.xiph.org/mailman/listinfo/icecast> > > _______________________________________________ > 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/20170420/765375fd/attachment-0001.html>
I have spent part of today at a site which uses all of the above programs. A change of mains power service should be more reliable. Recent conversations here prompted this review. We have 2 machines running Darkice & Icecast2 each connected to a fibre service. Darkice is set to provide a high grade aac+ stream for 3 broadcast sites, a rebroadcast / logger [256b] mp3 local recording, and a skinny [56b] mp3 'website' stream. You can shape the mp3 audio with lowpass an highpass options. We have experimented with various formats and have gone with what the majority of players will handle. Everything runs at 48000 which is the native sampling rate of the on board sound cards. One less resampling process saves time and processor capacity. That's 2 Fibre cables in to the site, and 2 ISP's. One or other can fail, and they do, There was once a short period when both were out. We feed 3 broadcast sites and one IP relay site, which runs Icecast2. The relay site is a paid service provider and allows 200 connections. The relay site 'pulls' the audio from the fixed IP at the studio. It is configured and maintained by the service provider. This in turn feeds several relay services, some of them 'free', and a website player. I have no idea what the external links use, but everything works. There are more links than we know about as some just seem to add us to a list. We have a 'popular' programme! I note some of the relay sites resample our audio. The original installation was ADSL and the uplink could not manage 4 clients because ADSL uplinks are really low grade. In fact we think the ISP's were controlling the bandwidth more than they would admit. We used one upload to an IP relay site. Now we have fibre the relay transmitters connect direct. Each darkice machine has a logger which is a script running as an hourly cron job. We use a high sample rate because a number of the live programmes get rebroadcast. The playout machine is limited to wav and mp3. We use BUTT in a laptop connected to a mobile phone as a hotspot for OB's [Remotes] and the G3 uplink is generally good. We are fortunate that the cellular coverage here is mostly very good and very few users occupy the uplink. We have used local ADSL and Fibre. If we have an event where there will be a huge number of people live streaming from their smartphones, which tends to overload the network we make sure we have a non cellular circuit. BUTT feeds one of the studio Icecast2 servers and comes up in the studio on a second computer running Chrome. Audio plays direct into the desk from the #2 computer soundcard. BUTT is simple, works in windows, and its easy to adjust the bit rate to suit the link. It works better with a bit of headroom. Keep the levels down! Avoid processing. Sample as high as possible. The big advantage of this setup is the cost. The darkice/icecast2 machines are old ex lease junk computers we get for next to nothing. Once configured they run with no screen keyboard or mouse. The HP ones have better power supplies. OS and software is free. They reboot and run BUTT runs on Windows which the frontline are comfortable with. Everyone has a laptop. It does not matter what IP BUTT has, it sends to the fixed IP at the studio on port [ 8000 ] with a mount like /liveBroadcast.mp3 We get around crossovers by arranging presentation to accomodate the audio delay. Darkice handles multiple encoding with ease. Icecast2 does the transportation BUTT is the simple remote origination solution. regards Robert -- *Raupo Radio* 64 Warner Park Avenue Laingholm Auckland 0604 09 8176358 0221693124 06 650 6087 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20170421/93410bcd/attachment.html>
Possibly Parallel Threads
- Using Icecast relay function with dynamic IP at remote source end
- Using Icecast relay function with dynamic IP at remote source end
- Using Icecast relay function with dynamic IP at remote source end
- Using Icecast relay function with dynamic IP at remote source end
- Using Icecast relay function with dynamic IP at remote source end