From yellowjacketlite at gmail.com  Thu Feb  5 14:45:28 2015
From: yellowjacketlite at gmail.com (Tony)
Date: Thu, 5 Feb 2015 09:45:28 -0500
Subject: [Icecast] Typically end-to-end 'delay' of live audio
Message-ID: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>

I have an audio device driver for a live feed that produces Opus frames, if
I were to use icecast, what sort of real-time delay can I expect? 3-5s?
5-10s? more?

I've tried using the html5 <audio> tag directly to stream my source, but it
seems browsers like to queue-up 250K to 500K of audio 'data' before they
begin playback.  That introduces a 15-30s delay depending on browser and
the audio compression used.  I'd like an html5 (plugin-less) solution that
introduces no more than a 3-5s delay.
-- 
Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150205/1ad55029/attachment.htm>

From thomas at ruecker.fi  Thu Feb  5 16:03:08 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 05 Feb 2015 16:03:08 +0000
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
Message-ID: <54D3943C.2070502@ruecker.fi>

On 02/05/2015 02:45 PM, Tony wrote:
> I have an audio device driver for a live feed that produces Opus
> frames, if I were to use icecast, what sort of real-time delay can I
> expect? 3-5s? 5-10s? more?

Likely that or more. This highly depends on the client side buffers.
Icecast itself doesn't buffer much and that can be disabled by turning
off the burst-on connect functionality.
HTTP streaming is not "real-time" for most values of real time, it's
still more "real time" than HLS thought, to my surprise.


> I've tried using the html5 <audio> tag directly to stream my source,
> but it seems browsers like to queue-up 250K to 500K of audio 'data'
> before they begin playback.  That introduces a 15-30s delay depending
> on browser and the audio compression used.  I'd like an html5
> (plugin-less) solution that introduces no more than a 3-5s delay.

Yes, you can't control client side buffers for HTTP based streaming to
browsers.

If you aim for something reliably <<5s without having total control of
the client side, then your best bet is to look at something else. Maybe
WebRTC?

I'd probably be able to point out something more helpful, but you don't
state your actual use case.

Generic standard comment:
Most cases where people think they need an Icecast stream to have a
"low" delay are cases where some slight change in approaching the
problem would help. E.g. for collaborative streaming a real time / VoIP
backend that then streams to Icecast. Or in case of a "internet radio" a
question queue instead of trying to achieve "chat like response" over
the air, or rely on listeners actually "dialling in" through e.g. VoIP
for questions.


Cheers

Thomas





From yellowjacketlite at gmail.com  Thu Feb  5 16:30:45 2015
From: yellowjacketlite at gmail.com (Tony)
Date: Thu, 5 Feb 2015 11:30:45 -0500
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <54D3943C.2070502@ruecker.fi>
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
	<54D3943C.2070502@ruecker.fi>
Message-ID: <CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>

Thanks.  Here's bit more detail.

We have a scientific audio instrument that comes with its own audio
driver.  This driver gives us Opus 'frames'.  From a remote location
(typically less than 200mS round trip) we would like someone using a
browser (without a plugin) to 'hear' this device.  We need the low
end-to-end delay as there is an active Video session (separate application)
connecting the same two locations.  The remote participant has the ability
to mute either feed (video or scientific device).  However, if the device's
feed is too far 'delayed' from the video feed, it becomes rather annoying
for the remote participant even with the audio portion of the video feed
muted.

Today, we have a browser plugin.  And we transmit the device's audio data
to the remote participant via websockets, wherein the browser feeds the
data to the plugin for decoding and playback.

Unfortunately, browser plugin's are dying technology.  In fact, chrome is
phasing them out later this year.  And Firefox claims they will do the same
"soon".  So, we need to find a replacement.


On Thu, Feb 5, 2015 at 11:03 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:

> On 02/05/2015 02:45 PM, Tony wrote:
> > I have an audio device driver for a live feed that produces Opus
> > frames, if I were to use icecast, what sort of real-time delay can I
> > expect? 3-5s? 5-10s? more?
>
> Likely that or more. This highly depends on the client side buffers.
> Icecast itself doesn't buffer much and that can be disabled by turning
> off the burst-on connect functionality.
> HTTP streaming is not "real-time" for most values of real time, it's
> still more "real time" than HLS thought, to my surprise.
>
>
> > I've tried using the html5 <audio> tag directly to stream my source,
> > but it seems browsers like to queue-up 250K to 500K of audio 'data'
> > before they begin playback.  That introduces a 15-30s delay depending
> > on browser and the audio compression used.  I'd like an html5
> > (plugin-less) solution that introduces no more than a 3-5s delay.
>
> Yes, you can't control client side buffers for HTTP based streaming to
> browsers.
>
> If you aim for something reliably <<5s without having total control of
> the client side, then your best bet is to look at something else. Maybe
> WebRTC?
>
> I'd probably be able to point out something more helpful, but you don't
> state your actual use case.
>
> Generic standard comment:
> Most cases where people think they need an Icecast stream to have a
> "low" delay are cases where some slight change in approaching the
> problem would help. E.g. for collaborative streaming a real time / VoIP
> backend that then streams to Icecast. Or in case of a "internet radio" a
> question queue instead of trying to achieve "chat like response" over
> the air, or rely on listeners actually "dialling in" through e.g. VoIP
> for questions.
>
>
> Cheers
>
> Thomas
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>



-- 
Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150205/162c388f/attachment.htm>

From thomas at ruecker.fi  Thu Feb  5 16:52:49 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 05 Feb 2015 16:52:49 +0000
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>	<54D3943C.2070502@ruecker.fi>
	<CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>
Message-ID: <54D39FE1.2010507@ruecker.fi>

Hi,

On 02/05/2015 04:30 PM, Tony wrote:
> Thanks.  Here's bit more detail.
>
> We have a scientific audio instrument that comes with its own audio
> driver.  This driver gives us Opus 'frames'.  From a remote location
> (typically less than 200mS round trip) we would like someone using a
> browser (without a plugin) to 'hear' this device.  We need the low
> end-to-end delay as there is an active Video session (separate
> application) connecting the same two locations.  The remote
> participant has the ability to mute either feed (video or scientific
> device).  However, if the device's feed is too far 'delayed' from the
> video feed, it becomes rather annoying for the remote participant even
> with the audio portion of the video feed muted.

Ideally you'd mux both video and audio and thus establishing a strict
relation between both.
As it sounds you don't have that option (video happening outside the
browser?) it becomes rather tricky.

> Today, we have a browser plugin.  And we transmit the device's audio
> data to the remote participant via websockets, wherein the browser
> feeds the data to the plugin for decoding and playback.

I'd probably look at webRTC (don't have experience but might be better
suited or even able to consume what you have) or reusing that existing
websocket and instead of feeding a plugin, feed it to a javascript based
decoder. I've heard of emscripten based compiles working reasonably, but
haven't tried it in a while (both audiocogs and libav I've noticed).

You should also ask the opus mailing list. They might have better
suggestions. Our event horizon is quite limited to HTTP here on this list.

> Unfortunately, browser plugin's are dying technology.  In fact, chrome
> is phasing them out later this year.  And Firefox claims they will do
> the same "soon".  So, we need to find a replacement.

I'll disagree, fortunately they are fading away. I'm not entirely sure
if everything that is moving in to replace them is good, but so far it
doesn't look as bad as it used to be.
I do realize though that the scientific community has come to rely on a
variety of specific browser plugins and was a slow mover so far. I hope
you get your specific use case sorted without going through too much pain.


Cheers

Thomas

>
>
> On Thu, Feb 5, 2015 at 11:03 AM, "Thomas B. R?cker" <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> wrote:
>
>     On 02/05/2015 02:45 PM, Tony wrote:
>     > I have an audio device driver for a live feed that produces Opus
>     > frames, if I were to use icecast, what sort of real-time delay can I
>     > expect? 3-5s? 5-10s? more?
>
>     Likely that or more. This highly depends on the client side buffers.
>     Icecast itself doesn't buffer much and that can be disabled by turning
>     off the burst-on connect functionality.
>     HTTP streaming is not "real-time" for most values of real time, it's
>     still more "real time" than HLS thought, to my surprise.
>
>
>     > I've tried using the html5 <audio> tag directly to stream my source,
>     > but it seems browsers like to queue-up 250K to 500K of audio 'data'
>     > before they begin playback.  That introduces a 15-30s delay
>     depending
>     > on browser and the audio compression used.  I'd like an html5
>     > (plugin-less) solution that introduces no more than a 3-5s delay.
>
>     Yes, you can't control client side buffers for HTTP based streaming to
>     browsers.
>
>     If you aim for something reliably <<5s without having total control of
>     the client side, then your best bet is to look at something else.
>     Maybe
>     WebRTC?
>
>     I'd probably be able to point out something more helpful, but you
>     don't
>     state your actual use case.
>
>     Generic standard comment:
>     Most cases where people think they need an Icecast stream to have a
>     "low" delay are cases where some slight change in approaching the
>     problem would help. E.g. for collaborative streaming a real time /
>     VoIP
>     backend that then streams to Icecast. Or in case of a "internet
>     radio" a
>     question queue instead of trying to achieve "chat like response" over
>     the air, or rely on listeners actually "dialling in" through e.g. VoIP
>     for questions.
>
>
>     Cheers
>
>     Thomas
>
>
>
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto:Icecast at xiph.org>
>     http://lists.xiph.org/mailman/listinfo/icecast
>
>
>
>
> -- 
> Tony
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast




