I'm looking for a way to tag my live feeds via an audio announcement every 30 minutes or so using the Linux install of Icecast. Some of the feeds I control locally, and other feeds are from remote locations - so implimenting this must be as painless as possible for each encoding location. As of now, the best way I can think of to do this is by running 2 instances of Icecast. Allowing the first instance to have the announcement as part of the "intro" tag, and kick each feed after 30 minutes, and then having the 2nd instance of Icecast relay all of the feeds from the first Icecast. These will also be standard announcements, and not rotating commercials. If this is the easiest way to continue, what is the process for installing a 2nd copy of Icecast on CentOS? Or do I just use icecast -b -c config.1 and icecast -b -c config.2 for each copy I want to run? Thanks for any help in getting this little project finalized. 73 Phil / W2LIE.
On Tue, Nov 02, 2010 at 02:35:46PM -0500, W2LIE wrote:> I'm looking for a way to tag my live feeds via an audio announcement every > 30 minutes or so using the Linux install of Icecast.I seem to remember that the kh-branch has some experimental ad-injection. http://www.xiphicecast.webspace.virginmedia.com/ It should do exactly what you want. There was something on the developer mailing list about it. 73 es 42 de Thomas, OH3-DM8TBR
On 02/11/10 19:35, W2LIE wrote:> I'm looking for a way to tag my live feeds via an audio announcement every > 30 minutes or so using the Linux install of Icecast. > > Some of the feeds I control locally, and other feeds are from remote > locations - so implimenting this must be as painless as possible for each > encoding location.> As of now, the best way I can think of to do this is by running 2 > instances of Icecast. Allowing the first instance to have the announcement > as part of the "intro" tag, and kick each feed after 30 minutes, and then > having the 2nd instance of Icecast relay all of the feeds from the first > Icecast. These will also be standard announcements, and not rotating > commercials.You could do this although you don't need 2 icecasts, you can use 2 mountpoints. mount1 would be the initial feed (relay/source), but with a max listener duration of say 1800 seconds and a intro file, the second mount (what listeners use) would be a relay of 127.0.0.1 mount1. The relay would be dropped and and restarted. Another/simpler way would be to run a source client every half an hour that overrides the mount running the stream and play just the ID once, the override moves the listeners and then the listeners fall back to the stream when finished. So mount1 would be the normal stream for listeners, mount2 would fed by a source client when you want the ID played, mount2 would fallback/override mount1 karl.
Karl & All, Thanks for the replies.. It looks like there might be 1,000 ways to skin this cat. I was even looking at the LiquidSoap Harbor code as well- but only if I can run LiquidSoap as a service under CentOS. 73 Phil On Tue, 02 Nov 2010 21:15:47 +0000, Karl Heyes <karl at xiph.org> wrote:> On 02/11/10 19:35, W2LIE wrote: >> I'm looking for a way to tag my live feeds via an audio announcement >> every >> 30 minutes or so using the Linux install of Icecast. >> >> Some of the feeds I control locally, and other feeds are from remote >> locations - so implimenting this must be as painless as possible foreach>> encoding location. > > >> As of now, the best way I can think of to do this is by running 2 >> instances of Icecast. Allowing the first instance to have the >> announcement >> as part of the "intro" tag, and kick each feed after 30 minutes, andthen>> having the 2nd instance of Icecast relay all of the feeds from thefirst>> Icecast. These will also be standard announcements, and not rotating >> commercials. > > You could do this although you don't need 2 icecasts, you can use 2 > mountpoints. mount1 would be the initial feed (relay/source), but with a> max listener duration of say 1800 seconds and a intro file, the second > mount (what listeners use) would be a relay of 127.0.0.1 mount1. The > relay would be dropped and and restarted. > > Another/simpler way would be to run a source client every half an hour > that overrides the mount running the stream and play just the ID once, > the override moves the listeners and then the listeners fall back to the> stream when finished. So mount1 would be the normal stream for > listeners, mount2 would fed by a source client when you want the ID > played, mount2 would fallback/override mount1 > > karl.