similar to: Circumvention of authentication when using fallback mounts

Good afternoon, On Fri, 2017-05-12 at 14:37 +0200, Michael Franzl wrote: > Using latest icecast, let's assume the following hosting scenario. (For the records: this applies to 2.4.x as well as current 2.5.x.) > We have 2 mountpoints which are configured with authentication callbacks: > > /mount1 > /mount2 > > Both mountpoints have configured the same fallback

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

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

Each MountPoint has a different URL, but in the ways that I have described, you don't use it like that. You can have 2 or 3 MountPoints but, one you can just serve as a fallback for all 3 of them. Let's take this example for a few seconds. Say for example, if you had, "http://yourdomain.com:8000/mount1" that will just serve as the listener MountPoint. "/mount2"

On 05/13/2017 03:12 PM, Philipp Schafft wrote: > Basically the client structure would need to keep track of which sources > the client was attached to in form of a stack. This is important as > there can be fallbacks of fallbacks (and there are valid reasons to > build something like that). A pure 'original mount' thing may result in > unexpected behavior. That being even

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

On Friday 18 July 2003 11:16, Ethan wrote: > Hello, I'm a long time user of Icecast. We currently run 12 streams on > Icecast 1.x (Mp3). I plan to expand this to 20 streems soon. They are all > low bitrate community service. > > Recently some friends and myself came across the thought of actually > generating our own content. Music, talk, etc. > > I've been running

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

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

Good evening, On Sat, 2017-05-13 at 16:11 +0200, Michael Franzl wrote: > On 05/13/2017 03:12 PM, Philipp Schafft wrote: > > Basically the client structure would need to keep track of which sources > > the client was attached to in form of a stack. This is important as > > there can be fallbacks of fallbacks (and there are valid reasons to > > build something like that).

I am using SystemImager to auto-install about 500 different machines, some of them are CentOS; as you can Imagine I want to automate the installation of the bootloader; so I wrote a 2 scripts to accomplish this task. Why two? Because some of the machines are IDE, and some of them are SATA, and I need to be able to use the same disk image on both of the drive types. Here is the first bash script:

On 18 Jul 2003 at 13:06, Michael Smith wrote: > On Friday 18 July 2003 11:16, Ethan wrote: > > If I had 1 icecast server acting as a relay, connecting to a 2nd > > one, could I switch between "2nd ones" and not interrupt the > > listener? > > Not precisely. What you can do (with icecast2) is: > server1: /relay-mount1 <---- server2 > :

Thanks been a big help!Have you got a personal email or Facebook that I can message so its off the mailing list Thankshannah To: icecast at xiph.org From: jonathancandler_msa at q.com Date: Tue, 17 Nov 2015 03:46:46 -0700 Subject: Re: [Icecast] fallback mount points? Each MountPoint has a different URL, but in the ways that I have described, you don't use it like

> Icecast2 is fully mp3 capable as well, calling 1.x "the mp3 capable icecast" > indicates you didn't realise that. It also supports other (better) formats as > well, of course... By the way, you were looking for the word "deprecated", > not "depreciated" (which is a real word, but means something entirely > different). So anyway, you can use mp3

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

Hello, this is coming from our radio station's icecast config. change at your needs and feel free to use this. <mount> <mount-name>/stream.mp3</mount-name> <fallback-mount>/live.mp3</fallback-mount> <fallback-override>1</fallback-override> <hidden>1</hidden> </mount> <mount>

On Thu, Jul 17, 2003 at 09:55:04AM -0600, Jack Moffitt wrote: > Please speak to Ralph Giles <giles@xiph.org> about obtaining commit > access to CVS. We should check in your debian/ dir into the official > tree and that way we can be sure to sync releases. Also people using CVS > snapshots will be able to build their own debs. Well... Thanks! I've been maintaining my own

Hi everyone, i would like to have some suggestion about the most appropriate source client to use in conjunction with IceCast2 given few requirements: 1) the client should be able to handle multiple streams simultaneously and thus multiple resource folders (for music files). 2) the client should be able to be programmatically manipulated (scripting or API) and can thus provide a dynamic way to

Hi guys , I have a little doubt: It's possible with the last version of icecast2 to set a diffferent password for every mountpoint different from the server's password? Becasue I want to manage the access to the server for every mountpoint and without give the server's password. Another question it's if I do some changes on the icecast.xml configuration , and later restart

Hi there! I don't know, if there have already been such a question, so that it is... I have icecast2 and 7 livestreams on it (by some reasons 6 darkices' mp3 and 1 ices2's ogg). By the given order I need to summarize the time each mount is listened for (for example, /mount1 is being listened by 3 listeners for 3 hours, than by 2 listeners for 1 hour and then by 1 listener for 2