From corbe at corbe.net  Thu Feb  5 20:30:31 2015
From: corbe at corbe.net (Daniel Corbe)
Date: Thu, 05 Feb 2015 15:30:31 -0500
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
	(Tony's message of "Thu, 5 Feb 2015 09:45:28 -0500")
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
Message-ID: <87fvakw17c.fsf@corbe.net>


This is slightly off topic, but why fuss over broadcast delay budget?
What are you broadcasting that's so sensitive to delay?

Curiously,
Daniel

Tony <yellowjacketlite at gmail.com> writes:

> I have an audio device driver for a live feed that produces Opus frames, if I were to use icecast, what sort of
> real-time delay can I expect? 3-5s? 5-10s? more?
>
> I've tried using the html5 <audio> tag directly to stream my source, but it seems browsers like to queue-up 250K to
> 500K of audio 'data' before they begin playback.? That introduces a 15-30s delay depending on browser and the audio
> compression used.? I'd like an html5 (plugin-less) solution that introduces no more than a 3-5s delay.
> --
> Tony
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From jerickson at logicalnetworking.net  Fri Feb  6 01:43:19 2015
From: jerickson at logicalnetworking.net (Jordan Erickson)
Date: Thu, 05 Feb 2015 17:43:19 -0800
Subject: [Icecast] Cool Mic (Android source client) v0.4 released
In-Reply-To: <54C52DE4.1020106@logicalnetworking.net>
References: <54BED61D.1050205@logicalnetworking.net>	<20150125113440.GB28726@aporee.org>
	<54C52DE4.1020106@logicalnetworking.net>
Message-ID: <54D41C37.7030400@logicalnetworking.net>

Hi List,

We've fixed some stuff and made a few improvements to Cool Mic. Please
see the "News" link for changes and to download the latest beta:
http://coolmic.net/?page_id=98

Any feedback, including bug reports, suggestions and/or questions are
very much appreciated!


Cheers,
Jordan



From stefb at wizzz.net  Fri Feb  6 10:27:22 2015
From: stefb at wizzz.net (=?windows-1252?Q?St=E9phane_Benoit?=)
Date: Fri, 06 Feb 2015 11:27:22 +0100
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>	<54D3943C.2070502@ruecker.fi>
	<CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>
Message-ID: <54D4970A.2010309@wizzz.net>

Hello,

Have you tried something like 
http://www.schillmania.com/projects/soundmanager2/ for your player ?

It looks promising.

Regards,
St?phane Benoit.

Le 05/02/2015 17:30, Tony a ?crit :
> Thanks.  Here's bit more detail.
>
> We have a scientific audio instrument that comes with its own audio 
> driver.  This driver gives us Opus 'frames'.  From a remote location 
> (typically less than 200mS round trip) we would like someone using a 
> browser (without a plugin) to 'hear' this device.  We need the low 
> end-to-end delay as there is an active Video session (separate 
> application) connecting the same two locations.  The remote 
> participant has the ability to mute either feed (video or scientific 
> device).  However, if the device's feed is too far 'delayed' from the 
> video feed, it becomes rather annoying for the remote participant even 
> with the audio portion of the video feed muted.
>
> Today, we have a browser plugin.  And we transmit the device's audio 
> data to the remote participant via websockets, wherein the browser 
> feeds the data to the plugin for decoding and playback.
>
> Unfortunately, browser plugin's are dying technology.  In fact, chrome 
> is phasing them out later this year.  And Firefox claims they will do 
> the same "soon".  So, we need to find a replacement.
>
>
> On Thu, Feb 5, 2015 at 11:03 AM, "Thomas B. R?cker" <thomas at ruecker.fi 
> <mailto:thomas at ruecker.fi>> wrote:
>
>     On 02/05/2015 02:45 PM, Tony wrote:
>     > I have an audio device driver for a live feed that produces Opus
>     > frames, if I were to use icecast, what sort of real-time delay can I
>     > expect? 3-5s? 5-10s? more?
>
>     Likely that or more. This highly depends on the client side buffers.
>     Icecast itself doesn't buffer much and that can be disabled by turning
>     off the burst-on connect functionality.
>     HTTP streaming is not "real-time" for most values of real time, it's
>     still more "real time" than HLS thought, to my surprise.
>
>
>     > I've tried using the html5 <audio> tag directly to stream my source,
>     > but it seems browsers like to queue-up 250K to 500K of audio 'data'
>     > before they begin playback.  That introduces a 15-30s delay
>     depending
>     > on browser and the audio compression used.  I'd like an html5
>     > (plugin-less) solution that introduces no more than a 3-5s delay.
>
>     Yes, you can't control client side buffers for HTTP based streaming to
>     browsers.
>
>     If you aim for something reliably <<5s without having total control of
>     the client side, then your best bet is to look at something else.
>     Maybe
>     WebRTC?
>
>     I'd probably be able to point out something more helpful, but you
>     don't
>     state your actual use case.
>
>     Generic standard comment:
>     Most cases where people think they need an Icecast stream to have a
>     "low" delay are cases where some slight change in approaching the
>     problem would help. E.g. for collaborative streaming a real time /
>     VoIP
>     backend that then streams to Icecast. Or in case of a "internet
>     radio" a
>     question queue instead of trying to achieve "chat like response" over
>     the air, or rely on listeners actually "dialling in" through e.g. VoIP
>     for questions.
>
>
>     Cheers
>
>     Thomas
>
>
>
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto:Icecast at xiph.org>
>     http://lists.xiph.org/mailman/listinfo/icecast
>
>
>
>
> -- 
> Tony
>
>
> _______________________________________________
> 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/20150206/03d5de42/attachment.htm>

From yellowjacketlite at gmail.com  Fri Feb  6 12:41:56 2015
From: yellowjacketlite at gmail.com (Tony)
Date: Fri, 6 Feb 2015 07:41:56 -0500
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <54D4970A.2010309@wizzz.net>
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
	<54D3943C.2070502@ruecker.fi>
	<CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>
	<54D4970A.2010309@wizzz.net>
Message-ID: <CAE9wCXAe8ZL3YeWUP5xKSxS+2JkWiJnTZKcJT=QmUt34606sQw@mail.gmail.com>

Not yet.  We have thought about going to flash in hopes it would provide
less latency, but I haven't looked into it yet.  Though, technically, flash
is a plugin, but it seems to have earned "special status" by the browser
developers.

On Fri, Feb 6, 2015 at 5:27 AM, St?phane Benoit <stefb at wizzz.net> wrote:

>  Hello,
>
> Have you tried something like
> http://www.schillmania.com/projects/soundmanager2/ for your player ?
>
> It looks promising.
>
> Regards,
> St?phane Benoit.
>
> Le 05/02/2015 17:30, Tony a ?crit :
>
>  Thanks.  Here's bit more detail.
>
> We have a scientific audio instrument that comes with its own audio
> driver.  This driver gives us Opus 'frames'.  From a remote location
> (typically less than 200mS round trip) we would like someone using a
> browser (without a plugin) to 'hear' this device.  We need the low
> end-to-end delay as there is an active Video session (separate application)
> connecting the same two locations.  The remote participant has the ability
> to mute either feed (video or scientific device).  However, if the device's
> feed is too far 'delayed' from the video feed, it becomes rather annoying
> for the remote participant even with the audio portion of the video feed
> muted.
>
>  Today, we have a browser plugin.  And we transmit the device's audio data
> to the remote participant via websockets, wherein the browser feeds the
> data to the plugin for decoding and playback.
>
>  Unfortunately, browser plugin's are dying technology.  In fact, chrome is
> phasing them out later this year.  And Firefox claims they will do the same
> "soon".  So, we need to find a replacement.
>
>
> On Thu, Feb 5, 2015 at 11:03 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
> wrote:
>
>> On 02/05/2015 02:45 PM, Tony wrote:
>> > I have an audio device driver for a live feed that produces Opus
>> > frames, if I were to use icecast, what sort of real-time delay can I
>> > expect? 3-5s? 5-10s? more?
>>
>> Likely that or more. This highly depends on the client side buffers.
>> Icecast itself doesn't buffer much and that can be disabled by turning
>> off the burst-on connect functionality.
>> HTTP streaming is not "real-time" for most values of real time, it's
>> still more "real time" than HLS thought, to my surprise.
>>
>>
>> > I've tried using the html5 <audio> tag directly to stream my source,
>> > but it seems browsers like to queue-up 250K to 500K of audio 'data'
>> > before they begin playback.  That introduces a 15-30s delay depending
>> > on browser and the audio compression used.  I'd like an html5
>> > (plugin-less) solution that introduces no more than a 3-5s delay.
>>
>> Yes, you can't control client side buffers for HTTP based streaming to
>> browsers.
>>
>> If you aim for something reliably <<5s without having total control of
>> the client side, then your best bet is to look at something else. Maybe
>> WebRTC?
>>
>> I'd probably be able to point out something more helpful, but you don't
>> state your actual use case.
>>
>> Generic standard comment:
>> Most cases where people think they need an Icecast stream to have a
>> "low" delay are cases where some slight change in approaching the
>> problem would help. E.g. for collaborative streaming a real time / VoIP
>> backend that then streams to Icecast. Or in case of a "internet radio" a
>> question queue instead of trying to achieve "chat like response" over
>> the air, or rely on listeners actually "dialling in" through e.g. VoIP
>> for questions.
>>
>>
>> Cheers
>>
>> Thomas
>>
>>
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>
>
>
> --
> Tony
>
>
> _______________________________________________
> 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
>
>


-- 
Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150206/8ef25521/attachment.htm>

From michel.memeteau at gmail.com  Sat Feb  7 09:17:29 2015
From: michel.memeteau at gmail.com (Michel Memeteau)
Date: Sat, 7 Feb 2015 10:17:29 +0100
Subject: [Icecast] Typically end-to-end 'delay' of live audio
In-Reply-To: <CAE9wCXAe8ZL3YeWUP5xKSxS+2JkWiJnTZKcJT=QmUt34606sQw@mail.gmail.com>
References: <CAE9wCXA1bJ54dtY-U-6pKghXOSJjRH9MFDa2e-XLJPfWm8usnA@mail.gmail.com>
	<54D3943C.2070502@ruecker.fi>
	<CAE9wCXD0B8HXh7VbFK86=w+CLGx6EwWk_QnPyEudMPBbgwxxfw@mail.gmail.com>
	<54D4970A.2010309@wizzz.net>
	<CAE9wCXAe8ZL3YeWUP5xKSxS+2JkWiJnTZKcJT=QmUt34606sQw@mail.gmail.com>
Message-ID: <CAJbJ1BsFs9nTJVo7CS-s-E9ftH9WjjOdzeiP-fRhKFwZFBmLqg@mail.gmail.com>

Just my thoughts : Flash is dead and even be blocked as a default in a
near future by most browsers.

I don't think the delay is on the browser side, but more on the
processing/server side here.
<----------------------------------------------------------------------------------------------------------->
http://shop.ekimia.fr : Achetez votre PC Ubuntu Linux en ligne , support inclus.
Photos perso sur : http://memeteau.org


2015-02-06 13:41 GMT+01:00 Tony <yellowjacketlite at gmail.com>:
> Not yet.  We have thought about going to flash in hopes it would provide
> less latency, but I haven't looked into it yet.  Though, technically, flash
> is a plugin, but it seems to have earned "special status" by the browser
> developers.
>
> On Fri, Feb 6, 2015 at 5:27 AM, St?phane Benoit <stefb at wizzz.net> wrote:
>>
>> Hello,
>>
>> Have you tried something like
>> http://www.schillmania.com/projects/soundmanager2/ for your player ?
>>
>> It looks promising.
>>
>> Regards,
>> St?phane Benoit.
>>
>> Le 05/02/2015 17:30, Tony a ?crit :
>>
>> Thanks.  Here's bit more detail.
>>
>> We have a scientific audio instrument that comes with its own audio
>> driver.  This driver gives us Opus 'frames'.  From a remote location
>> (typically less than 200mS round trip) we would like someone using a browser
>> (without a plugin) to 'hear' this device.  We need the low end-to-end delay
>> as there is an active Video session (separate application) connecting the
>> same two locations.  The remote participant has the ability to mute either
>> feed (video or scientific device).  However, if the device's feed is too far
>> 'delayed' from the video feed, it becomes rather annoying for the remote
>> participant even with the audio portion of the video feed muted.
>>
>> Today, we have a browser plugin.  And we transmit the device's audio data
>> to the remote participant via websockets, wherein the browser feeds the data
>> to the plugin for decoding and playback.
>>
>> Unfortunately, browser plugin's are dying technology.  In fact, chrome is
>> phasing them out later this year.  And Firefox claims they will do the same
>> "soon".  So, we need to find a replacement.
>>
>>
>> On Thu, Feb 5, 2015 at 11:03 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
>> wrote:
>>>
>>> On 02/05/2015 02:45 PM, Tony wrote:
>>> > I have an audio device driver for a live feed that produces Opus
>>> > frames, if I were to use icecast, what sort of real-time delay can I
>>> > expect? 3-5s? 5-10s? more?
>>>
>>> Likely that or more. This highly depends on the client side buffers.
>>> Icecast itself doesn't buffer much and that can be disabled by turning
>>> off the burst-on connect functionality.
>>> HTTP streaming is not "real-time" for most values of real time, it's
>>> still more "real time" than HLS thought, to my surprise.
>>>
>>>
>>> > I've tried using the html5 <audio> tag directly to stream my source,
>>> > but it seems browsers like to queue-up 250K to 500K of audio 'data'
>>> > before they begin playback.  That introduces a 15-30s delay depending
>>> > on browser and the audio compression used.  I'd like an html5
>>> > (plugin-less) solution that introduces no more than a 3-5s delay.
>>>
>>> Yes, you can't control client side buffers for HTTP based streaming to
>>> browsers.
>>>
>>> If you aim for something reliably <<5s without having total control of
>>> the client side, then your best bet is to look at something else. Maybe
>>> WebRTC?
>>>
>>> I'd probably be able to point out something more helpful, but you don't
>>> state your actual use case.
>>>
>>> Generic standard comment:
>>> Most cases where people think they need an Icecast stream to have a
>>> "low" delay are cases where some slight change in approaching the
>>> problem would help. E.g. for collaborative streaming a real time / VoIP
>>> backend that then streams to Icecast. Or in case of a "internet radio" a
>>> question queue instead of trying to achieve "chat like response" over
>>> the air, or rely on listeners actually "dialling in" through e.g. VoIP
>>> for questions.
>>>
>>>
>>> Cheers
>>>
>>> Thomas
>>>
>>>
>>>
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>>
>>
>>
>> --
>> Tony
>>
>>
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Tony
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


From diegobaccino at outlook.com  Mon Feb  9 23:34:56 2015
From: diegobaccino at outlook.com (Diego Baccino)
Date: Mon, 9 Feb 2015 23:34:56 +0000
Subject: [Icecast] =?utf-8?q?IceCast_on_PaaS?=
Message-ID: <SNT405-EAS82E8B90351D29512FB0ACED7270@phx.gbl>

Dear all, 


I'm running IceCast on a VM on Azure. I'd like to migrate this to a Cloud Service. Has anybody found a way to do this? 


Thanks. 






Diego Baccino
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150209/85d7300b/attachment.htm>

From thomas at ruecker.fi  Tue Feb 10 05:22:58 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Tue, 10 Feb 2015 05:22:58 +0000
Subject: [Icecast] IceCast on PaaS
In-Reply-To: <SNT405-EAS82E8B90351D29512FB0ACED7270@phx.gbl>
References: <SNT405-EAS82E8B90351D29512FB0ACED7270@phx.gbl>
Message-ID: <54D995B2.4030400@ruecker.fi>

On 02/09/2015 11:34 PM, Diego Baccino wrote:
> Dear all,
>
> I'm running IceCast on a VM on Azure. I'd like to migrate this to a
> Cloud Service. Has anybody found a way to do this?

Azure /is/ already a cloud service. It will also run just fine on AWS
and DigitalOcean, to name two more.

Can you be more specific about what kind of service you want to migrate
to and for what reason?

As you mention it in the message subject, if you mean PaaS as in
http://en.wikipedia.org/wiki/Platform_as_a_service , then the answer is
"It depends".
PaaS seems to be mostly about running web applications using interpreted
languages. Icecast is neither a web application, nor written in an
interpreted language. There seem to be some types of services that
support binary deployments (openShift), but there it also mentions "web
apps", whatever that means. Also it would be probably significant work
to get Icecast to work, negating pretty much any savings.

While it may be possible to get Icecast running in such a context, I
don't see the benefit of doing so. Virtual machine instances are cheap
and available. Icecast will run on the very smallest of them. If you go
for e.g. CentOS + EPEL and configure automated updates, then your system
will be secure for years, including the odd Icecast upgrade, at almost
no effort.

If you want a managed environment, where some company is responsible for
maintaining it instead of you, then there are plenty of stream hosting
outfits. They tend to be more expensive than those virtual machines
though. Also their "maintenance" isn't often /that/ good either and I
fail to see the value for the premium. I've seen hosters run Icecast
versions from over 5 years ago, with known problems. I can only imagine
what that means how they maintain underlying systems.

Cheers

Thomas



From admin at internetradiohd.com  Sat Feb 14 15:05:54 2015
From: admin at internetradiohd.com (admin at internetradiohd.com)
Date: Sat, 14 Feb 2015 16:05:54 +0100
Subject: [Icecast] Fwd: icecast client problem / forum activate problem
Message-ID: <7aff43511e8c5ac77b8c6b9bf6a472c7@internetradiohd.com>

Hallo Karl,


For some reason i don't get an activate mail after subscribing to the 
icecast forum (http://icecast.imux.net/)
I also tried it a few months ago, this mail address is also the mail 
address for the forum subscription.


---------------------------------------

I also have an problem with android on icecast, With low buffering 
streams for example with 40kbps, i have to wait up to 10 seconds before 
the player plays music.
I haired that the problem might be that the buffering time of the new 
android 4.x versions has been multiplied a view times causing this 
problem.

Do you know and alternative (webplayer) to use for android devices 
where i can set my own buffering time for low bit streams?


with kind regards
Leon Wanningen


From thomas at ruecker.fi  Sun Feb 15 13:09:55 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Sun, 15 Feb 2015 13:09:55 +0000
Subject: [Icecast] Fwd: icecast client problem / forum activate problem
In-Reply-To: <7aff43511e8c5ac77b8c6b9bf6a472c7@internetradiohd.com>
References: <7aff43511e8c5ac77b8c6b9bf6a472c7@internetradiohd.com>
Message-ID: <54E09AA3.8030003@ruecker.fi>

Hi,

On 02/14/2015 03:05 PM, admin at internetradiohd.com wrote:
> For some reason i don't get an activate mail after subscribing to the 
> icecast forum (http://icecast.imux.net/)
> I also tried it a few months ago, this mail address is also the mail 
> address for the forum subscription.

From what we understand the forum doesn't send confirmation mails but
after some time someone activates your account. That's usually a few
days. Xiph.org does not run the forum, it's operated by a 3rd party.

Feel free to ask your question on this mailing list though.
To reliably receive answers to your questions/mails, please register here:

http://lists.xiph.org/mailman/listinfo/icecast



> I also have an problem with android on icecast, With low buffering 
> streams for example with 40kbps, i have to wait up to 10 seconds before 
> the player plays music.
> I haired that the problem might be that the buffering time of the new 
> android 4.x versions has been multiplied a view times causing this 
> problem.

Which app on Android are you referring to?
This is going to be application specific and not determined by the
operating system.


> Do you know and alternative (webplayer) to use for android devices 
> where i can set my own buffering time for low bit streams?

I'm not aware of a way to set the buffer in Android web browsers, or
browsers in general.

I suspect some careful testing to fine-tune this would be necessary.
You'll want to strike the right balance between the size of
burst-on-connect and bandwidth limitations of mobile users.
Please keep in mind, that mobile devices are often going through
connectivity issues, hence a larger buffer (if what you guess happened)
does make sense, otherwise the stream would likely drop or stutter
frequently.
If those client devices with increased buffer size have bandwidth
available that exceeds your stream several times, then burst on-connect
makes sense and should be experimented with.


Cheers

Thomas




From ronlh1 at gmail.com  Mon Feb 16 12:24:06 2015
From: ronlh1 at gmail.com (Ron Harmon)
Date: Mon, 16 Feb 2015 07:24:06 -0500
Subject: [Icecast] listener authentication
Message-ID: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>

I cannot for the life of me get listener authentication to work.
Would it be possible to send me a complete xml file that has listener
authentication setup?

Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150216/1d5e1790/attachment.htm>

From thomas at ruecker.fi  Mon Feb 16 13:18:21 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 16 Feb 2015 13:18:21 +0000
Subject: [Icecast] listener authentication
In-Reply-To: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>
Message-ID: <54E1EE1D.8090708@ruecker.fi>

On 02/16/2015 12:24 PM, Ron Harmon wrote:
> I cannot for the life of me get listener authentication to work.
> Would it be possible to send me a complete xml file that has listener
> authentication setup?

Which kind of listener authentication are you looking for?
- htpasswd file based
- URL auth backend based

I would recommend htpasswd if you are a beginner and want something simple.

What OS/Distro is this on?
Which version of Icecast?

Have you tried looking at the documentation?
http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-authentication

Why I can't just "send a xml file" is, because this depends on a few
things on your system. The questions I posed will help me or others to
give you guidance to get it working correctly though.

Cheers

Thomas



From ronlh1 at gmail.com  Mon Feb 16 15:08:15 2015
From: ronlh1 at gmail.com (Ron Harmon)
Date: Mon, 16 Feb 2015 10:08:15 -0500
Subject: [Icecast] listener authentication
In-Reply-To: <54E1EE1D.8090708@ruecker.fi>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>
	<54E1EE1D.8090708@ruecker.fi>
Message-ID: <CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>

Thomas,

Thanks for your quick reply.
I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
I have read the documentation but I don't understand where to enter this in
the config file.

<mount>
	<mount-name>/example.ogg</mount-name>
	<authentication type="htpasswd">
		<option name="filename" value="myauth"/>
		<option name="allow_duplicate_users" value="0"/>
	</authentication></mount>


On Mon, Feb 16, 2015 at 8:18 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:

> On 02/16/2015 12:24 PM, Ron Harmon wrote:
> > I cannot for the life of me get listener authentication to work.
> > Would it be possible to send me a complete xml file that has listener
> > authentication setup?
>
> Which kind of listener authentication are you looking for?
> - htpasswd file based
> - URL auth backend based
>
> I would recommend htpasswd if you are a beginner and want something simple.
>
> What OS/Distro is this on?
> Which version of Icecast?
>
> Have you tried looking at the documentation?
>
> http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-authentication
>
> Why I can't just "send a xml file" is, because this depends on a few
> things on your system. The questions I posed will help me or others to
> give you guidance to get it working correctly though.
>
> Cheers
>
> Thomas
>
> _______________________________________________
> 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/20150216/214caab2/attachment.htm>

From thomas at ruecker.fi  Mon Feb 16 15:46:08 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 16 Feb 2015 15:46:08 +0000
Subject: [Icecast] listener authentication
In-Reply-To: <CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>	<54E1EE1D.8090708@ruecker.fi>
	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>
Message-ID: <54E210C0.6080509@ruecker.fi>

On 02/16/2015 03:08 PM, Ron Harmon wrote:
> Thanks for your quick reply.
> I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
> I have read the documentation but I don't understand where to enter
> this in the config file.
> |<mount>
> 	<mount-name>/example.ogg</mount-name>
> 	<authentication type="htpasswd">
> 		<option name="filename" value="myauth"/>
> 		<option name="allow_duplicate_users" value="0"/>
> 	</authentication>
> </mount>|
>

You could paste it in the default windows config right below this:
    <!-- Mountpoints
         Only define <mount> sections if you want to use advanced options,
         like alternative usernames or passwords
    -->

Just make sure to NOT put it inside a <!-- --> section. Because then it
would get ignored.
A good editor for the Icecast config would be notepad++, as it nicely
highlights what's active (blue/red) and what's commented out (green).
http://notepad-plus-plus.org/

You can then connect (re)start Icecast, then the source client and
proceed to the admin interface to edit authentication settings.
In case of "/example.ogg" this would be:
http://localhost:8000/admin/manageauth.xsl?mount=/example.ogg
(Please note that this is only available while a  source client is
running on that mountpoint!)

On Windows the file "myauth" gets automatically created after adding the
first user, in the Icecast installation directory, right next to the
config file.
On Linux/Unix/OSX it would need a bit more checking. Actually on Windows
too, but only if you'd run Icecast as a service and under a different user?


Cheers

Thomas


> On Mon, Feb 16, 2015 at 8:18 AM, "Thomas B. R?cker" <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> wrote:
>
>     On 02/16/2015 12:24 PM, Ron Harmon wrote:
>     > I cannot for the life of me get listener authentication to work.
>     > Would it be possible to send me a complete xml file that has
>     listener
>     > authentication setup?
>
>     Which kind of listener authentication are you looking for?
>     - htpasswd file based
>     - URL auth backend based
>
>     I would recommend htpasswd if you are a beginner and want
>     something simple.
>
>     What OS/Distro is this on?
>     Which version of Icecast?
>
>     Have you tried looking at the documentation?
>     http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-authentication
>
>     Why I can't just "send a xml file" is, because this depends on a few
>     things on your system. The questions I posed will help me or others to
>     give you guidance to get it working correctly though.
>
>     Cheers
>
>     Thomas
>
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto: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




From ronlh1 at gmail.com  Tue Feb 17 00:09:23 2015
From: ronlh1 at gmail.com (Ron Harmon)
Date: Mon, 16 Feb 2015 19:09:23 -0500
Subject: [Icecast] listener authentication
In-Reply-To: <54E210C0.6080509@ruecker.fi>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>	<54E1EE1D.8090708@ruecker.fi>	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>
	<54E210C0.6080509@ruecker.fi>
Message-ID: <000301d04a45$fc77e8a0$f567b9e0$@gmail.com>

Thomas,

Sorry to be a pain, but I'm still getting errors when I start Icecast.
StartingIcecast 2.4.1
Using config "icecast.xml" from installation directory ...

Please open http://localhost:8000 or http://127.0.0.1:8000 in your web
browser t
o see the web interface.
[2015-02-16  18:49:49] WARN auth_htpasswd/auth_htpasswd.c failed to check
status
 of myauth

I have attached a copy of my xml file.

Thanks!



-----Original Message-----
From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
Of "Thomas B. R?cker"
Sent: Monday, February 16, 2015 10:46 AM
To: icecast at xiph.org
Subject: Re: [Icecast] listener authentication

On 02/16/2015 03:08 PM, Ron Harmon wrote:
> Thanks for your quick reply.
> I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
> I have read the documentation but I don't understand where to enter 
> this in the config file.
> |<mount>
> 	<mount-name>/example.ogg</mount-name>
> 	<authentication type="htpasswd">
> 		<option name="filename" value="myauth"/>
> 		<option name="allow_duplicate_users" value="0"/>
> 	</authentication>
> </mount>|
>

You could paste it in the default windows config right below this:
    <!-- Mountpoints
         Only define <mount> sections if you want to use advanced options,
         like alternative usernames or passwords
    -->

Just make sure to NOT put it inside a <!-- --> section. Because then it
would get ignored.
A good editor for the Icecast config would be notepad++, as it nicely
highlights what's active (blue/red) and what's commented out (green).
http://notepad-plus-plus.org/

You can then connect (re)start Icecast, then the source client and proceed
to the admin interface to edit authentication settings.
In case of "/example.ogg" this would be:
http://localhost:8000/admin/manageauth.xsl?mount=/example.ogg
(Please note that this is only available while a  source client is running
on that mountpoint!)

On Windows the file "myauth" gets automatically created after adding the
first user, in the Icecast installation directory, right next to the config
file.
On Linux/Unix/OSX it would need a bit more checking. Actually on Windows
too, but only if you'd run Icecast as a service and under a different user



Cheers

Thomas


> On Mon, Feb 16, 2015 at 8:18 AM, "Thomas B. R?cker" <thomas at ruecker.fi 
> <mailto:thomas at ruecker.fi>> wrote:
>
>     On 02/16/2015 12:24 PM, Ron Harmon wrote:
>     > I cannot for the life of me get listener authentication to work.
>     > Would it be possible to send me a complete xml file that has
>     listener
>     > authentication setup?
>
>     Which kind of listener authentication are you looking for?
>     - htpasswd file based
>     - URL auth backend based
>
>     I would recommend htpasswd if you are a beginner and want
>     something simple.
>
>     What OS/Distro is this on?
>     Which version of Icecast?
>
>     Have you tried looking at the documentation?
>     
> http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-auth
> entication
>
>     Why I can't just "send a xml file" is, because this depends on a few
>     things on your system. The questions I posed will help me or others to
>     give you guidance to get it working correctly though.
>
>     Cheers
>
>     Thomas
>
>     _______________________________________________
>     Icecast mailing list
>     Icecast at xiph.org <mailto: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 list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
A non-text attachment was scrubbed...
Name: icecast.xml
Type: text/xml
Size: 8248 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150216/7b756e2c/attachment.xml>

From lion at lion.leolix.org  Tue Feb 17 14:16:49 2015
From: lion at lion.leolix.org (Philipp Schafft)
Date: Tue, 17 Feb 2015 14:16:49 +0000
Subject: [Icecast] listener authentication
In-Reply-To: <000301d04a45$fc77e8a0$f567b9e0$@gmail.com>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>
	<54E1EE1D.8090708@ruecker.fi>
	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>
	<54E210C0.6080509@ruecker.fi>
	<000301d04a45$fc77e8a0$f567b9e0$@gmail.com>
Message-ID: <20150217141652.5E77E127ED@grassland.keep-cool.org>

reflum,


On Mon, 2015-02-16 at 19:09 -0500, Ron Harmon wrote:
> Thomas,
> 
> Sorry to be a pain, but I'm still getting errors when I start Icecast.
> StartingIcecast 2.4.1
> Using config "icecast.xml" from installation directory ...
> 
> Please open http://localhost:8000 or http://127.0.0.1:8000 in your web
> browser t
> o see the web interface.
> [2015-02-16  18:49:49] WARN auth_htpasswd/auth_htpasswd.c failed to check
> status
>  of myauth

Have you created the file?
If not, does server startup work fine? Go to the admin interface with
your browser and after you connected a source the mount should show up.
In that listing there is a link to manage the authentication. If you add
a initial user the file should be created automagically.

> I have attached a copy of my xml file.

By the way: You set <mount-name>/example.m3u</mount-name>. This is a bit
strange for a mount point. .m3u are playlist files. Did you maybe mean
<mount-name>/example</mount-name>?

> Thanks!
> 
> 
> 
> -----Original Message-----
> From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
> Of "Thomas B. R?cker"
> Sent: Monday, February 16, 2015 10:46 AM
> To: icecast at xiph.org
> Subject: Re: [Icecast] listener authentication
> 
> On 02/16/2015 03:08 PM, Ron Harmon wrote:
> > Thanks for your quick reply.
> > I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
> > I have read the documentation but I don't understand where to enter 
> > this in the config file.
> > |<mount>
> > 	<mount-name>/example.ogg</mount-name>
> > 	<authentication type="htpasswd">
> > 		<option name="filename" value="myauth"/>
> > 		<option name="allow_duplicate_users" value="0"/>
> > 	</authentication>
> > </mount>|
> >
> 
> You could paste it in the default windows config right below this:
>     <!-- Mountpoints
>          Only define <mount> sections if you want to use advanced options,
>          like alternative usernames or passwords
>     -->
> 
> Just make sure to NOT put it inside a <!-- --> section. Because then it
> would get ignored.
> A good editor for the Icecast config would be notepad++, as it nicely
> highlights what's active (blue/red) and what's commented out (green).
> http://notepad-plus-plus.org/
> 
> You can then connect (re)start Icecast, then the source client and proceed
> to the admin interface to edit authentication settings.
> In case of "/example.ogg" this would be:
> http://localhost:8000/admin/manageauth.xsl?mount=/example.ogg
> (Please note that this is only available while a  source client is running
> on that mountpoint!)
> 
> On Windows the file "myauth" gets automatically created after adding the
> first user, in the Icecast installation directory, right next to the config
> file.
> On Linux/Unix/OSX it would need a bit more checking. Actually on Windows
> too, but only if you'd run Icecast as a service and under a different user

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150217/96a280f0/attachment.sig>

From thomas at ruecker.fi  Wed Feb 18 07:30:38 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 18 Feb 2015 07:30:38 +0000
Subject: [Icecast] listener authentication
In-Reply-To: <000301d04a45$fc77e8a0$f567b9e0$@gmail.com>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>	<54E1EE1D.8090708@ruecker.fi>	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>	<54E210C0.6080509@ruecker.fi>
	<000301d04a45$fc77e8a0$f567b9e0$@gmail.com>
Message-ID: <54E43F9E.6040504@ruecker.fi>

On 02/17/2015 12:09 AM, Ron Harmon wrote:
> Thomas,
>
> Sorry to be a pain, but I'm still getting errors when I start Icecast.
> StartingIcecast 2.4.1
> Using config "icecast.xml" from installation directory ...
>
> Please open http://localhost:8000 or http://127.0.0.1:8000 in your web
> browser t
> o see the web interface.
> [2015-02-16  18:49:49] WARN auth_htpasswd/auth_htpasswd.c failed to check
> status
>  of myauth
>
> I have attached a copy of my xml file.

There are a couple of things wrong with that.
* The hostname is NOT an URL. If you don't plan to list on dir.xiph.org,
leave it as "localhost" and ignore the warning.
* example.m3u is wrong, as pointed out by Philipp

I've attached a cleaned up icecast.xml file. With everything unused
removed. I've renamed /example.m3u to /example. This will only work if
you plan to stream mp3, if you stream any other codec then it needs the
respective "customary filename extension". Else it will confuse player
software. For Ogg/vorbis it would be /example.ogg and for Opus it would
be /example.opus

I'd suggest you complete the steps I pointed out earlier (connect a
source client to the right mountpoint and then go to admin interface!).

Thomas

>
> Thanks!
>
>
>
> -----Original Message-----
> From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
> Of "Thomas B. R?cker"
> Sent: Monday, February 16, 2015 10:46 AM
> To: icecast at xiph.org
> Subject: Re: [Icecast] listener authentication
>
> On 02/16/2015 03:08 PM, Ron Harmon wrote:
>> Thanks for your quick reply.
>> I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
>> I have read the documentation but I don't understand where to enter 
>> this in the config file.
>> |<mount>
>> 	<mount-name>/example.ogg</mount-name>
>> 	<authentication type="htpasswd">
>> 		<option name="filename" value="myauth"/>
>> 		<option name="allow_duplicate_users" value="0"/>
>> 	</authentication>
>> </mount>|
>>
> You could paste it in the default windows config right below this:
>     <!-- Mountpoints
>          Only define <mount> sections if you want to use advanced options,
>          like alternative usernames or passwords
>     -->
>
> Just make sure to NOT put it inside a <!-- --> section. Because then it
> would get ignored.
> A good editor for the Icecast config would be notepad++, as it nicely
> highlights what's active (blue/red) and what's commented out (green).
> http://notepad-plus-plus.org/
>
> You can then connect (re)start Icecast, then the source client and proceed
> to the admin interface to edit authentication settings.
> In case of "/example.ogg" this would be:
> http://localhost:8000/admin/manageauth.xsl?mount=/example.ogg
> (Please note that this is only available while a  source client is running
> on that mountpoint!)
>
> On Windows the file "myauth" gets automatically created after adding the
> first user, in the Icecast installation directory, right next to the config
> file.
> On Linux/Unix/OSX it would need a bit more checking. Actually on Windows
> too, but only if you'd run Icecast as a service and under a different user?
>
>
> Cheers
>
> Thomas
>
>
>> On Mon, Feb 16, 2015 at 8:18 AM, "Thomas B. R?cker" <thomas at ruecker.fi 
>> <mailto:thomas at ruecker.fi>> wrote:
>>
>>     On 02/16/2015 12:24 PM, Ron Harmon wrote:
>>     > I cannot for the life of me get listener authentication to work.
>>     > Would it be possible to send me a complete xml file that has
>>     listener
>>     > authentication setup?
>>
>>     Which kind of listener authentication are you looking for?
>>     - htpasswd file based
>>     - URL auth backend based
>>
>>     I would recommend htpasswd if you are a beginner and want
>>     something simple.
>>
>>     What OS/Distro is this on?
>>     Which version of Icecast?
>>
>>     Have you tried looking at the documentation?
>>     
>> http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-auth
>> entication
>>
>>     Why I can't just "send a xml file" is, because this depends on a few
>>     things on your system. The questions I posed will help me or others to
>>     give you guidance to get it working correctly though.
>>
>>     Cheers
>>
>>     Thomas
>>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: icecast.xml
Type: text/xml
Size: 2236 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150218/749afa76/attachment.xml>

From ronlh1 at gmail.com  Thu Feb 19 15:03:28 2015
From: ronlh1 at gmail.com (Ron Harmon)
Date: Thu, 19 Feb 2015 10:03:28 -0500
Subject: [Icecast] listener authentication
In-Reply-To: <54E43F9E.6040504@ruecker.fi>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>
	<54E1EE1D.8090708@ruecker.fi>
	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>
	<54E210C0.6080509@ruecker.fi>
	<000301d04a45$fc77e8a0$f567b9e0$@gmail.com>
	<54E43F9E.6040504@ruecker.fi>
Message-ID: <CAA+SqfTuAQ_LnyZfcnZMYN7iGRULHZQwumO2A5iYiwkp8MD1dw@mail.gmail.com>

Thomas and Phillip,

Thanks so much for your help. I have it working now but, is there a way to
setup that when the user clicks on the m3u to play that it would open a
player in the web page instead of creating the m3u file then having to open
it in windows media player as some of the time WMP wont play the file.

Thanks,

Ron

On Wed, Feb 18, 2015 at 2:30 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:

> On 02/17/2015 12:09 AM, Ron Harmon wrote:
> > Thomas,
> >
> > Sorry to be a pain, but I'm still getting errors when I start Icecast.
> > StartingIcecast 2.4.1
> > Using config "icecast.xml" from installation directory ...
> >
> > Please open http://localhost:8000 or http://127.0.0.1:8000 in your web
> > browser t
> > o see the web interface.
> > [2015-02-16  18:49:49] WARN auth_htpasswd/auth_htpasswd.c failed to check
> > status
> >  of myauth
> >
> > I have attached a copy of my xml file.
>
> There are a couple of things wrong with that.
> * The hostname is NOT an URL. If you don't plan to list on dir.xiph.org,
> leave it as "localhost" and ignore the warning.
> * example.m3u is wrong, as pointed out by Philipp
>
> I've attached a cleaned up icecast.xml file. With everything unused
> removed. I've renamed /example.m3u to /example. This will only work if
> you plan to stream mp3, if you stream any other codec then it needs the
> respective "customary filename extension". Else it will confuse player
> software. For Ogg/vorbis it would be /example.ogg and for Opus it would
> be /example.opus
>
> I'd suggest you complete the steps I pointed out earlier (connect a
> source client to the right mountpoint and then go to admin interface!).
>
> Thomas
>
> >
> > Thanks!
> >
> >
> >
> > -----Original Message-----
> > From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On
> Behalf
> > Of "Thomas B. R?cker"
> > Sent: Monday, February 16, 2015 10:46 AM
> > To: icecast at xiph.org
> > Subject: Re: [Icecast] listener authentication
> >
> > On 02/16/2015 03:08 PM, Ron Harmon wrote:
> >> Thanks for your quick reply.
> >> I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
> >> I have read the documentation but I don't understand where to enter
> >> this in the config file.
> >> |<mount>
> >>      <mount-name>/example.ogg</mount-name>
> >>      <authentication type="htpasswd">
> >>              <option name="filename" value="myauth"/>
> >>              <option name="allow_duplicate_users" value="0"/>
> >>      </authentication>
> >> </mount>|
> >>
> > You could paste it in the default windows config right below this:
> >     <!-- Mountpoints
> >          Only define <mount> sections if you want to use advanced
> options,
> >          like alternative usernames or passwords
> >     -->
> >
> > Just make sure to NOT put it inside a <!-- --> section. Because then it
> > would get ignored.
> > A good editor for the Icecast config would be notepad++, as it nicely
> > highlights what's active (blue/red) and what's commented out (green).
> > http://notepad-plus-plus.org/
> >
> > You can then connect (re)start Icecast, then the source client and
> proceed
> > to the admin interface to edit authentication settings.
> > In case of "/example.ogg" this would be:
> > http://localhost:8000/admin/manageauth.xsl?mount=/example.ogg
> > (Please note that this is only available while a  source client is
> running
> > on that mountpoint!)
> >
> > On Windows the file "myauth" gets automatically created after adding the
> > first user, in the Icecast installation directory, right next to the
> config
> > file.
> > On Linux/Unix/OSX it would need a bit more checking. Actually on Windows
> > too, but only if you'd run Icecast as a service and under a different
> user?
> >
> >
> > Cheers
> >
> > Thomas
> >
> >
> >> On Mon, Feb 16, 2015 at 8:18 AM, "Thomas B. R?cker" <thomas at ruecker.fi
> >> <mailto:thomas at ruecker.fi>> wrote:
> >>
> >>     On 02/16/2015 12:24 PM, Ron Harmon wrote:
> >>     > I cannot for the life of me get listener authentication to work.
> >>     > Would it be possible to send me a complete xml file that has
> >>     listener
> >>     > authentication setup?
> >>
> >>     Which kind of listener authentication are you looking for?
> >>     - htpasswd file based
> >>     - URL auth backend based
> >>
> >>     I would recommend htpasswd if you are a beginner and want
> >>     something simple.
> >>
> >>     What OS/Distro is this on?
> >>     Which version of Icecast?
> >>
> >>     Have you tried looking at the documentation?
> >>
> >> http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-auth
> >> entication
> >>
> >>     Why I can't just "send a xml file" is, because this depends on a few
> >>     things on your system. The questions I posed will help me or others
> to
> >>     give you guidance to get it working correctly though.
> >>
> >>     Cheers
> >>
> >>     Thomas
> >>
>
>
> _______________________________________________
> 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/20150219/dbbbf4ba/attachment.htm>

From un at dom.de  Thu Feb 19 15:17:33 2015
From: un at dom.de (unosonic)
Date: Thu, 19 Feb 2015 16:17:33 +0100
Subject: [Icecast] listener authentication
In-Reply-To: <CAA+SqfTuAQ_LnyZfcnZMYN7iGRULHZQwumO2A5iYiwkp8MD1dw@mail.gmail.com>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>
	<54E1EE1D.8090708@ruecker.fi>
	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>
	<54E210C0.6080509@ruecker.fi>
	<000301d04a45$fc77e8a0$f567b9e0$@gmail.com>
	<54E43F9E.6040504@ruecker.fi>
	<CAA+SqfTuAQ_LnyZfcnZMYN7iGRULHZQwumO2A5iYiwkp8MD1dw@mail.gmail.com>
Message-ID: <20150219151733.GC6039@aporee.org>

Ron Harmon:
> Thomas and Phillip,
> 
> Thanks so much for your help. I have it working now but, is there a way to
> setup that when the user clicks on the m3u to play that it would open a
> player in the web page instead of creating the m3u file then having to open

check for example this one:

http://jplayer.org/latest/demo-08/

works nice for me

but of course it wouldn't "open" on clicking the .m3u, since it's the job 
of your browser to decide what to do with that extension.

--u




From thomas at ruecker.fi  Mon Feb 23 05:49:24 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 23 Feb 2015 05:49:24 +0000
Subject: [Icecast] listener authentication
In-Reply-To: <CAA+SqfTuAQ_LnyZfcnZMYN7iGRULHZQwumO2A5iYiwkp8MD1dw@mail.gmail.com>
References: <CAA+SqfTpvFZN1j9TYjPR3oGmaSuhYLEY=NNAOn2YDWwZAr5TYg@mail.gmail.com>	<54E1EE1D.8090708@ruecker.fi>	<CAA+SqfRtnZ_X+BuafR+Dz4J-tFQc6M2Kszv9VAB5cXuUORz7Vg@mail.gmail.com>	<54E210C0.6080509@ruecker.fi>	<000301d04a45$fc77e8a0$f567b9e0$@gmail.com>	<54E43F9E.6040504@ruecker.fi>
	<CAA+SqfTuAQ_LnyZfcnZMYN7iGRULHZQwumO2A5iYiwkp8MD1dw@mail.gmail.com>
Message-ID: <54EABF64.7090208@ruecker.fi>

On 02/19/2015 03:03 PM, Ron Harmon wrote:
> Thomas and Phillip,
>
> Thanks so much for your help. I have it working now but, is there a
> way to setup that when the user clicks on the m3u to play that it
> would open a player in the web page instead of creating the m3u file
> then having to open it in windows media player as some of the time WMP
> wont play the file.

Just use an <audio> element or a javascript player that leverages this.
The latter ones tend to also have a fallback to some flash object in
case the browser doesn't support the format.

Starting with version 2.4 the officially supported formats also get a
<audio> object in the status page. Keep in mind though, that the status
page is not meant to be a focal point for end users, usually you'd embed
the player into your homepage or such.

Cheers

Thomas


> On Wed, Feb 18, 2015 at 2:30 AM, "Thomas B. R?cker" <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> wrote:
>
>     On 02/17/2015 12:09 AM, Ron Harmon wrote:
>     > Thomas,
>     >
>     > Sorry to be a pain, but I'm still getting errors when I start
>     Icecast.
>     > StartingIcecast 2.4.1
>     > Using config "icecast.xml" from installation directory ...
>     >
>     > Please open http://localhost:8000 or http://127.0.0.1:8000 in
>     your web
>     > browser t
>     > o see the web interface.
>     > [2015-02-16  18:49:49] WARN auth_htpasswd/auth_htpasswd.c failed
>     to check
>     > status
>     >  of myauth
>     >
>     > I have attached a copy of my xml file.
>
>     There are a couple of things wrong with that.
>     * The hostname is NOT an URL. If you don't plan to list on
>     dir.xiph.org <http://dir.xiph.org>,
>     leave it as "localhost" and ignore the warning.
>     * example.m3u is wrong, as pointed out by Philipp
>
>     I've attached a cleaned up icecast.xml file. With everything unused
>     removed. I've renamed /example.m3u to /example. This will only work if
>     you plan to stream mp3, if you stream any other codec then it
>     needs the
>     respective "customary filename extension". Else it will confuse player
>     software. For Ogg/vorbis it would be /example.ogg and for Opus it
>     would
>     be /example.opus
>
>     I'd suggest you complete the steps I pointed out earlier (connect a
>     source client to the right mountpoint and then go to admin
>     interface!).
>
>     Thomas
>
>     >
>     > Thanks!
>     >
>     >
>     >
>     > -----Original Message-----
>     > From: icecast-bounces at xiph.org <mailto:icecast-bounces at xiph.org>
>     [mailto:icecast-bounces at xiph.org
>     <mailto:icecast-bounces at xiph.org>] On Behalf
>     > Of "Thomas B. R?cker"
>     > Sent: Monday, February 16, 2015 10:46 AM
>     > To: icecast at xiph.org <mailto:icecast at xiph.org>
>     > Subject: Re: [Icecast] listener authentication
>     >
>     > On 02/16/2015 03:08 PM, Ron Harmon wrote:
>     >> Thanks for your quick reply.
>     >> I am looking at htpasswd. I am using 2.41 on Windows 7 with BUTT.
>     >> I have read the documentation but I don't understand where to enter
>     >> this in the config file.
>     >> |<mount>
>     >>      <mount-name>/example.ogg</mount-name>
>     >>      <authentication type="htpasswd">
>     >>              <option name="filename" value="myauth"/>
>     >>              <option name="allow_duplicate_users" value="0"/>
>     >>      </authentication>
>     >> </mount>|
>     >>
>     > You could paste it in the default windows config right below this:
>     >     <!-- Mountpoints
>     >          Only define <mount> sections if you want to use
>     advanced options,
>     >          like alternative usernames or passwords
>     >     -->
>     >
>     > Just make sure to NOT put it inside a <!-- --> section. Because
>     then it
>     > would get ignored.
>     > A good editor for the Icecast config would be notepad++, as it
>     nicely
>     > highlights what's active (blue/red) and what's commented out
>     (green).
>     > http://notepad-plus-plus.org/
>     >
>     > You can then connect (re)start Icecast, then the source client
>     and proceed
>     > to the admin interface to edit authentication settings.
>     > In case of "/example.ogg" this would be:
>     > http://localhost:8000/admin/manageauth.xsl?mount=/example.ogg
>     > (Please note that this is only available while a  source client
>     is running
>     > on that mountpoint!)
>     >
>     > On Windows the file "myauth" gets automatically created after
>     adding the
>     > first user, in the Icecast installation directory, right next to
>     the config
>     > file.
>     > On Linux/Unix/OSX it would need a bit more checking. Actually on
>     Windows
>     > too, but only if you'd run Icecast as a service and under a
>     different user?
>     >
>     >
>     > Cheers
>     >
>     > Thomas
>     >
>     >
>     >> On Mon, Feb 16, 2015 at 8:18 AM, "Thomas B. R?cker"
>     <thomas at ruecker.fi <mailto:thomas at ruecker.fi>
>     >> <mailto:thomas at ruecker.fi <mailto:thomas at ruecker.fi>>> wrote:
>     >>
>     >>     On 02/16/2015 12:24 PM, Ron Harmon wrote:
>     >>     > I cannot for the life of me get listener authentication
>     to work.
>     >>     > Would it be possible to send me a complete xml file that has
>     >>     listener
>     >>     > authentication setup?
>     >>
>     >>     Which kind of listener authentication are you looking for?
>     >>     - htpasswd file based
>     >>     - URL auth backend based
>     >>
>     >>     I would recommend htpasswd if you are a beginner and want
>     >>     something simple.
>     >>
>     >>     What OS/Distro is this on?
>     >>     Which version of Icecast?
>     >>
>     >>     Have you tried looking at the documentation?
>     >>
>     >>
>     http://icecast.org/docs/icecast-2.4.1/auth.html#htpasswd-listener-auth
>     >> entication
>     >>
>     >>     Why I can't just "send a xml file" is, because this depends
>     on a few
>     >>     things on your system. The questions I posed will help me
>     or others to
>     >>     give you guidance to get it working correctly though.
>     >>
>     >>     Cheers
>     >>
>     >>     Thomas
>     >>
>



