similar to: Icecast Digest, Vol 119, Issue 2

Thanks everyone! I will answer your questions regarding the AudioPump Web Encoder (http://demo.audiopump.co:3000/): *> Can you please explain the process exactly? what is the encoding server?* There is a server built on Node.js that receives audio data, control data, and metadata from the client over a binary websocket. All of these are multiplexed down the same connection. When the server

I have built a web-based source client using the Web Audio API and getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast source protocol for now, but I have the code nearly ready for the Icecast source protocol for when someone needs it. You can see a demo here: http://demo.audiopump.co:3000/ The Web Encoder is built with a jQuery Mobile UI optimized for mobile devices at the

Hi, On 20/02/13 11:38, Mike Thompsett wrote: > Hi All, > > Will this also bounce new connections to the relay server once the > master server is maxed out? So far we haven't done anything in this area. Also because I'd consider this to be outside of core icecast scope. (I won't oppose patches, though) The basic approach is round-robin DNS, which should give you an even

No problem Xabier, so we go, thank you !! El dom, 10-02-2013 a las 11:21 +0100, Xabier Oneca -- xOneca escribi?: > Oops! My fault, sorry!! :P > > > El 10/02/2013 03:01, "Jos? Luis Artuch" <artuch at speedy.com.ar> > escribi?: > > Ah ... thanks Dave, will give light to the subject: > <relay> >

2014-05-03 18:40 GMT+02:00 Brad Isbell <brad at musatcha.com>: > The general idea was to make a really simple source client that could be > launched with a single click (such as from a hosting provider's admin > panel). The client accepts parameters on the query-string for configuring > so that in a real-world environment, the user would not have to configure > anything.

Hi All, Will this also bounce new connections to the relay server once the master server is maxed out? Regards, Mike On 20 Feb 2013, at 07:53, Xabier Oneca -- xOneca <xoneca+icecast at gmail.com> wrote: > You have (little) documentation at > Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay > > Xabier Oneca_,,_ > > El 20/02/2013 08:48,

On 05/03/2014 04:40 PM, Brad Isbell wrote: > I have built a web-based source client using the Web Audio API and > getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast > source protocol for now, but I have the code nearly ready for the > Icecast source protocol for when someone needs it. > > You can see a demo here: http://demo.audiopump.co:3000/ That's

On 12/18/2014 09:43 PM, Xabier Oneca -- xOneca wrote: > > Hi Thomas, > > El 18/12/2014 22:25, Thomas B. R?cker <thomas at ruecker.fi > <mailto:thomas at ruecker.fi>> escribi?: > > > > On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote: > >> > >> Hello, Thomas, > >> > >> El 18/12/2014 21:35, Thomas B. R?cker <thomas at

You have (little) documentation at Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay Xabier Oneca_,,_ El 20/02/2013 08:48, "Xabier Oneca -- xOneca" <xoneca+icecast at gmail.com> escribi?: > You can set globally with the <relays-on-demand>1</relays-on-demand> in > the global <icecast/> section, or you can configure per-relay with >

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

Ah ... thanks Dave, will give light to the subject: <relay> <server>127.0.0.1</server> <port>8001</port> <mount>/example.ogg</mount> <local-mount>/different.ogg</local-mount> <on-demand>0</on-demand> <relay-shoutcast-metadata>0</relay-shoutcast-metadata>

Oops! My fault, sorry!! :P El 10/02/2013 03:01, "Jos? Luis Artuch" <artuch at speedy.com.ar> escribi?: > Ah ... thanks Dave, will give light to the subject: > <relay> > <server>127.0.0.1</server> > <port>8001</port> > <mount>/example.ogg</mount> >

Hi Thomas, El 18/12/2014 22:25, Thomas B. R?cker <thomas at ruecker.fi> escribi?: > > On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote: >> >> Hello, Thomas, >> >> El 18/12/2014 21:35, Thomas B. R?cker <thomas at ruecker.fi> escribi?: >> > >> > On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote: >> > > >> > >

The relaying-configuration seems to be straight-forward, unfortunately it does not work. That's my configuration: <relays-on-demand>1</relays-on-demand> <relay> <server>http://mp3stream7.apasf.apa.at</server> <port>8000</port> <mount>/</mount> <local-mount>/oe3.mp3</local-mount> <on-demand>1</on-demand>

Hi, On 10/02/13 06:53, Jos? Luis Artuch wrote: > I'm understanding why Icecast2 is an audio server, wow !!! > http://www.icecast.org/docs/icecast-2.0.1/icecast2_config_file.html > We're not an 'audio server', that's pulse-audio, esd, etc. territory. We're a multimedia streaming server. Slight difference. :) > Testing the relay option: > Two mountpoints

You can set globally with the <relays-on-demand>1</relays-on-demand> in the global <icecast/> section, or you can configure per-relay with <on-demand>. You can find it in the sample config file. (Does not say much more.) Xabier Oneca_,,_ El 20/02/2013 08:39, "Satz Klauer" <satzklauer at googlemail.com> escribi?: > Thanks, but which parameter influences

El mi?, 27-02-2013 a las 15:36 +0100, Xabier Oneca -- xOneca escribi?: > My last sentence still aplies to the bitrate. > Thanks Xabier, I mixed "burst" with "bitrate", was my confusion ;) > We usually use 80kbps, but sometimes we have used 64kbps (e.g. when > sourcing from a cellular network). > > With music you can get the difference, but with voice

On 12/18/2014 08:54 PM, Xabier Oneca -- xOneca wrote: > > Hello, Thomas, > > El 18/12/2014 21:35, Thomas B. R?cker <thomas at ruecker.fi > <mailto:thomas at ruecker.fi>> escribi?: > > > > On 12/18/2014 08:29 PM, Xabier Oneca -- xOneca wrote: > > > > > > Hello Daelynn, > > > > > > Icecast doesn't have SSL support, but

El dom, 10-02-2013 a las 17:47 -0300, Jos? Luis Artuch escribi?: > El dom, 10-02-2013 a las 10:07 +0200, R?cker Thomas escribi?: > > > Hi, > > > > On 10/02/13 06:53, Jos? Luis Artuch wrote: > > > > > > > I'm understanding why Icecast2 is an audio server, wow !!! > > > http://www.icecast.org/docs/icecast-2.0.1/icecast2_config_file.html

I was trying to tell you so. I'm not at home, so I can't tell you exactly how it is done, but I remember a <proxy> section in Icecast config file where you can tell the source stream and where to mount locally. But as I have said before, see the Icecast documentation for more details (or perhaps the original config file also has comments for configuring it). El 10/02/2013 00:12,