From thomas at ruecker.fi  Mon Feb 23 06:26:16 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 23 Feb 2015 06:26:16 +0000
Subject: [Icecast] IceCast Server (2.3.2) Limits? Disconnections due to
 user and memory?
In-Reply-To: <mcapbb$84c$1@ger.gmane.org>
References: <mcapbb$84c$1@ger.gmane.org>
Message-ID: <54EAC808.2090701@ruecker.fi>

Hi,

please see the inline comments.


On 02/21/2015 08:21 PM, Dean Sauer wrote:
> I have a VPS on OpenVZ 2GB RAM / 2GB Burst, and Ubuntu 12.04 64b server
>
> I use Icecast 2.3.2 <snip />
>
> As posted in previous threads I am seeing a situation reoccur where the 
> sources and clients ALL GET DUMPED...ALL AT ONCE.

We'd need error logs from such an incident, perferably at  log level 4.
Also dmesg and syslog from that time would be helpful


> During this time clients get dumped to a source specific MP3 file, one 
> for each of the sources that plays till the source comes back. At times 
> the clients can connect to this, at times VLC etc. can't connect when it 
> should be playing that MP3 file. There is ONE MP3 file for EACH source. 
> I've found having ONE for all sources And Icecast can't figure out where 
> to send clients back to after the source comes back.. so I have one for 
> each source now.

Yes that is correct. A client isn't bound to a certain origin mountpoint
and if there are two mounts that use the same fallback with override,
then the first one to connect gets all the listeners from the fallback.
That's how it is intended and having separate fallbacks is the correct
approach if you don't want this to happen.


> I've had a SSH session connected since the last incident, it didn't drop, 
> BUT the way these SSH sessions are done may not be an accurate gauge as 
> they go in via some differing than the server IP... this CONNECTION DOES 
> seem to lag in getting data.. as I have top running in 24/7 right now.
>
> Then there is this gyration of sources and clients trying to reconnect...
>
> After looking at things... the only conclusion I can find is that 2GB is 
> NOT ENOUGH for the few sources but with LARGE CLIENTS

What are "LARGE CLIENTS"?
How do you reckon that it's a memory problem if Icecast isn't killed by OOM?
What's its RSS/VSS during that sort of load?


> There are 11 SOURCES... the latest incident of this situation finds that 
> 3 of the sources had from 45-100 clients each.

That's rather mundane load for an Icecast server.


> IS this the limit for a 2GB VPS?

Most certainly not.


> Comments, ideas???? 
>
> I at the point that I am going to have to 
>
>
> 1) Find a solution on this host - comments, ideas???
>
> Note: for this VPS host, 2GB RAM/2GB BURST is their MAX CONFIG. They 
> refuse to budge on this... 

I don't see staying with this particular virtualization technology and
focusing on RAM as beneficial to resolving this.
I actually suspect that it's openVZ with it's rather old and problem
prone "virtualization" that is at the root of this. Or it's just a
highly overcommitted host and you get squeezed out by one of the other
tennants. Either way moving on is the answer.


> 2)find a different host,

I am quite sure, that you'll find switching to a host that uses a more
mature virtualization technology will help.
As you want to stay with 2.3.2, I'd suggest to find one that has Ubuntu
12.04 or another distribution that carries this version by default (e.g.
Debian 7).
I'd expect most of the large ones to support that, but as I haven't
tried any of them I can't point to a specific one.


Thomas



From simone.dalmaso at gmail.com  Mon Feb 23 14:26:10 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Mon, 23 Feb 2015 15:26:10 +0100
Subject: [Icecast] upgrading icecast to 2.4.1
Message-ID: <54EB3882.1080202@gmail.com>

Hello,
I'm a ubuntu 12.04 user.
I'm currently running icecast 2.3.2 installed from ubuntu apt-get,  with 
Liquidsoap 1.1.1 that instead is compiled by myself.
I'd like to upgrade to icecast 2.4.1, but since I have a webradio and 
all work fine, I'd like to know if there is a procedure or a tutorial on 
how to upgrade from 2.3.2 to 2.4.1.
Which steps  should I follow?
Thank you!





From thomas at ruecker.fi  Mon Feb 23 16:06:06 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 23 Feb 2015 16:06:06 +0000
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EB3882.1080202@gmail.com>
References: <54EB3882.1080202@gmail.com>
Message-ID: <54EB4FEE.8060900@ruecker.fi>

On 02/23/2015 02:26 PM, Simone Dal Maso wrote:
> Hello,
> I'm a ubuntu 12.04 user.
> I'm currently running icecast 2.3.2 installed from ubuntu apt-get,  with 
> Liquidsoap 1.1.1 that instead is compiled by myself.

OK, that's from the Icecast side an easy situation.

> I'd like to upgrade to icecast 2.4.1, but since I have a webradio and 
> all work fine, I'd like to know if there is a procedure or a tutorial on 
> how to upgrade from 2.3.2 to 2.4.1.
> Which steps  should I follow?

It is fairly easy, you add the official Icecast repository (it's like a
PPA):
http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_12.04/
The signing key is:
http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_12.04/Release.key


This line will add the official Icecast repository for Ubuntu 12.04 to
your system:
sudo sh -c "echo deb
http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/ ./
>>/etc/apt/sources.list.d/icecast.list"

This line will add the GPG signing key to your system:|
wget -qO -
||http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_12.04/Release.key
| sudo apt-key add -|

Once you've done that you should be able to just:
sudo apt-get update
sudo apt-get install icecast2

It should now offer the 2.4.1 package. Upgrading should "just work" and
your original config should be kept.

In case it doesn't work or you want to remove the repository, this will
get you back to the original Ubuntu package:
sudo rm /etc/apt/sources.list.d/icecast.list
sudo apt-get install icecast2/trusty

There should be no changes necessary to your Liquidsoap setup.


Cheers

Thomas



From simone.dalmaso at gmail.com  Mon Feb 23 16:41:02 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Mon, 23 Feb 2015 17:41:02 +0100
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EB4FEE.8060900@ruecker.fi>
References: <54EB3882.1080202@gmail.com> <54EB4FEE.8060900@ruecker.fi>
Message-ID: <54EB581E.8010601@gmail.com>

Il 23/02/2015 17:06, "Thomas B. R?cker" ha scritto:
> OK, that's from the Icecast side an easy situation.

really thank you very much!
I will make this operation tomorrow, but it seems easy.
Still thanks.



From thomas at ruecker.fi  Mon Feb 23 16:46:31 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 23 Feb 2015 16:46:31 +0000
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EB581E.8010601@gmail.com>
References: <54EB3882.1080202@gmail.com> <54EB4FEE.8060900@ruecker.fi>
	<54EB581E.8010601@gmail.com>
Message-ID: <54EB5967.6050000@ruecker.fi>

On 02/23/2015 04:41 PM, Simone Dal Maso wrote:
> Il 23/02/2015 17:06, "Thomas B. R?cker" ha scritto:
>> OK, that's from the Icecast side an easy situation.
> really thank you very much!
> I will make this operation tomorrow, but it seems easy.
> Still thanks.

Good luck, let us know if you run into problems.

Also, seeing how Thunderbird totally butchered up those commands,
attached please find a script that contains those. Or run it directly
"bash add-icecast-repo". The script is specific to Ubuntu 12.04.


Cheers

Thomas
-------------- next part --------------
#!/bin/sh
echo Adding official Icecast repository for Ubuntu 12.04
sudo sh -c "echo deb http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_12.04/ ./ >>/etc/apt/sources.list.d/icecast.list"

echo Importing GPG key for official Icecast repository
wget -qO - http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_12.04/Release.key | sudo apt-key add -


From simone.dalmaso at gmail.com  Tue Feb 24 08:51:40 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Tue, 24 Feb 2015 09:51:40 +0100
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EB5967.6050000@ruecker.fi>
References: <54EB3882.1080202@gmail.com>
	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>
	<54EB5967.6050000@ruecker.fi>
Message-ID: <54EC3B9C.5010707@gmail.com>

Il 23/02/2015 17:46, "Thomas B. R?cker" ha scritto:

> Also, seeing how Thunderbird totally butchered up those commands,

Yes, great power of email client of 2015!
Anyway I solved adjusting commands manually, now I have icecast 2.4.1 
running on my server, and I can work on building a script that shows me 
the current song on webpage of my radio.
Thanks!







From thomas at ruecker.fi  Tue Feb 24 12:56:11 2015
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Tue, 24 Feb 2015 12:56:11 +0000
Subject: [Icecast] IceCast Server (2.3.2) Limits? Disconnections due to
 user and memory?
In-Reply-To: <mcho06$7c5$1@ger.gmane.org>
References: <mcapbb$84c$1@ger.gmane.org> <54EAC808.2090701@ruecker.fi>
	<mcho06$7c5$1@ger.gmane.org>
Message-ID: <54EC74EB.6010607@ruecker.fi>

On 02/24/2015 11:40 AM, Dean Sauer wrote:
> On Mon, 23 Feb 2015 06:26:16 +0000, Thomas B. R?cker wrote:
>
>> We'd need error logs from such an incident, perferably at  log level 4.
> The error log from Icecast is as follows when this happened last:
> [2015-02-15  16:24:08] DBUG source/get_next_buffer last 1424035387, 
> timeout 60, now 1424035448
> [2015-02-15  16:24:08] WARN source/get_next_buffer Disconnecting source 
> due to socket timeout
> [2015-02-15  16:24:08] INFO source/source_shutdown Source "/feed" exiting
> [2015-02-15  16:24:08] DBUG source/source_run_script Starting command /
> etc/icecast2/feeddown4.sh
> [2015-02-15  16:24:08] DBUG source/get_next_buffer last 1424035387, 
> timeout 60, now 1424035448
> [2015-02-15  16:24:08] WARN source/get_next_buffer Disconnecting source 
> due to socket timeout
> [2015-02-15  16:24:08] INFO source/source_shutdown Source "/feed" exiting
> [2015-02-15  16:24:08] DBUG source/source_run_script Starting command /
> etc/icecast2/feeddown4usc.sh
> [2015-02-15  16:24:08] DBUG source/get_next_buffer last 1424035387, 
> timeout 60, now 1424035448
> [2015-02-15  16:24:08] WARN source/get_next_buffer Disconnecting source 
> due to socket timeout
> [2015-02-15  16:24:08] INFO source/source_shutdown Source "/feed" exiting
> [2015-02-15  16:24:08] DBUG source/get_next_buffer last 1424035387, 
> timeout 60, now 1424035448
> [2015-02-15  16:24:08] WARN source/get_next_buffer Disconnecting source 
> due to socket timeout
> [2015-02-15  16:24:08] INFO source/source_shutdown Source "/feed" exiting
> [2015-02-15  16:24:08] DBUG source/source_run_script Starting command /
> etc/icecast2/kingkendown.sh
> [2015-02-15  16:24:08] DBUG source/source_run_script Starting command /
> etc/icecast2/feeddown4.sh
> [2015-02-15  16:24:08] DBUG source/get_next_buffer last 1424035387, 
> timeout 60, now 1424035448
> [2015-02-15  16:24:08] WARN source/get_next_buffer Disconnecting source 
> due to socket timeout
> [2015-02-15  16:24:08] INFO source/source_shutdown Source "/feed" exiting
> [2015-02-15  16:24:08] DBUG source/source_run_script Starting command /
> etc/icecast2/feeddown4.sh
> [2015-02-15  16:24:08] DBUG source/get_next_buffer last 1424035387, 
> timeout 60, now 1424035448
> [2015-02-15  16:24:08] WARN source/get_next_buffer Disconnecting source 
> due to socket timeout
> [2015-02-15  16:24:08] INFO source/source_shutdown Source "/feed" exiting
> [2015-02-15  16:24:08] DBUG source/source_run_script Starting command /
> etc/icecast2/kingkendown.sh
> [2015-02-15  16:24:08] DBUG stats/modify_node_event update node listeners 
> (106)

I wonder why it claims, that the source shutting down is "/feed" every
time, that's highly suspicious.
Especially as it seems to run a different script for some of them.
Please provide icecast.xml with passwords removed.


> Doubtful I get this either...
>
> There also is the "spawning" issue...I've accessed what if/is causing 
> Icecast to "spawn" new server instances... as I recall the replies are 
> that Icecast CAN NOT SPAWN new instances... 

Correct. If you see other processes, then this might only be related to
the scripts you spawn from inside Icecast.
I'd recommend to avoid long running scripts in general. If you need
something long lived, spawn an own process for that, which is not
attached to the original script.


> Before I rebooted this thing there were like 30+ instances of Icecast 
> running... after a week there are now 5

What are you doing inside the scripts that you spawn?
Do those scripts terminate cleanly? How long do they run?
Can you attach such a script for further analysis?


> top - 06:13:09 up 8 days, 18:25,  0 users,  load average: 0.00, 0.03, 0.00
> Tasks:  15 total,   1 running,  14 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.1%us,  0.5%sy,  0.0%ni, 99.4%id,  0.0%wa,  0.0%hi,  0.0%si,  
> 0.0%st
> Mem:   2097152k total,    83800k used,  2013352k free,        0k buffers
> Swap:  2097152k total,        0k used,  2097152k free,    36984k cached
>
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  
> COMMAND                                                                                                                
>   668 icecast2  20   0 1841m  11m 1480 S    3  0.6 698:52.42 
> icecast2                                                                                                               
>     1 root      20   0 23768  880  504 S    0  0.0   0:01.76 
> init                                                                                                                   
>     2 root      20   0     0    0    0 S    0  0.0   0:00.00 
> kthreadd/54931                                                                                                         
>     3 root      20   0     0    0    0 S    0  0.0   0:00.00 
> khelper/54931                                                                                                          
>   221 root      20   0 49992 1240  628 S    0  0.1   0:10.51 
> sshd                                                                                                                   
>   347 root      20   0 19068  600  396 S    0  0.0   0:01.24 
> cron                                                                                                                   
>   349 root      20   0  6408  624  464 S    0  0.0   0:10.64 
> syslogd                                                                                                                
>   646 Debian-e  20   0 47480  880  432 S    0  0.0   0:00.21 
> exim4                                                                                                                  
>   732 root      20   0 36012  332   40 S    0  0.0   0:19.86 
> vzctl                                                                                                                  
>   733 root      20   0 18272 1152  444 S    0  0.1   0:00.09 
> bash                                                                                                                   
>  1082 icecast2  20   0 1647m 6152  104 S    0  0.3   0:00.00 
> icecast2                                                                                                               
>  4009 icecast2  20   0 1841m  10m  112 S    0  0.5   0:00.00 
> icecast2                                                                                                               
>  8120 icecast2  20   0 1776m 9036  104 S    0  0.4   0:00.00 
> icecast2                                                                                                               
>  8244 root      20   0 17160  892  632 R    0  0.0   4:52.08 
> top                                                                                                                    
> 29360 icecast2  20   0 1841m  10m  112 S    0  0.5   0:00.00 
> icecast2                                                                                                               
>


A Vss of 1841M is highly suspicious. In combination with an Rss of <10M
and almost all memory being listed as free it looks like a massive
memory allocation of some sort.

Have you modified any of the buffer or burst parameters in Icecast? Can
you provide your icecast.xml (passwords removed) as an attachment?

This might also be related to a security issue that was discovered and
fixed last year:
https://trac.xiph.org/ticket/2089
Fix was part of the 2.4.1 release of Icecast. I am not aware if the fix
was backported by Debian/Ubuntu and released to their users, you'd need
to check with Ubuntu. At least Fedora and CentOS/EPEL upgraded to 2.4.1
as the result.


>> I don't see staying with this particular virtualization technology and
>> focusing on RAM as beneficial to resolving this.
>> I actually suspect that it's openVZ with it's rather old and problem
>> prone "virtualization" that is at the root of this. Or it's just a
>> highly overcommitted host and you get squeezed out by one of the other
>> tennants. Either way moving on is the answer.
>
> One of two things is going on here:
>
> 1) Network filtering external to the host.. I know this host has 
> something that does this on ALL clients for somethings.. they "leak" this 
> out if you dig about them... then they offer DDOS services, which I don't 
> use...
>
> BUT...
>
> I think after the past few days... something causes Icecast to FAIL, thus 
> it disappears.. respawns some how..

Icecast does not respawn by itself and none of the distributions I know
restart Icecast if it fails. Though the latter might be changing in the
future with the spread of systemd. Ubuntu 12.04 certainly doesn't in the
default installation.


>  and then clients which THINK they are 
> connected are NOT CONNECTED to the NEW SPAWN'd server thus are "offline" 
> unavailable...even though the source(s) think they are connected.

Looking at the start time/date of the Icecast process using e.g. "ps
aux" should answer when it was started.
Identifying the true Icecast server process might be tricky given those
ghosts. It would help to turn on the pid-file option of Icecast and
check the pid-file for the real PID.


> Any one know what scripts that the Icecast package in 12.04 64b installs 
> that starts on boot Icecast? I may nuke that, and see if it kills the 
> respawns... or even more so icecast has to be started manually... a PITA 
> but there is something to this respawn issue 

/etc/init.d/icecast2 is ONLY executed on boot/shutdown or manually.
There should be no need WHATSOEVER to mess with this.
I'd recommend cleaning up the on-connect/disconnect scripting situation
first.


>> I am quite sure, that you'll find switching to a host that uses a more
>> mature virtualization technology will help.
>> As you want to stay with 2.3.2, I'd suggest to find one that has Ubuntu
>> 12.04 
> A new host is on the way.

Let us know how that goes.



Thomas



From thomas at ruecker.fi  Tue Feb 24 14:53:13 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Tue, 24 Feb 2015 14:53:13 +0000
Subject: [Icecast] 2.4.1 and Meta update from DIFFERING IP's - Status?
In-Reply-To: <mci1ad$acp$1@ger.gmane.org>
References: <mci1ad$acp$1@ger.gmane.org>
Message-ID: <54EC9059.5030103@ruecker.fi>

On 02/24/2015 02:19 PM, Dean Sauer wrote:
> In looking at the archives... on this.. 
>
> Does 2.4.1 allow the METADATA UPDATE from DIFFERING IP's with SOURCE 
> CREDS?

no.

This has been addressed as part of the authentication system rewrite
towards 2.5.0.
You will be able to even do such things as defining a user who can
_only_ update metadata for a certain stream.

We're currently going through a beta version phase. While we do provide
packages for those, we do not recommend them for production use.

The 2.5 final release is expected during the second half of 2015.

> I am not finding the message(s) I thought were there that outlined 
> this....or is this still a WIP??? I remember discussion about it being 
> worked/added and just can't seem to find the outcome in my arhives... 

We verified if there is a bug in returning a HTTP 200 to a request.
https://trac.xiph.org/ticket/2037
The answer is: There is no bug, we return 400 to a raw request and 200
plus an human readable error message to a web request. Which means the
bug should have been closed already, I'll be doing that later today.

Adding an option to disable the restriction in 2.4.1 was not considered
due to the rewrite that was going to happen for 2.5.0 around the same time.

I'd recommend a simple web interface wrapper to work around this
restriction:
Simple form that requires authentication, which can be managed by you
freely.
This form then triggers a request to the Icecast metadata API using
admin credentials:
|http://example.org:8000/admin/metadata?mount=/mystream&mode=updinfo&song=This+has+been+updated|
This way you can restrict access on a per mount level. Should be rather
simple in a server side scripting language of your choice.

If you want to modify 2.4.1, then you could always revert this commit:
https://trac.xiph.org/changeset/15264
changing the two if statements from:
if (same_ip && plugin && plugin->set_tag)
back to:
if (plugin && plugin->set_tag)
Then rebuild Icecast.


Thomas




From thomas at ruecker.fi  Tue Feb 24 16:08:22 2015
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Tue, 24 Feb 2015 16:08:22 +0000
Subject: [Icecast] IceCast Server (2.3.2) Limits? Disconnections due to
 user and memory?
In-Reply-To: <pan$3de2d$4545b49c$9634280d$184be5fe$1@gmail.com>
References: <mcapbb$84c$1@ger.gmane.org>
	<54EAC808.2090701@ruecker.fi>	<mcho06$7c5$1@ger.gmane.org>
	<54EC74EB.6010607@ruecker.fi>
	<pan$3de2d$4545b49c$9634280d$184be5fe$1@gmail.com>
Message-ID: <54ECA1F6.7010601@ruecker.fi>

On 02/24/2015 03:30 PM, Dean Sauer wrote:
> On Tue, 24 Feb 2015 12:56:11 +0000, Thomas B. R?cker wrote:
>
>> Have you modified any of the buffer or burst parameters in Icecast? Can
>> you provide your icecast.xml (passwords removed) as an attachment?
>>
> The list seems to dislike xml so hopefully this won't get stripped.
>

You're posting through the gmane NNTP interface using yenc encoding.
That somehow doesn't work at all in this combination. Something along
the way just eats everything.

Could you please email those files to me directly using my personal
email address, as regular mail attachments?

Thanks

Thomas


From victormukti at gmail.com  Wed Feb 25 00:30:44 2015
From: victormukti at gmail.com (Victor Mukti)
Date: Wed, 25 Feb 2015 07:30:44 +0700
Subject: [Icecast] Unreg
Message-ID: <5mcgq0l21vhc1pyuijjmjdrr.1424824244496@email.android.com>




Terkirim dari Samsung Mobile.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150225/3c3e834d/attachment.htm>

From simone.dalmaso at gmail.com  Wed Feb 25 08:42:02 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Wed, 25 Feb 2015 09:42:02 +0100
Subject: [Icecast] where can I find a "now playing" scripts
Message-ID: <54ED8ADA.7010505@gmail.com>

Hello,
I'm quite amazed that, after researching in Google, I can't find a 
simple script that use Icecast to provide simple statistics like song 
title, song author and a little history of the songs of my radio.
Oh, I found a php script that parses the xhtml page and it is not 
recommended by Icecast team.
Should I restart learning how search on Google or do you know where can 
I find a script that I can embed on my website?
Thank you!




From thomas at ruecker.fi  Wed Feb 25 09:34:52 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 25 Feb 2015 09:34:52 +0000
Subject: [Icecast] where can I find a "now playing" scripts
In-Reply-To: <54ED8ADA.7010505@gmail.com>
References: <54ED8ADA.7010505@gmail.com>
Message-ID: <54ED973C.5010608@ruecker.fi>

Hi,

On 02/25/2015 08:42 AM, Simone Dal Maso wrote:
> Hello,
> I'm quite amazed that, after researching in Google, I can't find a 
> simple script that use Icecast to provide simple statistics like song 
> title, song author and a little history of the songs of my radio.

In the past we recommended writing custom XSLT code to tailor output to
your specific needs.
There are some old and horrible examples that I did:
http://ruecker.fi/foss/icecast/xslt/

XSLT is not necessary everybody's favorite though, so there isn't /that/
much around for it.


> Oh, I found a php script that parses the xhtml page and it is not 
> recommended by Icecast team.

Yes, scraping HTML is bad, as we don't see the web interface as an API
and change it, even within minor releases.
Case in point: 2.5 is going to have a completely new and shiny web
interface.


> Should I restart learning how search on Google or do you know where can 
> I find a script that I can embed on my website?

No, your finding is pretty much correct, right now you can probably
mostly find crap.
BUT I have good news for you! In Icecast 2.4.1 we released a fully
working JSON API and make it available as CORS ACAO * (if you use the
default config or copy the HTTP-header part from it).
So you can just head over to
http://stream.example.org:8000/status-json.xsl and use the available
data directly from your website's JavaScript.
Bonus points if you post your Javascript somewhere publicly and let me
know, so I can link to it from icecast.org.
It's also being worked into our documentation:
http://icecast.org/docs/icecast-trunk/server-stats.html#json

Cheers

Thomas



From simone.dalmaso at gmail.com  Wed Feb 25 10:49:30 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Wed, 25 Feb 2015 11:49:30 +0100
Subject: [Icecast] icecast and proxy
Message-ID: <54EDA8BA.60602@gmail.com>

Hello,
sorry for all these questions, but there is a great news, this is the 
last! ... of the day :-)

So:
I run nvRadio on port 8000, that is a problem for all people that are at 
work, behind firewall or protected environment.
So, I thought that a proxy can be the solution for streaming on port 80.
I enabled the apache2 proxy and, yes, if I type:
www.nvapple.it/stream

the stream  is ok also now that I am on my office, on port80!

The problem is that if I look at the IP of people that are connected, 
visiting icecast's admin panel, I see always the ip of my machine, and 
it is unfortunately right, because they are listening through apache2 
proxy.

On my proxy.conf, I put:
***
  ProxyPass /stream http://www.nvapple.it:8000/stream 
 
 



  ProxyPassReverse /stream http://www.nvapple.it:8000/stream 
 
 

***
Do you know other solutions that can show me the ip of people or this is 
the right one?
Thank you!




From thomas at ruecker.fi  Wed Feb 25 11:09:16 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 25 Feb 2015 11:09:16 +0000
Subject: [Icecast] icecast and proxy
In-Reply-To: <54EDA8BA.60602@gmail.com>
References: <54EDA8BA.60602@gmail.com>
Message-ID: <54EDAD5C.2030804@ruecker.fi>

Hi,

On 02/25/2015 10:49 AM, Simone Dal Maso wrote:
> Hello,
> sorry for all these questions, but there is a great news, this is the 
> last! ... of the day :-)
>
> So:
> I run nvRadio on port 8000, that is a problem for all people that are at 
> work, behind firewall or protected environment.
> So, I thought that a proxy can be the solution for streaming on port 80.
> I enabled the apache2 proxy and, yes, if I type:
> www.nvapple.it/stream

The answer is:
DO NOT UNLESS YOU FULLY UNDERSTAND THE IMPLICATIONS!
If you have to ask yourself "what are the implications?", you don't.
You can easily kill your web server and other things can break too.
Icecast explicitly does NOT support being reverse proxied!
We recommend to bind Icecast directly (start as root, use changowner) to
port 80 on a separate IP address.

> the stream  is ok also now that I am on my office, on port80!
>
> The problem is that if I look at the IP of people that are connected, 
> visiting icecast's admin panel, I see always the ip of my machine, and 
> it is unfortunately right, because they are listening through apache2 
> proxy. [...]
> Do you know other solutions that can show me the ip of people or this is 
> the right one?

As Icecast does not support being reverse proxied, it will only show and
log the IP of the reverse proxy.

We are considering to make Icecast more reverse proxy friendly, but the
inherent risks of a reverse proxy setup remain.
https://trac.xiph.org/ticket/1959
https://trac.xiph.org/ticket/1851

Cheers

Thomas



From rafaelgomes at quijaua.com.br  Wed Feb 25 11:07:30 2015
From: rafaelgomes at quijaua.com.br (Rafael Gomes)
Date: Wed, 25 Feb 2015 08:07:30 -0300
Subject: [Icecast] icecast and proxy
In-Reply-To: <54EDA8BA.60602@gmail.com>
References: <54EDA8BA.60602@gmail.com>
Message-ID: <5f69ae7939206ffb7f97c86519fd30f6@quijaua.com.br>

I use iptables to either redirect the port packages

iptables -A PREROUTING -t nat -p tcp -d 192.168.2.32 --dport 80 -j 
REDIRECT --to-port 8000



Em 2015-02-25 07:49, Simone Dal Maso escreveu:
> Hello,
> sorry for all these questions, but there is a great news, this is the
> last! ... of the day :-)
> 
> So:
> I run nvRadio on port 8000, that is a problem for all people that are 
> at
> work, behind firewall or protected environment.
> So, I thought that a proxy can be the solution for streaming on port 
> 80.
> I enabled the apache2 proxy and, yes, if I type:
> www.nvapple.it/stream
> 
> the stream  is ok also now that I am on my office, on port80!
> 
> The problem is that if I look at the IP of people that are connected,
> visiting icecast's admin panel, I see always the ip of my machine, and
> it is unfortunately right, because they are listening through apache2
> proxy.
> 
> On my proxy.conf, I put:
> ***
>   ProxyPass /stream http://www.nvapple.it:8000/stream
> 
> 
> 
> 
> 
>   ProxyPassReverse /stream http://www.nvapple.it:8000/stream
> 
> 
> 
> ***
> Do you know other solutions that can show me the ip of people or this 
> is
> the right one?
> Thank you!
> 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From thomas at ruecker.fi  Wed Feb 25 11:18:55 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 25 Feb 2015 11:18:55 +0000
Subject: [Icecast] icecast and proxy
In-Reply-To: <5f69ae7939206ffb7f97c86519fd30f6@quijaua.com.br>
References: <54EDA8BA.60602@gmail.com>
	<5f69ae7939206ffb7f97c86519fd30f6@quijaua.com.br>
Message-ID: <54EDAF9F.5090800@ruecker.fi>

On 02/25/2015 11:07 AM, Rafael Gomes wrote:
> I use iptables to either redirect the port packages
>
> iptables -A PREROUTING -t nat -p tcp -d 192.168.2.32 --dport 80 -j 
> REDIRECT --to-port 8000
I do NOT recommend this. This tends to break in obscure ways, just as
reverse-proxies.
Icecast will happily listen on port 80 directly.

There are people who claim that it isn't possible, but that's because
they aren't capable to reverse the distro packaging breakage.
All it takes is to start the process as root and use the <changeowner>
directive to pass the information to which user to pivot after claiming
the privileged port.


Cheers

Thomas


From rafaelgomes at quijaua.com.br  Wed Feb 25 11:28:20 2015
From: rafaelgomes at quijaua.com.br (Rafael Gomes)
Date: Wed, 25 Feb 2015 08:28:20 -0300
Subject: [Icecast] icecast and proxy
In-Reply-To: <54EDAF9F.5090800@ruecker.fi>
References: <54EDA8BA.60602@gmail.com>
	<5f69ae7939206ffb7f97c86519fd30f6@quijaua.com.br>
	<54EDAF9F.5090800@ruecker.fi>
Message-ID: <5d7a1e444b670d556fda82f93e5ab50a@quijaua.com.br>

OK!

I made this solution because it is not suitable
to run as root applications that use ports below 1000


Em 2015-02-25 08:18, Thomas B. R?cker escreveu:
> On 02/25/2015 11:07 AM, Rafael Gomes wrote:
>> I use iptables to either redirect the port packages
>> 
>> iptables -A PREROUTING -t nat -p tcp -d 192.168.2.32 --dport 80 -j
>> REDIRECT --to-port 8000
> I do NOT recommend this. This tends to break in obscure ways, just as
> reverse-proxies.
> Icecast will happily listen on port 80 directly.
> 
> There are people who claim that it isn't possible, but that's because
> they aren't capable to reverse the distro packaging breakage.
> All it takes is to start the process as root and use the <changeowner>
> directive to pass the information to which user to pivot after claiming
> the privileged port.
> 
> 
> Cheers
> 
> Thomas
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From simone.dalmaso at gmail.com  Wed Feb 25 11:32:44 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Wed, 25 Feb 2015 12:32:44 +0100
Subject: [Icecast] icecast and proxy
In-Reply-To: <54EDAD5C.2030804@ruecker.fi>
References: <54EDA8BA.60602@gmail.com> <54EDAD5C.2030804@ruecker.fi>
Message-ID: <54EDB2DC.5060600@gmail.com>

Il 25/02/2015 12:09, "Thomas B. R?cker" ha scritto:
> DO NOT UNLESS YOU FULLY UNDERSTAND THE IMPLICATIONS!
> If you have to ask yourself "what are the implications?", you don't.
> You can easily kill your web server and other things can break too.
> Icecast explicitly does NOT support being reverse proxied!

Oh, ok...
I'm going to remove all public link from my website and replace with 
port 8000.
But for now I have no will to  purchase another linode server that run 
only for the webradio, also if it is the best solution.
I think that I will protect the page with a username and password, so 
only me and my team can use the port80, because otherwise it is 
impossible listen it at work.
So the access to that resource will be protected.
Hope it is better... and thank you!



From thomas at ruecker.fi  Wed Feb 25 11:50:26 2015
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Wed, 25 Feb 2015 11:50:26 +0000
Subject: [Icecast] icecast and proxy
In-Reply-To: <5d7a1e444b670d556fda82f93e5ab50a@quijaua.com.br>
References: <54EDA8BA.60602@gmail.com>	<5f69ae7939206ffb7f97c86519fd30f6@quijaua.com.br>	<54EDAF9F.5090800@ruecker.fi>
	<5d7a1e444b670d556fda82f93e5ab50a@quijaua.com.br>
Message-ID: <54EDB702.8080004@ruecker.fi>

On 02/25/2015 11:28 AM, Rafael Gomes wrote:
> OK!
>
> I made this solution because it is not suitable
> to run as root applications that use ports below 1000

Did you read my statement?
I address exactly this misconception.

As this seems to mostly happen to people who run Debian or its
derivatives, here are the #exactsteps to make Icecast listen to port 80
and as a bonus advertize this properly on YP without breaking:

* edit two lines in /etc/default/icecast2:
USERID=root
GROUPID=root
* edit the following lines in /etc/icecast2/icecast.xml:
 - this must be the *first* <listen-socket> entry:
    <listen-socket>
        <port>80</port>
    <listen-socket>
 - in the security section:
        <changeowner>
            <user>icecast2</user>
            <group>icecast</group>
        </changeowner>
 - for yp listings, make sure <hostname> resolves to your Icecast server
(not your homepage!) and remove the <!-- --> around the <directory> section.
* start Icecast through its init script / systemd

What this does:
Instead of changing the user in the init script, it gets changed during
start-up. At no point will Icecast actually keep running as root, it
only uses this to bind to privileged ports, <1024.
It _starts_ as "root", but _runs_ as "icecast2", just as *every* other
service binding to a port below 1024 does too, e.g. Apache HTTPD or NginX.
Security wise this is almost identical, BUT it enables Icecast to bind
to port 80 (and 443 too if you'd enable SSL support, but on debian that
would mean recompiling Icecast).

What this avoids:
We see hundreds of servers trying to list on YP that claim to be
"localhost" or to be listening on port 8000 while they are only
reachable on port 80 or some other port. All these radio streams are
automatically rejected from the YP directory at http://dir.xiph.org as
unreachable.
Also there are some other cases where Icecast will either use the first
listener port or the hostname and this will break a port redirect or a
reverse proxy setup.

Cheers

Thomas



From thomas at ruecker.fi  Wed Feb 25 18:47:45 2015
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Wed, 25 Feb 2015 18:47:45 +0000
Subject: [Icecast] IceCast Server (2.3.2) Limits? Disconnections due to
 user and memory?
In-Reply-To: <54ECA1F6.7010601@ruecker.fi>
References: <mcapbb$84c$1@ger.gmane.org>	<54EAC808.2090701@ruecker.fi>	<mcho06$7c5$1@ger.gmane.org>	<54EC74EB.6010607@ruecker.fi>	<pan$3de2d$4545b49c$9634280d$184be5fe$1@gmail.com>
	<54ECA1F6.7010601@ruecker.fi>
Message-ID: <54EE18D1.9000303@ruecker.fi>

On 02/24/2015 04:08 PM, "Thomas B. R?cker" wrote:
> On 02/24/2015 03:30 PM, Dean Sauer wrote:
>> On Tue, 24 Feb 2015 12:56:11 +0000, Thomas B. R?cker wrote:
>>
>>> Have you modified any of the buffer or burst parameters in Icecast? Can
>>> you provide your icecast.xml (passwords removed) as an attachment?
>>>
>> The list seems to dislike xml so hopefully this won't get stripped.
>>
> You're posting through the gmane NNTP interface using yenc encoding.
> That somehow doesn't work at all in this combination. Something along
> the way just eats everything.
>
> Could you please email those files to me directly using my personal
> email address, as regular mail attachments?

I received the files off list, attaching them to this mail.

The script is simple and ends with:
/usr/bin/mail -s "$SUBJECT" "$TO" < $MESSAGE
unset FEED

I don't see how that could be a problem unless the mail command would
for some reason stall.
Neither does 2.3.2 have threadpool support as it was removed way earlier.

The config doesn't look suspicious either. The particular values I was
interested look to be within bounds.

The only problem I spotted was a fallback definition:

<fallback-mount>feed9_pri_mark.mp3</fallback-mount>
Missing the prefix "/", but that might be due to how the file was "sanitized" from its original form.

I'm still suspcious of the script execution. It might help to attach to those additional processes and either strace them or look at them with gdb.


Thomas


-------------- next part --------------
<icecast>
    <limits>
        <clients>400</clients>
        <sources>420</sources>
        <threadpool>15</threadpool>
        <queue-size>524288</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>60</source-timeout>
        <!-- If enabled, this will provide a burst of data when a client 
             first connects, thereby significantly reducing the startup 
             time for listeners that do substantial buffering. However,
             it also significantly increases latency between the source
             client and listening client.  For low-latency setups, you
             might want to disable this. -->
        <burst-on-connect>1</burst-on-connect>
        <!-- same as burst-on-connect, but this allows for being more
             specific on how much to burst. Most people won't need to
             change from the default 64k. Applies to all mountpoints  -->
        <burst-size>65535</burst-size>
    </limits>

    <authentication>
        <!-- Sources log in with username 'source' -->
        <source-password>SOURCEPASS</source-password>
        <!-- Relays log in username 'relay' -->
        <relay-password>RELAYPASS</relay-password>

        <!-- Admin logs in with the username given below -->
        <admin-user>admin</admin-user>
        <admin-password>ADMINPASS</admin-password>
    </authentication>

    <!-- set the mountpoint for a shoutcast source to use, the default if not
         specified is /stream but you can change it here if an alternative is
         wanted or an extension is required
    <shoutcast-mount>/live.nsv</shoutcast-mount>
    -->

    <!-- Uncomment this if you want directory listings -->
    <!--
    <directory>
        <yp-url-timeout>15</yp-url-timeout>
        <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
    </directory>
     -->

    <!-- This is the hostname other people will use to connect to your server.
    It affects mainly the urls generated by Icecast for playlists and yp
    listings. -->
    <hostname>audio.somedomain.net</hostname>

    <!-- You may have multiple <listener> elements -->
    <listen-socket>
        <port>8000</port>
        <!-- <bind-address>127.0.0.1</bind-address> -->
        <!-- <shoutcast-mount>/stream</shoutcast-mount> -->
    </listen-socket>
    <!--
    <listen-socket>
        <port>8001</port>
    </listen-socket>
    -->

    <!--<master-server>127.0.0.1</master-server>-->
    <!--<master-server-port>8001</master-server-port>-->
    <!--<master-update-interval>120</master-update-interval>-->
    <!--<master-password>hackme</master-password>-->

    <!-- setting this makes all relays on-demand unless overridden, this is
         useful for master relays which do not have <relay> definitions here.
         The default is 0 -->
    <!--<relays-on-demand>1</relays-on-demand>-->

    <!--
    <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>
    </relay>
    -->
<mount>
 <mount-name>/Feed1.ogg</mount-name>
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>/feed_down_silence.ogg</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
 <mount-name>/Feed1</mount-name>
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>/feed1_down.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
 <mount-name>/feed2</mount-name>
 <!-- <fallback-mount>/feedmove.mp3</fallback-mount> -->
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>/feed2_primark.mp3</fallback-mount>
 <fallback-override>1</fallback-override> 
</mount>
<mount>
 <mount-name>/feed2.ogg</mount-name>
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>feed2_down_silence.ogg</fallback-mount>
</mount>
<mount>
 <mount-name>/feed3</mount-name>
 <on-disconnect>/etc/icecast2/kingkendown.sh</on-disconnect>
 <fallback-mount>/feed3_down.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
 <mount-name>/feed4</mount-name>
 <on-disconnect>/etc/icecast2/kingkendown.sh</on-disconnect>
 <fallback-mount>/feed4_down.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
 <mount-name>/feed5</mount-name>
<!-- <intro>/Scancaster_Rostraver.mp3</intro> -->
<!--  <on-disconnect>/etc/icecast2/feeddown2.sh</on-disconnect> -->
 <on-disconnect>/etc/icecast2/kingkendown.sh</on-disconnect>
 <fallback-mount>/feed5_down.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
 <mount-name>/feed6</mount-name>
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>/feed6_down.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
<mount-name>/feed7</mount-name>
  <fallback-mount>/feed7_pri_mark.mp3</fallback-mount>
  <on-disconnect>/etc/icecast2/feeddown4usc.sh</on-disconnect>
  <fallback-override>1</fallback-override>
  <hidden>1</hidden>
</mount>
<mount>
 <mount-name>/feed8</mount-name>
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>/feed8_down.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
<mount>
 <mount-name>/feed9</mount-name>
 <on-disconnect>/etc/icecast2/feeddown4.sh</on-disconnect>
 <fallback-mount>feed9_pri_mark.mp3</fallback-mount>
 <fallback-override>1</fallback-override>
</mount>
    <!-- Only define a <mount> section if you want to use advanced options,
         like alternative usernames or passwords
    <mount>
        <mount-name>/example-complex.ogg</mount-name>

        <username>othersource</username>
        <password>hackmemore</password>

        <max-listeners>1</max-listeners>
        <dump-file>/tmp/dump-example1.ogg</dump-file>
        <burst-size>65536</burst-size>
        <fallback-mount>/example2.ogg</fallback-mount>
        <fallback-override>1</fallback-override>
        <fallback-when-full>1</fallback-when-full>
        <intro>/example_intro.ogg</intro>
        <hidden>1</hidden>
        <no-yp>1</no-yp>
        <authentication type="htpasswd">
                <option name="filename" value="myauth"/>
                <option name="allow_duplicate_users" value="0"/>
        </authentication>
        <on-connect>/home/icecast/bin/stream-start</on-connect>
        <on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
    </mount>

    <mount>
        <mount-name>/auth_example.ogg</mount-name>
        <authentication type="url">
            <option name="mount_add"       value="http://myauthserver.net/notify_mount.php"/>
            <option name="mount_remove"    value="http://myauthserver.net/notify_mount.php"/>
            <option name="listener_add"    value="http://myauthserver.net/notify_listener.php"/>
            <option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
        </authentication>
    </mount>

    -->

    <fileserve>1</fileserve>

    <paths>
		<!-- basedir is only used if chroot is enabled -->
        <basedir>/usr/share/icecast2</basedir>

        <!-- Note that if <chroot> is turned on below, these paths must both
             be relative to the new root, not the original root -->
        <logdir>/var/log/icecast2</logdir>
        <webroot>/usr/share/icecast2/web</webroot>
        <adminroot>/usr/share/icecast2/admin</adminroot>
        <!-- <pidfile>/usr/share/icecast2/icecast.pid</pidfile> -->

        <!-- Aliases: treat requests for 'source' path as being for 'dest' path
             May be made specific to a port or bound address using the "port"
             and "bind-address" attributes.
          -->
        <!--
        <alias source="/foo" dest="/bar"/>
          -->
        <!-- Aliases: can also be used for simple redirections as well,
             this example will redirect all requests for http://server:port/ to
             the status page
          -->
        <alias source="/" dest="/status.xsl"/>
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <!-- <playlistlog>playlist.log</playlistlog> -->
      	<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
      	<logsize>10000</logsize> <!-- Max size of a logfile -->
        <!-- If logarchive is enabled (1), then when logsize is reached
             the logfile will be moved to [error|access|playlist].log.DATESTAMP,
             otherwise it will be moved to [error|access|playlist].log.old.
             Default is non-archive mode (i.e. overwrite)
        -->
        <logarchive>1</logarchive>
    </logging>

    <security>
        <chroot>0</chroot>
        <!--
        <changeowner>
            <user>nobody</user>
            <group>nogroup</group>
        </changeowner>
        -->
    </security>
</icecast>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kingkendown_SANI.sh
Type: application/x-shellscript
Size: 490 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20150225/e23587d2/attachment.bin>

From jonathancandler_msa at q.com  Wed Feb 25 18:40:34 2015
From: jonathancandler_msa at q.com (Jonathan)
Date: Wed, 25 Feb 2015 11:40:34 -0700
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EB5967.6050000@ruecker.fi>
References: <54EB3882.1080202@gmail.com>
	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>
	<54EB5967.6050000@ruecker.fi>
Message-ID: <54EE1722.5060001@q.com>

Just wondering, are the commands to upgrade icecast 2.3.2 to icecast 
version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I do 
have Ubuntu 14.04 and I have tried the bash script but modified the 
links a little bit to reflect the Ubuntu 14.04 distro, but keep getting 
errors and got an invalid extension in /etc/apt/sources.list.d


On 2/23/2015 9:46 AM, "Thomas B. R?cker" wrote:
> On 02/23/2015 04:41 PM, Simone Dal Maso wrote:
>> Il 23/02/2015 17:06, "Thomas B. R?cker" ha scritto:
>>> OK, that's from the Icecast side an easy situation.
>> really thank you very much!
>> I will make this operation tomorrow, but it seems easy.
>> Still thanks.
> Good luck, let us know if you run into problems.
>
> Also, seeing how Thunderbird totally butchered up those commands,
> attached please find a script that contains those. Or run it directly
> "bash add-icecast-repo". The script is specific to Ubuntu 12.04.
>
>
> Cheers
>
> Thomas
>
>
> _______________________________________________
> 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/20150225/928df0fa/attachment.htm>

From thomas at ruecker.fi  Wed Feb 25 19:00:55 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 25 Feb 2015 19:00:55 +0000
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EE1722.5060001@q.com>
References: <54EB3882.1080202@gmail.com>	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>	<54EB5967.6050000@ruecker.fi>
	<54EE1722.5060001@q.com>
Message-ID: <54EE1BE7.6040007@ruecker.fi>

On 02/25/2015 06:40 PM, Jonathan wrote:
> Just wondering, are the commands to upgrade icecast 2.3.2 to icecast
> version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I
> do have Ubuntu 14.04 and I have tried the bash script but modified the
> links a little bit to reflect the Ubuntu 14.04 distro, but keep
> getting errors and got an invalid extension in /etc/apt/sources.list.d

Did you use the commands from the previously attached script?
The inline commands were malformed.

The repository URL for 14.04 is:
http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/

I actually tested the script (with the 14.04 URL) on my 14.04 machine
before I originally sent it, so after fixing the URL it should have worked.

What error messages are you getting?


Cheers

Thomas

PS: Seeing, that there is demand for this, I'm going to see to get this
information added to the download page of icecast.org



From jonathancandler_msa at q.com  Wed Feb 25 19:17:08 2015
From: jonathancandler_msa at q.com (Jonathan)
Date: Wed, 25 Feb 2015 12:17:08 -0700
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EE1BE7.6040007@ruecker.fi>
References: <54EB3882.1080202@gmail.com>	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>	<54EB5967.6050000@ruecker.fi>	<54EE1722.5060001@q.com>
	<54EE1BE7.6040007@ruecker.fi>
Message-ID: <54EE1FB4.8060905@q.com>

I will send you the errors first and then the modified script.

Adding official Icecast repository for Ubuntu 14.04
add-icecast-repo: line 4: $'\r': command not found
Importing GPG key for official Icecast repository
"pg: Invalid option "-
add-icecast-repo: line 7: $'\r': command not found
Now, here is my script that I have changed

#!/bin/sh
echo Adding official Icecast repository for Ubuntu 14.04
sudo sh -c "echo deb 
http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/ ./ 
 >>/etc/apt/sources.list.d/icecast.list"

echo Importing GPG key for official Icecast repository
wget -qO - 
http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/Release.key 
| sudo apt-key add -


On 2/25/2015 12:00 PM, "Thomas B. R?cker" wrote:
> On 02/25/2015 06:40 PM, Jonathan wrote:
>> Just wondering, are the commands to upgrade icecast 2.3.2 to icecast
>> version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I
>> do have Ubuntu 14.04 and I have tried the bash script but modified the
>> links a little bit to reflect the Ubuntu 14.04 distro, but keep
>> getting errors and got an invalid extension in /etc/apt/sources.list.d
> Did you use the commands from the previously attached script?
> The inline commands were malformed.
>
> The repository URL for 14.04 is:
> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/
>
> I actually tested the script (with the 14.04 URL) on my 14.04 machine
> before I originally sent it, so after fixing the URL it should have worked.
>
> What error messages are you getting?
>
>
> Cheers
>
> Thomas
>
> PS: Seeing, that there is demand for this, I'm going to see to get this
> information added to the download page of icecast.org
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From thomas at ruecker.fi  Wed Feb 25 19:22:01 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 25 Feb 2015 19:22:01 +0000
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EE1FB4.8060905@q.com>
References: <54EB3882.1080202@gmail.com>	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>	<54EB5967.6050000@ruecker.fi>	<54EE1722.5060001@q.com>	<54EE1BE7.6040007@ruecker.fi>
	<54EE1FB4.8060905@q.com>
Message-ID: <54EE20D9.2040007@ruecker.fi>

On 02/25/2015 07:17 PM, Jonathan wrote:
> I will send you the errors first and then the modified script.
>
> Adding official Icecast repository for Ubuntu 14.04
> add-icecast-repo: line 4: $'\r': command not found
> Importing GPG key for official Icecast repository
> "pg: Invalid option "-
> add-icecast-repo: line 7: $'\r': command not found
> Now, here is my script that I have changed

Was Windows somehow involved in obtaining or transferring the script?
Try running "dos2unix add-icecast-repo" and then retry running the script.


>
> #!/bin/sh
> echo Adding official Icecast repository for Ubuntu 14.04
> sudo sh -c "echo deb 
> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/ ./ 
>  >>/etc/apt/sources.list.d/icecast.list"
>
> echo Importing GPG key for official Icecast repository
> wget -qO - 
> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/Release.key 
> | sudo apt-key add -

I guess that looks fine (slightly mangled by Thunderbird).


Cheers

Thomas
>
>
> On 2/25/2015 12:00 PM, "Thomas B. R?cker" wrote:
>> On 02/25/2015 06:40 PM, Jonathan wrote:
>>> Just wondering, are the commands to upgrade icecast 2.3.2 to icecast
>>> version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I
>>> do have Ubuntu 14.04 and I have tried the bash script but modified the
>>> links a little bit to reflect the Ubuntu 14.04 distro, but keep
>>> getting errors and got an invalid extension in /etc/apt/sources.list.d
>> Did you use the commands from the previously attached script?
>> The inline commands were malformed.
>>
>> The repository URL for 14.04 is:
>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/
>>
>> I actually tested the script (with the 14.04 URL) on my 14.04 machine
>> before I originally sent it, so after fixing the URL it should have worked.
>>
>> What error messages are you getting?
>>
>>
>> Cheers
>>
>> Thomas
>>
>> PS: Seeing, that there is demand for this, I'm going to see to get this
>> information added to the download page of icecast.org
>>
>> _______________________________________________
>> 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
>



From jonathancandler_msa at q.com  Wed Feb 25 20:08:42 2015
From: jonathancandler_msa at q.com (Jonathan)
Date: Wed, 25 Feb 2015 13:08:42 -0700
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EE20D9.2040007@ruecker.fi>
References: <54EB3882.1080202@gmail.com>	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>	<54EB5967.6050000@ruecker.fi>	<54EE1722.5060001@q.com>	<54EE1BE7.6040007@ruecker.fi>	<54EE1FB4.8060905@q.com>
	<54EE20D9.2040007@ruecker.fi>
Message-ID: <54EE2BCA.6030001@q.com>

Done that and all works... Thanks. and I could still use my old config 
file with all of my settings in it? Because that is what I'm still using 
now.

On 2/25/2015 12:22 PM, "Thomas B. R?cker" wrote:
> On 02/25/2015 07:17 PM, Jonathan wrote:
>> I will send you the errors first and then the modified script.
>>
>> Adding official Icecast repository for Ubuntu 14.04
>> add-icecast-repo: line 4: $'\r': command not found
>> Importing GPG key for official Icecast repository
>> "pg: Invalid option "-
>> add-icecast-repo: line 7: $'\r': command not found
>> Now, here is my script that I have changed
> Was Windows somehow involved in obtaining or transferring the script?
> Try running "dos2unix add-icecast-repo" and then retry running the script.
>
>
>> #!/bin/sh
>> echo Adding official Icecast repository for Ubuntu 14.04
>> sudo sh -c "echo deb
>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/ ./
>>   >>/etc/apt/sources.list.d/icecast.list"
>>
>> echo Importing GPG key for official Icecast repository
>> wget -qO -
>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/Release.key
>> | sudo apt-key add -
> I guess that looks fine (slightly mangled by Thunderbird).
>
>
> Cheers
>
> Thomas
>>
>> On 2/25/2015 12:00 PM, "Thomas B. R?cker" wrote:
>>> On 02/25/2015 06:40 PM, Jonathan wrote:
>>>> Just wondering, are the commands to upgrade icecast 2.3.2 to icecast
>>>> version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I
>>>> do have Ubuntu 14.04 and I have tried the bash script but modified the
>>>> links a little bit to reflect the Ubuntu 14.04 distro, but keep
>>>> getting errors and got an invalid extension in /etc/apt/sources.list.d
>>> Did you use the commands from the previously attached script?
>>> The inline commands were malformed.
>>>
>>> The repository URL for 14.04 is:
>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/
>>>
>>> I actually tested the script (with the 14.04 URL) on my 14.04 machine
>>> before I originally sent it, so after fixing the URL it should have worked.
>>>
>>> What error messages are you getting?
>>>
>>>
>>> Cheers
>>>
>>> Thomas
>>>
>>> PS: Seeing, that there is demand for this, I'm going to see to get this
>>> information added to the download page of icecast.org
>>>
>>> _______________________________________________
>>> 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 list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From thomas at ruecker.fi  Wed Feb 25 20:45:38 2015
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 25 Feb 2015 20:45:38 +0000
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EE2BCA.6030001@q.com>
References: <54EB3882.1080202@gmail.com>	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>	<54EB5967.6050000@ruecker.fi>	<54EE1722.5060001@q.com>	<54EE1BE7.6040007@ruecker.fi>	<54EE1FB4.8060905@q.com>	<54EE20D9.2040007@ruecker.fi>
	<54EE2BCA.6030001@q.com>
Message-ID: <54EE3472.1000007@ruecker.fi>

On 02/25/2015 08:08 PM, Jonathan wrote:
> Done that and all works... Thanks. and I could still use my old config 
> file with all of my settings in it? Because that is what I'm still using 
> now.

Yes, we're ensuring backwards compatibility with mainline Icecast releases.

If you are planning to use the JSON API directly from browsers, you
should add the headers though.

    <http-headers>
        <header name="Access-Control-Allow-Origin" value="*" />
    </http-headers>

For the rest I'd recommend release notes of all versions in between and
documentation.
http://icecast.org/docs/icecast-2.4.1/config-file.html


Cheers

Thomas


>
> On 2/25/2015 12:22 PM, "Thomas B. R?cker" wrote:
>> On 02/25/2015 07:17 PM, Jonathan wrote:
>>> I will send you the errors first and then the modified script.
>>>
>>> Adding official Icecast repository for Ubuntu 14.04
>>> add-icecast-repo: line 4: $'\r': command not found
>>> Importing GPG key for official Icecast repository
>>> "pg: Invalid option "-
>>> add-icecast-repo: line 7: $'\r': command not found
>>> Now, here is my script that I have changed
>> Was Windows somehow involved in obtaining or transferring the script?
>> Try running "dos2unix add-icecast-repo" and then retry running the script.
>>
>>
>>> #!/bin/sh
>>> echo Adding official Icecast repository for Ubuntu 14.04
>>> sudo sh -c "echo deb
>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/ ./
>>>   >>/etc/apt/sources.list.d/icecast.list"
>>>
>>> echo Importing GPG key for official Icecast repository
>>> wget -qO -
>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/Release.key
>>> | sudo apt-key add -
>> I guess that looks fine (slightly mangled by Thunderbird).
>>
>>
>> Cheers
>>
>> Thomas
>>> On 2/25/2015 12:00 PM, "Thomas B. R?cker" wrote:
>>>> On 02/25/2015 06:40 PM, Jonathan wrote:
>>>>> Just wondering, are the commands to upgrade icecast 2.3.2 to icecast
>>>>> version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I
>>>>> do have Ubuntu 14.04 and I have tried the bash script but modified the
>>>>> links a little bit to reflect the Ubuntu 14.04 distro, but keep
>>>>> getting errors and got an invalid extension in /etc/apt/sources.list.d
>>>> Did you use the commands from the previously attached script?
>>>> The inline commands were malformed.
>>>>
>>>> The repository URL for 14.04 is:
>>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/
>>>>
>>>> I actually tested the script (with the 14.04 URL) on my 14.04 machine
>>>> before I originally sent it, so after fixing the URL it should have worked.
>>>>
>>>> What error messages are you getting?
>>>>
>>>>
>>>> Cheers
>>>>
>>>> Thomas
>>>>
>>>> PS: Seeing, that there is demand for this, I'm going to see to get this
>>>> information added to the download page of icecast.org
>>>>




From jonathancandler_msa at q.com  Wed Feb 25 20:59:41 2015
From: jonathancandler_msa at q.com (Jonathan)
Date: Wed, 25 Feb 2015 13:59:41 -0700
Subject: [Icecast] upgrading icecast to 2.4.1
In-Reply-To: <54EE3472.1000007@ruecker.fi>
References: <54EB3882.1080202@gmail.com>	<54EB4FEE.8060900@ruecker.fi>	<54EB581E.8010601@gmail.com>	<54EB5967.6050000@ruecker.fi>	<54EE1722.5060001@q.com>	<54EE1BE7.6040007@ruecker.fi>	<54EE1FB4.8060905@q.com>	<54EE20D9.2040007@ruecker.fi>	<54EE2BCA.6030001@q.com>
	<54EE3472.1000007@ruecker.fi>
Message-ID: <54EE37BD.1030605@q.com>

I'm thinking about adding my headers, but, if I do that, how would I go 
about coding that into a web page?

On 2/25/2015 1:45 PM, "Thomas B. R?cker" wrote:
> On 02/25/2015 08:08 PM, Jonathan wrote:
>> Done that and all works... Thanks. and I could still use my old config
>> file with all of my settings in it? Because that is what I'm still using
>> now.
> Yes, we're ensuring backwards compatibility with mainline Icecast releases.
>
> If you are planning to use the JSON API directly from browsers, you
> should add the headers though.
>
>      <http-headers>
>          <header name="Access-Control-Allow-Origin" value="*" />
>      </http-headers>
>
> For the rest I'd recommend release notes of all versions in between and
> documentation.
> http://icecast.org/docs/icecast-2.4.1/config-file.html
>
>
> Cheers
>
> Thomas
>
>
>> On 2/25/2015 12:22 PM, "Thomas B. R?cker" wrote:
>>> On 02/25/2015 07:17 PM, Jonathan wrote:
>>>> I will send you the errors first and then the modified script.
>>>>
>>>> Adding official Icecast repository for Ubuntu 14.04
>>>> add-icecast-repo: line 4: $'\r': command not found
>>>> Importing GPG key for official Icecast repository
>>>> "pg: Invalid option "-
>>>> add-icecast-repo: line 7: $'\r': command not found
>>>> Now, here is my script that I have changed
>>> Was Windows somehow involved in obtaining or transferring the script?
>>> Try running "dos2unix add-icecast-repo" and then retry running the script.
>>>
>>>
>>>> #!/bin/sh
>>>> echo Adding official Icecast repository for Ubuntu 14.04
>>>> sudo sh -c "echo deb
>>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/ ./
>>>>    >>/etc/apt/sources.list.d/icecast.list"
>>>>
>>>> echo Importing GPG key for official Icecast repository
>>>> wget -qO -
>>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/Release.key
>>>> | sudo apt-key add -
>>> I guess that looks fine (slightly mangled by Thunderbird).
>>>
>>>
>>> Cheers
>>>
>>> Thomas
>>>> On 2/25/2015 12:00 PM, "Thomas B. R?cker" wrote:
>>>>> On 02/25/2015 06:40 PM, Jonathan wrote:
>>>>>> Just wondering, are the commands to upgrade icecast 2.3.2 to icecast
>>>>>> version 2.4.1 the same in Ubuntu 12.04 as they are in Ubuntu 14.04? I
>>>>>> do have Ubuntu 14.04 and I have tried the bash script but modified the
>>>>>> links a little bit to reflect the Ubuntu 14.04 distro, but keep
>>>>>> getting errors and got an invalid extension in /etc/apt/sources.list.d
>>>>> Did you use the commands from the previously attached script?
>>>>> The inline commands were malformed.
>>>>>
>>>>> The repository URL for 14.04 is:
>>>>> http://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04/
>>>>>
>>>>> I actually tested the script (with the 14.04 URL) on my 14.04 machine
>>>>> before I originally sent it, so after fixing the URL it should have worked.
>>>>>
>>>>> What error messages are you getting?
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> Thomas
>>>>>
>>>>> PS: Seeing, that there is demand for this, I'm going to see to get this
>>>>> information added to the download page of icecast.org
>>>>>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From simone.dalmaso at gmail.com  Thu Feb 26 09:56:15 2015
From: simone.dalmaso at gmail.com (Simone Dal Maso)
Date: Thu, 26 Feb 2015 10:56:15 +0100
Subject: [Icecast] a simple modification to html output of icecast
Message-ID: <54EEEDBF.2020606@gmail.com>

Hello,
well, this is only a simple modification I need only me, but I don't 
know why it seems not to work.
Since I'm blind, I use sometime a special braille computer in order to 
access internet.
The browser is really poor and not compatible with flash, html5, so it 
is quite old.
Anyway:
 From the moment I upgrade to icecast 2.4.1, instead of showing 
correctly the status page:
www.nvapple.it:8000
it shows me the source of the page.
This is really annoying!

To solve the problem I must modify the line in which there is:

<html xmlns="http://www.w3.org/1999/xhtml">

in:
<html>

A simple and stupid modification, as you can see, but for unexplained 
reasons, it is what this  old machine wants.
So I open my ssh console.

cd /usr/share/icecast2/web
nano status.xsl

I modified the line and save.
Restarted icecast2.

But the page is always shown with:

<html xmlns="http://www.w3.org/1999/xhtml">

Why?
Is there another page to modify?
Thank you!



From epirat07 at gmail.com  Thu Feb 26 11:00:26 2015
From: epirat07 at gmail.com (Marvin Scholz)
Date: Thu, 26 Feb 2015 12:00:26 +0100
Subject: [Icecast] a simple modification to html output of icecast
In-Reply-To: <54EEEDBF.2020606@gmail.com>
References: <54EEEDBF.2020606@gmail.com>
Message-ID: <F664BFFE-14EC-4004-953B-51706655B97B@gmail.com>

On 26 Feb 2015, at 10:56, Simone Dal Maso wrote:

> Hello,
> well, this is only a simple modification I need only me, but I don't
> know why it seems not to work.
> Since I'm blind, I use sometime a special braille computer in order to
> access internet.
> The browser is really poor and not compatible with flash, html5, so it
> is quite old.
> Anyway:
> From the moment I upgrade to icecast 2.4.1, instead of showing
> correctly the status page:
> www.nvapple.it:8000
> it shows me the source of the page.
> This is really annoying!
>
> To solve the problem I must modify the line in which there is:
>
> <html xmlns="http://www.w3.org/1999/xhtml">
>
> in:
> <html>

Yeah, I already noticed this and it will be fixed in the completely new 
Web interface of Icecast 2.5.

>
> A simple and stupid modification, as you can see, but for unexplained
> reasons, it is what this  old machine wants.
> So I open my ssh console.
>
> cd /usr/share/icecast2/web
> nano status.xsl
>
> I modified the line and save.
> Restarted icecast2.
>
> But the page is always shown with:
>
> <html xmlns="http://www.w3.org/1999/xhtml">
>
> Why?
> Is there another page to modify?
> Thank you!

This is because the xsl transform inserts it there, try changing the 
xsl:output to look like the following:
(Most important is that the method is html there.)

<xsl:output method="html" doctype-public="-//W3C//DTD XHTML 1.0 
Strict//EN" 
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" 
indent="yes" encoding="UTF-8" />

Please let me know if this fixes the problem!

>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast