From brad at musatcha.com  Tue Nov  4 14:37:57 2014
From: brad at musatcha.com (Brad Isbell)
Date: Tue, 4 Nov 2014 08:37:57 -0600
Subject: [Icecast] Source Dropouts - More info
In-Reply-To: <m3af0o$8o2$1@ger.gmane.org>
References: <m30gmk$b8l$1@ger.gmane.org> <m3af0o$8o2$1@ger.gmane.org>
Message-ID: <CAELR-fBa+2s8Ni04uDQ0UQbYBBGwRZ8Q-i3fBdzK2BcvNH9Kvg@mail.gmail.com>

Is it possible to run a packet capture to see what happens over the wire
when this occurs?  That would give some concrete information.

If you have the disk space, just rotate out a capture file every hour.
Once you catch it, filter out a pcap file with what happens when the
sources are disconnected, and send us a link.

Brad Isbell
brad at musatcha.com
http://www.musatcha.com

On Tue, Nov 4, 2014 at 5:58 AM, Dean Sauer <wemanageitfl at gmail.com> wrote:

> On Fri, 31 Oct 2014 17:25:41 +0000, Dean Sauer wrote:
>
> > I have a IceCast Server as follows:
> >
> > 2048MB RAM 2048MB SWAP
> >
> > OpenVZ VPS Ubuntu 12.04 64b full update
> >
> > I've looked at logs and I am not seeing a reason for ALL THE FEEDS to
> > DROP AT ONCE SAME TIME within milliseconds. Then they reconnect. Fine
> > for weeks or more, or might drop again... in a few seconds, minutes,
> > hours, or continue on for days and weeks...
> >
>
> The latest incident, yesterday AM, and of course I can't access it for
> the next 6 hours, so nothing but silence on those feeds.
>
> The server DROPS the SOURCES, BUT the SOURCES think they are connected.
>
> In this case, four feeds, think they are connected BUT the server has
> dropped them and is using the backup mount, which is to feed silence.
>
> The ONLY way to correct this is to drop the sources at the encoding
> source, and reconnect.
>
> In this case the sources are DarkIce 1.x via *buntu and Raspbian.
>
> It will happen on sources using non Linux based systems as well.
>
> Any hints at what to look for???? Other ideas???
>
>
> _______________________________________________
> 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/20141104/49299e16/attachment.htm>

From neha1451 at iiitd.ac.in  Mon Nov  3 16:17:44 2014
From: neha1451 at iiitd.ac.in (Neha Arora)
Date: Mon, 3 Nov 2014 21:47:44 +0530
Subject: [Icecast] HELP
Message-ID: <CABnYB8Y=SD_AQ3BGfo=DXMYEDarixvaRHv61P2phRnP3YHLKww@mail.gmail.com>

is there a way to create multiple streams/channels through icecast.
P.S: i am using icecast with winamp and edcast plugin. To create multiple
streams i need to create multiple instances of winamp. But i want to save
all data regarding icecast( icecast/ winamp/ edcast/ database) on an online
server so that server remains online everytime. Creating multiple instances
will take a lot of space.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141103/17f95463/attachment.htm>

From thomas at ruecker.fi  Wed Nov  5 10:49:33 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Wed, 05 Nov 2014 10:49:33 +0000
Subject: [Icecast] HELP
In-Reply-To: <CABnYB8Y=SD_AQ3BGfo=DXMYEDarixvaRHv61P2phRnP3YHLKww@mail.gmail.com>
References: <CABnYB8Y=SD_AQ3BGfo=DXMYEDarixvaRHv61P2phRnP3YHLKww@mail.gmail.com>
Message-ID: <545A00BD.8020401@ruecker.fi>

Hi,

On 11/03/2014 04:17 PM, Neha Arora wrote:
> is there a way to create multiple streams/channels through icecast.

Yes, it's called "mountpoints". The documentation covers that quite well.
This page also nicely visualizes the concept:
http://liveice.sourceforge.net/understanding.html


> P.S: i am using icecast with winamp and edcast plugin. To create
> multiple streams i need to create multiple instances of winamp.

If you want multiple streams with _different_ content, then yes, of course.
If you want to stream the same content at several qualities and codecs,
then one instance with multiple stream output can work too.


> But i want to save all data regarding icecast( icecast/ winamp/
> edcast/ database) on an online server so that server remains online
> everytime. Creating multiple instances will take a lot of space.

Not really. It's fairly manageable. One Icecast server and some source
clients. Of course a micro-instance of $random_cloud_service will maybe
not be sufficient. But given, that even physical servers can already be
had for around 10-20?/month that shouldn't be of issue.

Cheers

Thomas

PS: Please note that you were not subscribed to the mailing list when
you sent the email. Please subscribe here to receive all possible
answers to your question and be able to ask further questions:
http://lists.xiph.org/mailman/listinfo/icecast



From veres at akos.me  Wed Nov  5 10:47:43 2014
From: veres at akos.me (Akos Veres)
Date: Wed, 5 Nov 2014 11:47:43 +0100
Subject: [Icecast] HELP
In-Reply-To: <CABnYB8Y=SD_AQ3BGfo=DXMYEDarixvaRHv61P2phRnP3YHLKww@mail.gmail.com>
References: <CABnYB8Y=SD_AQ3BGfo=DXMYEDarixvaRHv61P2phRnP3YHLKww@mail.gmail.com>
Message-ID: <CAMhiM5JXix9gp1EJ71Sdux+U4C_KryVfFF9vq35moCY+WJqSXQ@mail.gmail.com>

Just create additional mountpoints, that will solve your issue, you don't
need additional icecast instances. The documentation has this explained.

Best regards,
        *?kos Veres*

_____________________________________________
http://akos.me - A little about me.

On Mon, Nov 3, 2014 at 5:17 PM, Neha Arora <neha1451 at iiitd.ac.in> wrote:

> is there a way to create multiple streams/channels through icecast.
> P.S: i am using icecast with winamp and edcast plugin. To create multiple
> streams i need to create multiple instances of winamp. But i want to save
> all data regarding icecast( icecast/ winamp/ edcast/ database) on an online
> server so that server remains online everytime. Creating multiple instances
> will take a lot of space.
>
> _______________________________________________
> 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/20141105/9f58c5cd/attachment.htm>

From genocid3ita at gmail.com  Fri Nov  7 15:48:28 2014
From: genocid3ita at gmail.com (genocid3)
Date: Fri, 7 Nov 2014 16:48:28 +0100
Subject: [Icecast] suggestion on appropriate source client
Message-ID: <CAFoW9ow9U7uo49Ewct24ONQS7ZfozRdotCHDnxQwkfaJFuN5xQ@mail.gmail.com>

Hi everyone,

i would like to have some suggestion about the most appropriate source
client to use in conjunction with IceCast2 given few requirements:

1) the client should be able to handle multiple streams simultaneously and
thus multiple resource folders (for music files).
2) the client should be able to be programmatically manipulated (scripting
or API) and can thus provide a dynamic way to add or remove mountpoints to
icecast and manage the related music sources.
3) i am pretty much going to stream only music files (no dj's or live
sources).
4) i  would prefer something OpenSource.
5) the client should be able to automatically detect changes in music
folders and automatically updated the related playlist (eg i drop an mp3 to
the /mount1/ music folder and the appropriate playlist for that particular
stream gets updated).
6) should provide fallbacks when empty music folders are present (eg.
stream "silence").

Please be gentle, its my first post :)

Thank you in advance!,
Emanuel.

-- 

There are 10 people in the world, those who understand hexadecimal and
those who don't...the other 14 just don't care.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141107/5071223b/attachment.htm>

From brad at musatcha.com  Fri Nov  7 16:27:34 2014
From: brad at musatcha.com (Brad Isbell)
Date: Fri, 7 Nov 2014 10:27:34 -0600
Subject: [Icecast] suggestion on appropriate source client
In-Reply-To: <CAFoW9ow9U7uo49Ewct24ONQS7ZfozRdotCHDnxQwkfaJFuN5xQ@mail.gmail.com>
References: <CAFoW9ow9U7uo49Ewct24ONQS7ZfozRdotCHDnxQwkfaJFuN5xQ@mail.gmail.com>
Message-ID: <CAELR-fBXLHBb6E7KcvcX2Bq1ggeh7Oj5v3AVk5U=Qne9CzeYcw@mail.gmail.com>

Liquidsoap is exactly what you are looking for.

http://savonet.sourceforge.net/

Brad Isbell
brad at musatcha.com
http://www.musatcha.com

On Fri, Nov 7, 2014 at 9:48 AM, genocid3 <genocid3ita at gmail.com> wrote:

> Hi everyone,
>
> i would like to have some suggestion about the most appropriate source
> client to use in conjunction with IceCast2 given few requirements:
>
> 1) the client should be able to handle multiple streams simultaneously and
> thus multiple resource folders (for music files).
> 2) the client should be able to be programmatically manipulated (scripting
> or API) and can thus provide a dynamic way to add or remove mountpoints to
> icecast and manage the related music sources.
> 3) i am pretty much going to stream only music files (no dj's or live
> sources).
> 4) i  would prefer something OpenSource.
> 5) the client should be able to automatically detect changes in music
> folders and automatically updated the related playlist (eg i drop an mp3 to
> the /mount1/ music folder and the appropriate playlist for that particular
> stream gets updated).
> 6) should provide fallbacks when empty music folders are present (eg.
> stream "silence").
>
> Please be gentle, its my first post :)
>
> Thank you in advance!,
> Emanuel.
>
> --
>
> There are 10 people in the world, those who understand hexadecimal and
> those who don't...the other 14 just don't care.
>
> _______________________________________________
> 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/20141107/47c1c241/attachment.htm>

From 0turn1 at gmail.com  Fri Nov  7 21:04:03 2014
From: 0turn1 at gmail.com (Scott Winterstein)
Date: Fri, 7 Nov 2014 22:04:03 +0100
Subject: [Icecast] suggestion on appropriate source client
In-Reply-To: <CAFoW9ow9U7uo49Ewct24ONQS7ZfozRdotCHDnxQwkfaJFuN5xQ@mail.gmail.com>
References: <CAFoW9ow9U7uo49Ewct24ONQS7ZfozRdotCHDnxQwkfaJFuN5xQ@mail.gmail.com>
Message-ID: <CA+3r0CJow3yyTBDMFej542bYXX1Yry1SKiyXP96EA-Le9mn_UQ@mail.gmail.com>

Some of this will require special scripts and programming to work as
described. You can program IceCast to create all the settings and streams /
mountpoints you need, your source encoder software settings pointed to the
correct mount in the IceCast server. But to stream separate sources will
work best if you setup separate systems for each one since running multiple
instances of a source encoding takes up a big amount of resources and only
a very powerful system setup with multiple source encoder hardware can do
the job right and with as little interruption. I have vast exp in this and
find alot of it has to do with really figuring out the math and setup to be
a simple configuration of a source that matches the bitrate your serving.
64kbps serving then the source mp3 ogg wav etc etc should be the same.
Other wise you have the encoding that is very source hogging and alot of
crash or glitches, music thats slugginsh or sounds bad... I can stream a
32kbps stream that sounds pretty powerful and can be turned up by the
endpoint with no problem. the old saying is garbage in garbage out...

I hope this helps

Mit freundlichen Gr??en
Scott Winterstein

EMAIL: 0turn1 at gmail dot com

On Fri, Nov 7, 2014 at 4:48 PM, genocid3 <genocid3ita at gmail.com> wrote:

> Hi everyone,
>
> i would like to have some suggestion about the most appropriate source
> client to use in conjunction with IceCast2 given few requirements:
>
> 1) the client should be able to handle multiple streams simultaneously and
> thus multiple resource folders (for music files).
> 2) the client should be able to be programmatically manipulated (scripting
> or API) and can thus provide a dynamic way to add or remove mountpoints to
> icecast and manage the related music sources.
> 3) i am pretty much going to stream only music files (no dj's or live
> sources).
> 4) i  would prefer something OpenSource.
> 5) the client should be able to automatically detect changes in music
> folders and automatically updated the related playlist (eg i drop an mp3 to
> the /mount1/ music folder and the appropriate playlist for that particular
> stream gets updated).
> 6) should provide fallbacks when empty music folders are present (eg.
> stream "silence").
>
> Please be gentle, its my first post :)
>
> Thank you in advance!,
> Emanuel.
>
> --
>
> There are 10 people in the world, those who understand hexadecimal and
> those who don't...the other 14 just don't care.
>
> _______________________________________________
> 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/20141107/053a6afb/attachment.htm>

From xoneca+icecast at gmail.com  Sat Nov  8 15:02:40 2014
From: xoneca+icecast at gmail.com (Xabier Oneca -- xOneca)
Date: Sat, 8 Nov 2014 16:02:40 +0100
Subject: [Icecast] Source Dropouts - V2.3.2 - Ubuntu 12.04 64b
In-Reply-To: <m30gmk$b8l$1@ger.gmane.org>
References: <m30gmk$b8l$1@ger.gmane.org>
Message-ID: <CACkgH72cOuJWv4qPagtebuGMi9Oto01VvziaY64rfKXn8CLwKA@mail.gmail.com>

Hello Dean,

> OpenVZ VPS

Not sure if related, but I had VPSLink's OpenVZ servers and they
dropped connection svery often. I since migrated to AWS and no
connection drops again.

Cheers,
Xabier Oneca_,,_


From thomas at ruecker.fi  Sat Nov  8 15:37:22 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Sat, 08 Nov 2014 15:37:22 +0000
Subject: [Icecast] Access Log Time Issue
In-Reply-To: <CAJZoRVX3hg0d1g7BBoTGkVKJhMrH8GMNh825CMt_Zuxt0KWe9Q@mail.gmail.com>
References: <CAJZoRVX3hg0d1g7BBoTGkVKJhMrH8GMNh825CMt_Zuxt0KWe9Q@mail.gmail.com>
Message-ID: <545E38B2.80300@ruecker.fi>

On 10/11/2014 12:25 AM, Drew Proctor wrote:
> I am having an issue with access.log. The listen time is way too
> large. I am getting lines such as:
> 10.120.34.31 - - [29/Sep/2014:00:12:03 -0400] "GET /music HTTP/1.1"
> 200 8827 "(null)" "-" 16099200
>
> 16099200 is way too large for a listen time. I am using Icecast 2.4.0
> on Windows Server 2012 R2.Does anyone know why this is happening?

We have isolated the issue and fixed it. https://trac.xiph.org/ticket/2081
It will be released as part of a larger bug-fix release of Icecast 2.4.1
in the next couple of days (we're feature complete, this was the last
bug on my list).


Cheers

Thomas



From jprince14 at live.com  Tue Nov 11 05:53:24 2014
From: jprince14 at live.com (Jeremy Prince)
Date: Tue, 11 Nov 2014 00:53:24 -0500
Subject: [Icecast] Socket to Icecast
Message-ID: <SNT148-W7545E6E5A1469CFA657067CF810@phx.gbl>

I am working on a project where I am reading data from a radio then encoding it to mp3. I would like to then send this encoded data to Icecast for streaming, is all I need to do is create a tcp connection to the icecast socket and then start sending the encoded buffer?
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141111/f54eafe6/attachment.htm>

From thomas at ruecker.fi  Tue Nov 11 12:32:55 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Tue, 11 Nov 2014 12:32:55 +0000
Subject: [Icecast] Socket to Icecast
In-Reply-To: <SNT148-W7545E6E5A1469CFA657067CF810@phx.gbl>
References: <SNT148-W7545E6E5A1469CFA657067CF810@phx.gbl>
Message-ID: <546201F7.10705@ruecker.fi>

Hi,

On 11/11/2014 05:53 AM, Jeremy Prince wrote:
> I am working on a project where I am reading data from a radio then
> encoding it to mp3. I would like to then send this encoded data to
> Icecast for streaming, is all I need to do is create a tcp connection
> to the icecast socket and then start sending the encoded buffer?

It's a bit more than that. Probably the easiest way for you is to look
at integrating libShout into your project. It handles all the specifics.
Or in case of Icecast 2.4.x, implement HTTP PUT.

We're currently working on updated documentation about Icecast source
connections. You'll find it on http://icecast.org soon.


Cheers

Thomas


From jprince14 at gmail.com  Wed Nov 12 04:45:01 2014
From: jprince14 at gmail.com (Jeremy Prince)
Date: Tue, 11 Nov 2014 23:45:01 -0500
Subject: [Icecast] Socket to Icecast
In-Reply-To: <546201F7.10705@ruecker.fi>
References: <SNT148-W7545E6E5A1469CFA657067CF810@phx.gbl>
	<546201F7.10705@ruecker.fi>
Message-ID: <CAD9Mk=Lj94NwL8EJnQbpofFqQ+1nuikVSiSK1SQBOemVdWiuUg@mail.gmail.com>

Thomas,

Thanks for pointing me in the right direction. I updated my code to use
cURL for sending the mp3 encoded audio to http://localhost:8001/test_stream.
What should I put in my icecast configuration file to properly receive the
stream?

This example of using cURL for HTTP PUT operations was very helpful in case
anyone else is interested.
http://curl.haxx.se/libcurl/c/httpput.html

thanks again,

Jeremy

On Tue, Nov 11, 2014 at 7:32 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:

> Hi,
>
> On 11/11/2014 05:53 AM, Jeremy Prince wrote:
> > I am working on a project where I am reading data from a radio then
> > encoding it to mp3. I would like to then send this encoded data to
> > Icecast for streaming, is all I need to do is create a tcp connection
> > to the icecast socket and then start sending the encoded buffer?
>
> It's a bit more than that. Probably the easiest way for you is to look
> at integrating libShout into your project. It handles all the specifics.
> Or in case of Icecast 2.4.x, implement HTTP PUT.
>
> We're currently working on updated documentation about Icecast source
> connections. You'll find it on http://icecast.org soon.
>
>
> 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/20141111/6d1a682f/attachment.htm>

From thomas at ruecker.fi  Thu Nov 13 11:23:29 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 13 Nov 2014 11:23:29 +0000
Subject: [Icecast] Socket to Icecast
In-Reply-To: <CAD9Mk=Lj94NwL8EJnQbpofFqQ+1nuikVSiSK1SQBOemVdWiuUg@mail.gmail.com>
References: <SNT148-W7545E6E5A1469CFA657067CF810@phx.gbl>	<546201F7.10705@ruecker.fi>
	<CAD9Mk=Lj94NwL8EJnQbpofFqQ+1nuikVSiSK1SQBOemVdWiuUg@mail.gmail.com>
Message-ID: <546494B1.4010207@ruecker.fi>

On 11/12/2014 04:45 AM, Jeremy Prince wrote:
> Thomas,
>
> Thanks for pointing me in the right direction. I updated my code to
> use cURL for sending the mp3 encoded audio to
> http://localhost:8001/test_stream. What should I put in my icecast
> configuration file to properly receive the stream?

Please note that PUT will work only with Icecast 2.4.0 or newer.
The only thing, for this to work, you need to set in the Icecast config
is the source-password. Once you've done that and restarted Icecast, you
can use the credentials:
username: source
password: whateveryouset in <source-password>

The stream should then appear on the Icecast status page. In your case
probably:
http://localhost:8001/

More complicated setups are possible. Please refer to the Icecast
documentation for details:
http://icecast.org/docs/


Cheers

Thomas



From genocid3ita at gmail.com  Fri Nov 14 20:43:16 2014
From: genocid3ita at gmail.com (genocid3)
Date: Fri, 14 Nov 2014 21:43:16 +0100
Subject: [Icecast] Pyhton Class/library for Icecast 2.32 Stats and other
 info access?
In-Reply-To: <m45nrs$r0g$1@ger.gmane.org>
References: <m45nrs$r0g$1@ger.gmane.org>
Message-ID: <CAFoW9oxWrcyt=p7HgYXKYyRUfvwAdBxzzZp=MStUBzXipby0pg@mail.gmail.com>

Hi, if i am not mistaken 2.4 has a servlet which provides json output for
active mounts and stats.

You can check it out at http://your host:8000/status-json.xsl

Just upgrade your version and you should be fine.

Hth
In a search for access to various ways to interact with Icecast via
Python, I ran across this:

http://xiph.org/~brendan/pyshout2/pyshout2-0.0.1.tar.gz

Which is now dead (404).

I have a need to be able to query an Icecast Server and get the number of
listeners for a mount. I need to do this via Python, and preferably with
out scraping the stats page of Icecast to do so. If there was access to
other data that would be a plus, but a simple means to call a Python
function and get an integer back with this value would be a plus.

Is there something else out there to do this with out scraping a page?

Python is the only route at this time due to the nature of other code
involved which is already done in Python, and far to advanced to rewrite
at this point, and is only supported on Python due to the underlying
hardware used.


_______________________________________________
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/20141114/80484bbc/attachment.htm>

From geoff at QuiteLikely.com  Fri Nov 14 21:45:03 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 14 Nov 2014 23:45:03 +0200 (IST)
Subject: [Icecast] Pyhton Class/library for Icecast 2.32 Stats and other
 info access?
In-Reply-To: <m45nrs$r0g$1@ger.gmane.org>
References: <m45nrs$r0g$1@ger.gmane.org>
Message-ID: <alpine.DEB.2.02.1411142329040.3835@voldemort.home>

On Fri, 14 Nov 2014, Dean Sauer wrote:

> In a search for access to various ways to interact with Icecast via
> Python, I ran across this:
>
> http://xiph.org/~brendan/pyshout2/pyshout2-0.0.1.tar.gz
>
> Which is now dead (404).

I don't think this library would have helped.  I expect it would be useful 
for source clients to send media to a server.

> I have a need to be able to query an Icecast Server and get the number of
> listeners for a mount. I need to do this via Python, and preferably with
> out scraping the stats page of Icecast to do so. If there was access to
> other data that would be a plus, but a simple means to call a Python
> function and get an integer back with this value would be a plus.

First, I take it you know that you can get all the stats there are by 
querying http://<server>:<port>/admin/stats.xml (this requires the admin 
username and password of course).

If you don't want to go to these lengths, you could write an XSL transform 
to get you this info.   Something like this should do it:

<xsl:stylesheet xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" version = "1.0" >
<xsl:output omit-xml-declaration="yes" method="text" doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" indent="no" encoding="UTF-8" />
<xsl:template match = "/icestats" >
<xsl:for-each select="source">
<xsl:value-of select="listeners" />
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>

Note that if you call this without arguments, it will mash all the 
listener numbers together into one big integer, so you'll want to specify 
a mountpoint.  If you were to call it listeners.xsl, you could call it 
like so:

http://<server>:<port>/listeners.xsl?mount=/<mountname>

HTH,
Geoff.



From thomas at ruecker.fi  Mon Nov 17 06:48:46 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Mon, 17 Nov 2014 06:48:46 +0000
Subject: [Icecast] Pyhton Class/library for Icecast 2.32 Stats and other
 info access?
In-Reply-To: <CAFoW9oxWrcyt=p7HgYXKYyRUfvwAdBxzzZp=MStUBzXipby0pg@mail.gmail.com>
References: <m45nrs$r0g$1@ger.gmane.org>
	<CAFoW9oxWrcyt=p7HgYXKYyRUfvwAdBxzzZp=MStUBzXipby0pg@mail.gmail.com>
Message-ID: <54699A4E.3020009@ruecker.fi>

On 11/14/2014 08:43 PM, genocid3 wrote:
>
> Hi, if i am not mistaken 2.4 has a servlet which provides json output
> for active mounts and stats.
>
> You can check it out at http://your host:8000/status-json.xsl
>
> Just upgrade your version and you should be fine.
>

Actually you should be able to retrofit that to older versions too. If,
like Dean, you really want to stick to that for some reason.
All it needs is to copy two files:
status-json.xsl
xml2json.xsl
They go into the webroot.
If you want to do that, please use the status-json.xsl from Icecast
2.4.1 (or until I release it within the coming days, from trunk)

As far as I understand python works quite well with JSON, so that would
probably simplify things

> Hth
>
> In a search for access to various ways to interact with Icecast via
> Python, I ran across this:
>
> http://xiph.org/~brendan/pyshout2/pyshout2-0.0.1.tar.gz
> <http://xiph.org/%7Ebrendan/pyshout2/pyshout2-0.0.1.tar.gz>
>
> Which is now dead (404).
>
> I have a need to be able to query an Icecast Server and get the number of
> listeners for a mount. I need to do this via Python, and preferably with
> out scraping the stats page of Icecast to do so. If there was access to
> other data that would be a plus, but a simple means to call a Python
> function and get an integer back with this value would be a plus.
>
> Is there something else out there to do this with out scraping a page?
>
> Python is the only route at this time due to the nature of other code
> involved which is already done in Python, and far to advanced to rewrite
> at this point, and is only supported on Python due to the underlying
> hardware used.


Cheers

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141117/20948dc2/attachment.htm>

From simon at bkconnect.net  Tue Nov 18 14:55:00 2014
From: simon at bkconnect.net (Simon Blandford)
Date: Tue, 18 Nov 2014 14:55:00 +0000
Subject: [Icecast] Password authentication problem with IOS and Android HTML5
Message-ID: <546B5DC4.4060505@bkconnect.net>

Hi,

I have been using password protected MP3 streams for a number of years 
but I've hit against a problem. Neither Android or recent versions of 
IOS work with password protected MP3 streams.

Now Android has dropped Flash, IOS doesn't work any more and more and 
more people expect to use their mobile devices to hear the streams. This 
is getting difficult.

I know this isn't a problem with Icecast. I have filed a bug report to 
the Android issue tracker here with a test stream to illustrate the 
problem. If you have any Android or IOS devices feel free to try.
https://code.google.com/p/android/issues/detail?id=62632

I am just curious if anyone else has encountered this problem and if 
there are any known work-arounds to make it work.

Regards...


From rajil.s at gmail.com  Tue Nov 18 15:47:52 2014
From: rajil.s at gmail.com (Rajil Saraswat)
Date: Tue, 18 Nov 2014 09:47:52 -0600
Subject: [Icecast] Password authentication problem with IOS and Android
	HTML5
In-Reply-To: <546B5DC4.4060505@bkconnect.net>
References: <546B5DC4.4060505@bkconnect.net>
Message-ID: <CAFoaQoB9ZT6grNDMGzsZdRRXPxPD=YPYM9dOSuaZSfU+WvtFzg@mail.gmail.com>

On Nov 18, 2014 8:55 AM, "Simon Blandford" <simon at bkconnect.net> wrote:
>
> Hi,
>
> I have been using password protected MP3 streams for a number of years
> but I've hit against a problem. Neither Android or recent versions of
> IOS work with password protected MP3 streams.
>
> Now Android has dropped Flash, IOS doesn't work any more and more and
> more people expect to use their mobile devices to hear the streams. This
> is getting difficult.
>
> I know this isn't a problem with Icecast. I have filed a bug report to
> the Android issue tracker here with a test stream to illustrate the
> problem. If you have any Android or IOS devices feel free to try.
> https://code.google.com/p/android/issues/detail?id=62632
>
> I am just curious if anyone else has encountered this problem and if
> there are any known work-arounds to make it work.
>
> Regards...
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

The protected stream works in Firefox on the android phone. In my
experience xiialive player (available in google playstore) works well with
protected ogg streams.

Rajil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141118/43b8e6bb/attachment.htm>

From simon at bkconnect.net  Tue Nov 18 16:39:16 2014
From: simon at bkconnect.net (Simon Blandford)
Date: Tue, 18 Nov 2014 16:39:16 +0000
Subject: [Icecast] Password authentication problem with IOS and Android
 HTML5
In-Reply-To: <CAFoaQoB9ZT6grNDMGzsZdRRXPxPD=YPYM9dOSuaZSfU+WvtFzg@mail.gmail.com>
References: <546B5DC4.4060505@bkconnect.net>
	<CAFoaQoB9ZT6grNDMGzsZdRRXPxPD=YPYM9dOSuaZSfU+WvtFzg@mail.gmail.com>
Message-ID: <546B7634.1020308@bkconnect.net>

Thanks. I've just also found another work-around for Chrome/Android. I 
have yet to test it on IOS.

If the username and password is injected into the URL it works. This can 
be done with some Javascript on the HTML5 player i.e.

<source src="http://username:password at myicecastserver.org/mystream.mp3" />

On 18/11/14 15:47, Rajil Saraswat wrote:
>
>
> On Nov 18, 2014 8:55 AM, "Simon Blandford" <simon at bkconnect.net 
> <mailto:simon at bkconnect.net>> wrote:
> >
> > Hi,
> >
> > I have been using password protected MP3 streams for a number of years
> > but I've hit against a problem. Neither Android or recent versions of
> > IOS work with password protected MP3 streams.
> >
> > Now Android has dropped Flash, IOS doesn't work any more and more and
> > more people expect to use their mobile devices to hear the streams. This
> > is getting difficult.
> >
> > I know this isn't a problem with Icecast. I have filed a bug report to
> > the Android issue tracker here with a test stream to illustrate the
> > problem. If you have any Android or IOS devices feel free to try.
> > https://code.google.com/p/android/issues/detail?id=62632
> >
> > I am just curious if anyone else has encountered this problem and if
> > there are any known work-arounds to make it work.
> >
> > Regards...
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org <mailto:Icecast at xiph.org>
> > http://lists.xiph.org/mailman/listinfo/icecast
>
> The protected stream works in Firefox on the android phone. In my 
> experience xiialive player (available in google playstore) works well 
> with protected ogg streams.
>
> Rajil
>
>
>
> _______________________________________________
> 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/20141118/5fc6295b/attachment.htm>

From thomas at ruecker.fi  Thu Nov 20 09:20:48 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 20 Nov 2014 09:20:48 +0000
Subject: [Icecast]  [Icecast-dev]  Icecast 2.4.1 release
Message-ID: <546DB270.8090301@ruecker.fi>

This is to announce the release of Icecast 2.4.1.

This is a pure bugfix-only release. Upgrading to it is recommended,
especially due to security fixes. A summary of the changes is listed
below, for details please refer to the ChangeLog.

Fixes

    * Fix autogen.sh to work properly on OS X
    * Removed threadpool from the example config
      (it is long gone and unused)
    * More detailed logging:
        - Add source IP adress to source start/stop logging
        - Add mountpoints to some log lines
    * Fix logging to send errors to STDERR prior to opening log files
    * Fix <auth> in default mounts (<mount type="default">)
    * Fix the JSON status API (status-json.xsl),
      which could return invalid JSON in some cases
    * SSL Security improvements:
        - Disable SSLv3
        - Disable SSL compression
        - Updated the default ciphers to be more secure
    * Handle empty strings in config file better
    * Fix logging of client connection duration time on Windows
    * Fix possibly broken XML on Windows
    * Require Content-Type header for PUT requests
    * Fix on-connect and on-disconnect script STDIN/STDOUT/STDERR
      corruption due to shared file descriptors.
    * Fix JSON access by adding support for global and mount specific
      custom HTTP headers

Known issues

    * HTTP PUT implementation currently doesn?t support
      chunked encoding yet.
    * HTTP PUT with ?Expect: 100-Continue? receives first a ?100? and
      soon after a ?200?, instead of the ?200? at end of transmission.
    * Caution should be exercised when using <on-connect> or
      <on-disconnect>, as there is a small chance of stream file
      descriptors being mixed up with script file descriptors, if the
      FD numbers go above 1024. This will be further addressed in the
      next Icecast release.
    * Don?t use comments inside <http-headers> as it will prevent
      processing of further <header> tags.
    * Web interface shows Login when using just stream_auth.


Change log:
http://svn.xiph.org/icecast/tags/icecast-2.4.1/ChangeLog

Source tar ball:
http://downloads.xiph.org/releases/icecast/icecast-2.4.1.tar.gz

Windows build:
http://downloads.xiph.org/releases/icecast/icecast_win32_2.4.1.zip


Soon I'll also update the OBS repositories from 2.4.0 to 2.4.1:
https://build.opensuse.org/package/show?package=icecast&project=home%3Adm8tbr
The package repositories are here:
http://download.opensuse.org/repositories/home:/dm8tbr/
While the packages don't go through extensive testing, they should work
fine, please report any issues you encounter on the icecast mailing list.


Cheers

Thomas


From thomas at ruecker.fi  Thu Nov 20 15:42:11 2014
From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=)
Date: Thu, 20 Nov 2014 15:42:11 +0000
Subject: [Icecast] [Icecast-dev]  Icecast 2.4.1 release
In-Reply-To: <546DB270.8090301@ruecker.fi>
References: <546DB270.8090301@ruecker.fi>
Message-ID: <546E0BD3.3030401@ruecker.fi>

Hi,

Quick update below.

On 11/20/2014 09:20 AM, "Thomas B. R?cker" wrote:
> This is to announce the release of Icecast 2.4.1.
>
> Fixes
> [?]
>     * Fix on-connect and on-disconnect script STDIN/STDOUT/STDERR
>       corruption due to shared file descriptors.

On request of the RedHat security team to the oss-security list, MITRE
has assigned this issue the following identifier:

CVE-2014-9018


I'd like to thank the Debian and RedHat teams for taking care of Icecast
and this issue.

Also I'd like to remind everyone, that 2.4.0?2.4.1 is a pure bug-fix
release and a real no-brainer to upgrade, please do so.


Cheers

Thomas



From sm at noisynotes.com  Thu Nov 20 16:41:59 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 20 Nov 2014 11:41:59 -0500
Subject: [Icecast] Problem Starting IceS
Message-ID: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>

I installed IceS version 2.33. libshout.so.3, which is a symlink to
libshout.so.3.2.0, is located in /usr/lib64. That's where the Red Hat
Package Manager put it. I have a line in /etc/ld.so.conf:

/usr/lib64

to make sure the shared object library gets loaded. According to the
output from 'ldconfig -p|grep libshout' it
has. When I start IceS, I get:

ices: error while loading shared libraries: libshout.so.3: cannot open
shared object: no such file or directory

Every analysis of this error points to a missing shared object library
(.so), but it's there.

$ ls -al /usr/lib64/libshout*
lrwxrwxrwx 1 root root    17 Aug 19 01:59 /usr/lib64/libshout.so.3 ->
libshout.so.3.2.0
-rwxr-xr-x 1 root root 77016 Aug  3  2013 /usr/lib64/libshout.so.3.2.0

The Linux account from which I am attempting to start IceS has been
added to the line in /etc/group (maybe not the best practice, but it
serves a purpose), so I don't think it's a read permissions problem.

Your kind assistance, please, is most appreciated in solving this one.


From geoff at QuiteLikely.com  Thu Nov 20 17:38:31 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Thu, 20 Nov 2014 19:38:31 +0200 (IST)
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>
Message-ID: <alpine.DEB.2.02.1411201937220.3835@voldemort.home>

On Thu, 20 Nov 2014, Steve Matzura wrote:

> ices: error while loading shared libraries: libshout.so.3: cannot open
> shared object: no such file or directory

As root, run:

ldconfig

Then try running it.

HTH,
Geoff.



From sm at noisynotes.com  Thu Nov 20 18:57:43 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 20 Nov 2014 13:57:43 -0500
Subject: [Icecast] Problem Starting IceS
Message-ID: <daes6adstm76s83ijk14413q8vdjl7i5tp@4ax.com>

Before I forget something else, I also ran:

ldd /usr/local/bin/ices|grep libshout.so.3

And what to my wond'ring eyes did appear, but 'libshout.s0.3 not
found"! How is this possible? Did something go wrong with the
installation of ices?


From sm at noisynotes.com  Thu Nov 20 18:51:25 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 20 Nov 2014 13:51:25 -0500
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <alpine.DEB.2.02.1411201937220.3835@voldemort.home>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>
	<alpine.DEB.2.02.1411201937220.3835@voldemort.home>
Message-ID: <5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>

On Thu, 20 Nov 2014 19:38:31 +0200 (IST), you wrote:

>On Thu, 20 Nov 2014, Steve Matzura wrote:
>
>> ices: error while loading shared libraries: libshout.so.3: cannot open
>> shared object: no such file or directory
>
>As root, run:
>
>ldconfig
>
>Then try running it.

Sorry, I forgot to report that I did that, too. Same error.


From thomas at ruecker.fi  Thu Nov 20 19:26:30 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 20 Nov 2014 19:26:30 +0000
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>	<alpine.DEB.2.02.1411201937220.3835@voldemort.home>
	<5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>
Message-ID: <546E4066.8080305@ruecker.fi>

On 11/20/2014 06:51 PM, Steve Matzura wrote:
> On Thu, 20 Nov 2014 19:38:31 +0200 (IST), you wrote:
>
>> On Thu, 20 Nov 2014, Steve Matzura wrote:
>>
>>> ices: error while loading shared libraries: libshout.so.3: cannot open
>>> shared object: no such file or directory
>> As root, run:
>>
>> ldconfig
>>
>> Then try running it.
> Sorry, I forgot to report that I did that, too. Same error.

Which version of RedHat is this?
Could this be a x86 vs amd64 thing? Just to be sure run "file" on the
binary?

Cheers

Thomas



From sm at noisynotes.com  Fri Nov 21 01:21:33 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Thu, 20 Nov 2014 20:21:33 -0500
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <546E4066.8080305@ruecker.fi>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>	<alpine.DEB.2.02.1411201937220.3835@voldemort.home>
	<5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>
	<546E4066.8080305@ruecker.fi>
Message-ID: <8l3t6a52ki3d45ad3nqcohq6gna23pf64j@4ax.com>

Thomas:

On Thu, 20 Nov 2014 19:26:30 +0000, you wrote:

>Which version of RedHat is this?

Fedora release 20 (Heisenbug)

>Could this be a x86 vs amd64 thing? Just to be sure run "file" on the
>binary?

The processor is definitely a 64-bit processor, even though that's not
verified with the above version name. However, I'm the one who
installed it, I know it's the 64-bit edition.

Now here's where it gets interesting.

[root at p2 admin]# find / -name ice es
/usr/bin/ices
/usr/local/bin/ices
/etc/logrotate.d/ices
/var/log/ices
/home/admin/ices
[root at p2 admin]# ls -al /usr/bin/ices
-rwxr-xr-x 1 root root 101672 Feb 15  2013 /usr/bin/ices
[root at p2 admin]# file /usr/bin/ices
/usr/bin/ices: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.32,
BuildID[sha1]=f45c33d35277ac27e9d9f4d61c68bcd5ec5df7d4, stripped
[root at p2 admin]# ls -al /usr/local/bin/ices
-rwxr-xr-x 1 admin admin 155572 May  1  2009 /usr/local/bin/ices
[root at p2 admin]# file /usr/local/bin/ices
/usr/local/bin/ices: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.1,
not stripped

And the next interesting thing, after answering the question of how I
wound up with a 32- *and* a 64-bit version, is that /usr/local/bin
(the location of the 32-bit version) comes immediately before /usr/bin
(the location of the 64-bit version in the $PATH environment symbol.


From geoff at QuiteLikely.com  Fri Nov 21 08:16:41 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 10:16:41 +0200 (IST)
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <8l3t6a52ki3d45ad3nqcohq6gna23pf64j@4ax.com>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>
	<alpine.DEB.2.02.1411201937220.3835@voldemort.home>
	<5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>
	<546E4066.8080305@ruecker.fi>
	<8l3t6a52ki3d45ad3nqcohq6gna23pf64j@4ax.com>
Message-ID: <alpine.DEB.2.02.1411211014130.3835@voldemort.home>

On Thu, 20 Nov 2014, Steve Matzura wrote:

> /usr/bin/ices
> /usr/local/bin/ices

Looks like you have two copies of ices installed.

I'm not very familiar with Redhat but I would have expected the version in 
/usr/local to be a version locally compiled, which makes it odd that it 
would be 32-bit on a 64-bit system.

Geoff.



From maartensvo at live.nl  Fri Nov 21 08:52:02 2014
From: maartensvo at live.nl (Maarten S)
Date: Fri, 21 Nov 2014 08:52:02 +0000
Subject: [Icecast] =?utf-8?q?Icecast_concept?=
Message-ID: <DUB407-EAS374035E584038065F3920ECA770@phx.gbl>


Hi,




I have installed Icecast on a VPS server as trial set up. Works very well and easy to understand. Thanks!


This does lead to 2 questions:


My intent is to set up a server to host various sources, providing each one of them their dedicated stream channel. If I have enough bandwidth, what is the maximum number of sources in Icecast that can be set up and streamed at the same time?


The documentation of Icecast states "It is very versatile in that new formats can be added". Does this meam also other formats than Ogg Vorbis or MP3 can be streamed?





Thanks and best regards, 


Maarten

Netherlands

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141121/51411676/attachment.htm>

From info at events47.de  Fri Nov 21 10:17:57 2014
From: info at events47.de (=?ISO-8859-15?Q?Peter_R=F6hl?=)
Date: Fri, 21 Nov 2014 11:17:57 +0100
Subject: [Icecast] Upgrade
Message-ID: <546F1155.2060908@events47.de>

Hi!
I am running Version 2.3.2 together with liquid soap on a debian System. 
everything works fine.
What is the easiest way to upgrade?

Save the config xml and web-folder, uninstall 2.3.2, install the latest 
release,restore the config xml and the web-folder?

Are there known issues with the latest release and liquid soap?

Thank you very much!

Peter Roehl




-- 
Peter R?hl
Phone: 0361 78029990
Fax: 0361 78029989
info at events47.de
http://www.events47.com,
Am Buchenberg 2, 99097 Erfurt



From geoff at QuiteLikely.com  Fri Nov 21 10:28:39 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 12:28:39 +0200 (IST)
Subject: [Icecast] Upgrade
In-Reply-To: <546F1155.2060908@events47.de>
References: <546F1155.2060908@events47.de>
Message-ID: <alpine.DEB.2.02.1411211225480.3835@voldemort.home>

On Fri, 21 Nov 2014, Peter R?hl wrote:

> I am running Version 2.3.2 together with liquid soap on a debian System.

I just looked.  Backports has a newer version but it's currently still 
2.4.0.  You may want to wait for it to move to 2.4.1 if you want to use 
that package.

If it's the security fixes you're after, you may find a security update 
is issued for Wheezy's 2.3.2 package in due course.

I'd never actually looked in Backports for a newer version and I'm 
interested in trying it myself.  But I'll wait for 2.4.1 before I try it.

Cheers,
Geoff.

From thomas at ruecker.fi  Fri Nov 21 10:29:16 2014
From: thomas at ruecker.fi (=?ISO-8859-15?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 21 Nov 2014 10:29:16 +0000
Subject: [Icecast] Upgrade
In-Reply-To: <546F1155.2060908@events47.de>
References: <546F1155.2060908@events47.de>
Message-ID: <546F13FC.4040001@ruecker.fi>

Hi,

On 11/21/2014 10:17 AM, Peter R?hl wrote:
> Hi!
> I am running Version 2.3.2 together with liquid soap on a debian System. 
> everything works fine.
> What is the easiest way to upgrade?

This sounds like old-stable, so you won't find any backports.
You'll have two choices:
- Rebuild the source package (once 2.4.1 hits SID)
- Install the binary package that I maintain for Icecast.org on OBS
(once I release 2.4.1 there)
Both will probably be mentioned here on the list.

> Save the config xml and web-folder, uninstall 2.3.2, install the latest 
> release,restore the config xml and the web-folder?

No, that shouldn't be necessary. Backing those up won't hurt, but if you
use a deb package then things should be taken care of automagically.


> Are there known issues with the latest release and liquid soap?

We are not aware of any issues with liquidsoap.

Unrelated to liquidsoap, if you use mountpoint credentials to update
metadata for a stream, but are on a different IP than the connected
source client, that will fail.


Cheers

Thomas



From geoff at QuiteLikely.com  Fri Nov 21 10:34:39 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 12:34:39 +0200 (IST)
Subject: [Icecast] Upgrade
In-Reply-To: <546F13FC.4040001@ruecker.fi>
References: <546F1155.2060908@events47.de> <546F13FC.4040001@ruecker.fi>
Message-ID: <alpine.DEB.2.02.1411211233480.3835@voldemort.home>

On Fri, 21 Nov 2014, "Thomas B. R?cker" wrote:

> On 11/21/2014 10:17 AM, Peter R?hl wrote:
>> I am running Version 2.3.2 together with liquid soap on a debian System.
>
> This sounds like old-stable, so you won't find any backports.

Wheezy has 2.3.2-9+deb7u2

Geoff.

From thomas at ruecker.fi  Fri Nov 21 10:37:17 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 21 Nov 2014 10:37:17 +0000
Subject: [Icecast] Icecast concept
In-Reply-To: <DUB407-EAS374035E584038065F3920ECA770@phx.gbl>
References: <DUB407-EAS374035E584038065F3920ECA770@phx.gbl>
Message-ID: <546F15DD.2060506@ruecker.fi>

Hi,
On 11/21/2014 08:52 AM, Maarten S wrote:
> I have installed Icecast on a VPS server as trial set up. Works very
> well and easy to understand. Thanks!
>
> This does lead to 2 questions:
>
> My intent is to set up a server to host various sources, providing
> each one of them their dedicated stream channel. If I have enough
> bandwidth, what is the maximum number of sources in Icecast that can
> be set up and streamed at the same time?

Most users won't reach that limit. Without further modifications, I'd
expect it to be in the hundreds. There is currently no known limit when
it comes to the number of listeners. Most installations run out of
bandwidth before they reach any significant system load - to spell it
out it's at least tens of thousands.
I know of instances that run up to 3000 streams in parallel, but I think
there the Icecast code had to be modified to achieve this.


> The documentation of Icecast states "It is very versatile in that new
> formats can be added". Does this meam also other formats than Ogg
> Vorbis or MP3 can be streamed?

Yes, we also officially support Opus (inside an Ogg container), Theora
and WebM, to name the most popular ones.
Known to work, but not officially supported are codecs like AAC and
h.264, but there we simply pass through the stream in "legacy mode" to
avoid any possible IPR issues.


Cheers

Thomas



From sm at noisynotes.com  Fri Nov 21 10:45:20 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 05:45:20 -0500
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <alpine.DEB.2.02.1411211014130.3835@voldemort.home>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>
	<alpine.DEB.2.02.1411201937220.3835@voldemort.home>
	<5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>
	<546E4066.8080305@ruecker.fi>
	<8l3t6a52ki3d45ad3nqcohq6gna23pf64j@4ax.com>
	<alpine.DEB.2.02.1411211014130.3835@voldemort.home>
Message-ID: <fq5u6al3ufa6s4msr35ngoasto6riup029@4ax.com>


On Fri, 21 Nov 2014 10:16:41 +0200 (IST), you wrote:

>On Thu, 20 Nov 2014, Steve Matzura wrote:
>
>> /usr/bin/ices
>> /usr/local/bin/ices
>
>Looks like you have two copies of ices installed.
>
>I'm not very familiar with Redhat but I would have expected the version in 
>/usr/local to be a version locally compiled, which makes it odd that it 
>would be 32-bit on a 64-bit system.
>
>Geoff.

And therein lies the conundrum--how'd it get there? I'm the only one
had his hands on this box since I put it up in August.

So, to remedy this, should I remove ices, clean up after it, and
re-install it? Or maybe just remove the 32-bit file?


From sm at noisynotes.com  Fri Nov 21 12:14:24 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 07:14:24 -0500
Subject: [Icecast] Problem Starting IceS
In-Reply-To: <fq5u6al3ufa6s4msr35ngoasto6riup029@4ax.com>
References: <ou5s6atf174tefcdpku0kaiggo0u1uepje@4ax.com>
	<alpine.DEB.2.02.1411201937220.3835@voldemort.home>
	<5uds6apj29qd8d5pdafbtqe6hjtkm2pqt7@4ax.com>
	<546E4066.8080305@ruecker.fi>
	<8l3t6a52ki3d45ad3nqcohq6gna23pf64j@4ax.com>
	<alpine.DEB.2.02.1411211014130.3835@voldemort.home>
	<fq5u6al3ufa6s4msr35ngoasto6riup029@4ax.com>
Message-ID: <52bu6al2fnfjonh4639l0mdbg47j2aj9af@4ax.com>

Oh dear, I suspect I've put my foot in it this time! Turns out,
someone copied the contents of an entire folder from another system
into /usr/local/bin, along with which came a 32-bit copy of IceS that
should not have come along for the ride. All fixed now.


From info at events47.de  Fri Nov 21 12:53:05 2014
From: info at events47.de (=?ISO-8859-1?Q?Peter_R=F6hl?=)
Date: Fri, 21 Nov 2014 13:53:05 +0100
Subject: [Icecast] Upgrade
In-Reply-To: <alpine.DEB.2.02.1411211233480.3835@voldemort.home>
References: <546F1155.2060908@events47.de> <546F13FC.4040001@ruecker.fi>
	<alpine.DEB.2.02.1411211233480.3835@voldemort.home>
Message-ID: <546F35B1.3010808@events47.de>

thx you all so far, i will try it asap! :)



Am 21.11.2014 11:34, schrieb Geoff Shang:
> On Fri, 21 Nov 2014, "Thomas B. R?cker" wrote:
>
>> On 11/21/2014 10:17 AM, Peter R?hl wrote:
>>> I am running Version 2.3.2 together with liquid soap on a debian 
>>> System.
>>
>> This sounds like old-stable, so you won't find any backports.
>
> Wheezy has 2.3.2-9+deb7u2
>
> Geoff.
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Peter R?hl
Phone: 0361 78029990
Fax: 0361 78029989
info at events47.de
http://www.events47.com,
Am Buchenberg 2, 99097 Erfurt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141121/a59057e8/attachment.htm>

From sm at noisynotes.com  Fri Nov 21 13:45:35 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 08:45:35 -0500
Subject: [Icecast] Software running, but no audio
Message-ID: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>

Logs indicate everything's running correctly, my player says I'm
connected, and the Web page for the server says it's playing files,
but there's no audio. Strange. Any thoughts? Did I possibly convert
the MP3's to Ogg Vorbis incorrectly?


From thomas at ruecker.fi  Fri Nov 21 13:49:21 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 21 Nov 2014 13:49:21 +0000
Subject: [Icecast] Software running, but no audio
In-Reply-To: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>
References: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>
Message-ID: <546F42E1.5050307@ruecker.fi>

On 11/21/2014 01:45 PM, Steve Matzura wrote:
> Logs indicate everything's running correctly, my player says I'm
> connected, and the Web page for the server says it's playing files,
> but there's no audio. Strange. Any thoughts? 

Which player are you using? If it's not a web browser, then most desktop
players are notoriously horrible at content-type sensing (they ignore
HTTP headers and go for "file extension"), so make sure your mountpoint
name ends in ".ogg".

> Did I possibly convert
> the MP3's to Ogg Vorbis incorrectly?

Do the files play back directly fine? e.g. using ogg123, vlc, or avplay


Cheers

Thomas


From sm at noisynotes.com  Fri Nov 21 13:51:45 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 08:51:45 -0500
Subject: [Icecast] EZStream Question
Message-ID: <5ngu6at3b7chb0vu2h85r6hcpu7ki7plae@4ax.com>

Can it, or will it ever be able to, process .CUE files along with the
MP3 streams? If not, this would be a *VERY* VERY* valuable feature, as
a popular playout system in common use can now create .CUE files when
recording programs for later airing.


From thomas at ruecker.fi  Fri Nov 21 14:02:28 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 21 Nov 2014 14:02:28 +0000
Subject: [Icecast] EZStream Question
In-Reply-To: <5ngu6at3b7chb0vu2h85r6hcpu7ki7plae@4ax.com>
References: <5ngu6at3b7chb0vu2h85r6hcpu7ki7plae@4ax.com>
Message-ID: <546F45F4.4020509@ruecker.fi>

On 11/21/2014 01:51 PM, Steve Matzura wrote:
> Can it, or will it ever be able to, process .CUE files along with the
> MP3 streams? If not, this would be a *VERY* VERY* valuable feature, as
> a popular playout system in common use can now create .CUE files when
> recording programs for later airing.

I'm going to give the slightly disappointing answer:
"Patches welcome!"
I haven't heard from the maintainer of ez-stream in a very good while,
so don't expect any activity on their behalf.

If someone wants to sponsor the development of a patch, they can mention
this here or I can hook them up directly with some people capable of
doing that.


Cheers

Thomas


From geoff at QuiteLikely.com  Fri Nov 21 14:21:15 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 16:21:15 +0200 (IST)
Subject: [Icecast] Metadata configurablity in Icecast
Message-ID: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>

Hi,

On Fri, 21 Nov 2014, "Thomas B. R?cker" wrote:

> Unrelated to liquidsoap, if you use mountpoint credentials to update
> metadata for a stream, but are on a different IP than the connected
> source client, that will fail.

I would like to request that this be configurable somehow.  I agree that 
this is undesirable under most circumstances, but there are situations 
where this is required.

One example I can think of.  I was working for an organisation that needed 
to track metadata for royalty reporting.  The playout software in use sent 
metadata, including album and record label, to a PHP script via a get 
request.  This script filed it in a MySQL database, along with other 
details like date and time, source IP and listener count, and also passed 
the metadata on to the streaming server.

Such a setup would not work on current Icecast.

Another example was just posted to the mailing list.  The idea of being 
able to put details in a cue file which could be used to send metadata 
during the repeat of a live show.  Rather than needing support in the 
source client, an external utility could be fired off at the same time 
playout commences, and the metadata could be sent at the right time from 
potentially a different IP address.  The above-mentioned database, for 
example, could be used for this sort of thing in addition to its original 
purpose.

There are probably other applications.  I know of at least one regular 
poster to this list who has not upgraded their Icecast installation 
because they rely on this feature.

I would like to suggest a couple of possibilities.

1.  The ability to turn the feature on and off.  This may not be the best 
route but it may be the simplest to implement.

2.  An option to allow metadata from the local host as well as the source 
address.

3.  The ability to specify a whitelist of allowed IP addresses.

Being able to do this on a per mount basis as well as globally would be 
ideal.

Thoughts?

Geoff.

From jonathancandler_msa at q.com  Fri Nov 21 14:21:51 2014
From: jonathancandler_msa at q.com (Jonathan)
Date: Fri, 21 Nov 2014 07:21:51 -0700
Subject: [Icecast] EZStream Question
In-Reply-To: <546F45F4.4020509@ruecker.fi>
References: <5ngu6at3b7chb0vu2h85r6hcpu7ki7plae@4ax.com>
	<546F45F4.4020509@ruecker.fi>
Message-ID: <546F4A7F.2060504@q.com>

Another thing that I would like to comment on. Ezstream you can't do as 
much with... for example, as far as I know, you can't really schedule 
jingles or other things to that kind. of things. I would learn how to 
use liquidsoap sense it has a lot of stuff that you can do with it. We 
are running an internet radio station, and if you all would like to 
check it out, go to http://kjscradio.com
but, We use to use ezstream simply for an easy setup and quick 
configuration, and that's if you just want a simple automation system. 
That's all well and fine but, if you are looking for something that you 
can schedule something to be played at a later time, liquidsoap is the 
best way to do here... These are just     my 2 sense.
On 11/21/2014 7:02 AM, "Thomas B. R?cker" wrote:
> On 11/21/2014 01:51 PM, Steve Matzura wrote:
>> Can it, or will it ever be able to, process .CUE files along with the
>> MP3 streams? If not, this would be a *VERY* VERY* valuable feature, as
>> a popular playout system in common use can now create .CUE files when
>> recording programs for later airing.
> I'm going to give the slightly disappointing answer:
> "Patches welcome!"
> I haven't heard from the maintainer of ez-stream in a very good while,
> so don't expect any activity on their behalf.
>
> If someone wants to sponsor the development of a patch, they can mention
> this here or I can hook them up directly with some people capable of
> doing that.
>
>
> Cheers
>
> Thomas
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From brad at musatcha.com  Fri Nov 21 14:42:26 2014
From: brad at musatcha.com (Brad Isbell)
Date: Fri, 21 Nov 2014 08:42:26 -0600
Subject: [Icecast] Software running, but no audio
In-Reply-To: <546F42E1.5050307@ruecker.fi>
References: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>
	<546F42E1.5050307@ruecker.fi>
Message-ID: <CAELR-fBjBQKNvnSk_xh6Z=fLUt5t4TZ3pUs3N1gmfUx=_6TgPw@mail.gmail.com>

Thomas,
Do you by chance know which players are ignoring the content-type headers?
I have done quite a bit of testing for that exact issue but haven't ran
into any problems.  Perhaps I am testing the wrong players.

Thanks,

Brad Isbell
brad at musatcha.com
http://www.musatcha.com

On Fri, Nov 21, 2014 at 7:49 AM, "Thomas B. R?cker" <thomas at ruecker.fi>
wrote:

> On 11/21/2014 01:45 PM, Steve Matzura wrote:
> > Logs indicate everything's running correctly, my player says I'm
> > connected, and the Web page for the server says it's playing files,
> > but there's no audio. Strange. Any thoughts?
>
> Which player are you using? If it's not a web browser, then most desktop
> players are notoriously horrible at content-type sensing (they ignore
> HTTP headers and go for "file extension"), so make sure your mountpoint
> name ends in ".ogg".
>
> > Did I possibly convert
> > the MP3's to Ogg Vorbis incorrectly?
>
> Do the files play back directly fine? e.g. using ogg123, vlc, or avplay
>
>
> 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/20141121/e0706326/attachment.htm>

From thomas at ruecker.fi  Fri Nov 21 15:01:27 2014
From: thomas at ruecker.fi (=?ISO-8859-1?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 21 Nov 2014 15:01:27 +0000
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
Message-ID: <546F53C7.2010902@ruecker.fi>

On 11/21/2014 02:21 PM, Geoff Shang wrote:
> Hi,
>
> On Fri, 21 Nov 2014, "Thomas B. R?cker" wrote:
>
>> Unrelated to liquidsoap, if you use mountpoint credentials to update
>> metadata for a stream, but are on a different IP than the connected
>> source client, that will fail.
>
> I would like to request that this be configurable somehow.  I agree
> that this is undesirable under most circumstances, but there are
> situations where this is required.

It has been requested before and the answer is still the same, we have
it on our radar and it will happen in the future. If someone wants to
make sure it's in the $next_release, then possible avenues are:
- sending a patch (after discussing how to approach this, see below)
- sponsoring development of a patch (I'd expect this to be in the 0.5-2h
range)

2.4.2 is penciled in for early 2015 (end of year is unlikely on my
behalf due to 31C3 and such). Feature freeze would likely occur mid
December.


> I would like to suggest a couple of possibilities.
>
> 1.  The ability to turn the feature on and off.  This may not be the
> best route but it may be the simplest to implement.
>
> 2.  An option to allow metadata from the local host as well as the
> source address.
>
> 3.  The ability to specify a whitelist of allowed IP addresses.

I'm partial to KISS and just put a big switch in (option 1).
Just to be clear, *anyone* with mountpoint credentials is then able to
mess with metadata from anywhere... We disabled this completely for a
good reason (leaving it open to the administrator account).


> Being able to do this on a per mount basis as well as globally would
> be ideal.

Not sure if I want to carry the complexity for this. It's a niche
feature already, this would be a niche within a niche...


Cheers

Thomas



From geoff at QuiteLikely.com  Fri Nov 21 15:06:14 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 17:06:14 +0200 (IST)
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <546F53C7.2010902@ruecker.fi>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
	<546F53C7.2010902@ruecker.fi>
Message-ID: <alpine.DEB.2.02.1411211703250.3835@voldemort.home>

On Fri, 21 Nov 2014, "Thomas B. R?cker" wrote:

> On 11/21/2014 02:21 PM, Geoff Shang wrote:
>> I would like to request that this be configurable somehow.  I agree
>> that this is undesirable under most circumstances, but there are
>> situations where this is required.
>
> It has been requested before and the answer is still the same, we have
> it on our radar and it will happen in the future. If someone wants to
> make sure it's in the $next_release, then possible avenues are:
> - sending a patch (after discussing how to approach this, see below)
> - sponsoring development of a patch (I'd expect this to be in the 0.5-2h
> range)

How much money would be needed??

> I'm partial to KISS and just put a big switch in (option 1).
> Just to be clear, *anyone* with mountpoint credentials is then able to
> mess with metadata from anywhere... We disabled this completely for a
> good reason (leaving it open to the administrator account).

Oh I didn't realise the admin account could override this.  This makes it 
less pressing, though still nice to have.

Geoff.

From thomas at ruecker.fi  Fri Nov 21 15:10:20 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Fri, 21 Nov 2014 15:10:20 +0000
Subject: [Icecast] Software running, but no audio
In-Reply-To: <CAELR-fBjBQKNvnSk_xh6Z=fLUt5t4TZ3pUs3N1gmfUx=_6TgPw@mail.gmail.com>
References: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>	<546F42E1.5050307@ruecker.fi>
	<CAELR-fBjBQKNvnSk_xh6Z=fLUt5t4TZ3pUs3N1gmfUx=_6TgPw@mail.gmail.com>
Message-ID: <546F55DC.9000408@ruecker.fi>

Hi,

On 11/21/2014 02:42 PM, Brad Isbell wrote:
> Thomas,
> Do you by chance know which players are ignoring the content-type
> headers? I have done quite a bit of testing for that exact issue but
> haven't ran into any problems. Perhaps I am testing the wrong players.

I'm 100% sure only of Winamp right now, but there have been many many
more and it's a very frequent problem mentioned on IRC. I'm hesitant to
name any as I don't have test results at hand.
Someone? could make a wiki page of players and their support of things
like content-type, ogg chaining, Opus, etc.
http://wiki.xiph.org/Icecast/Players would be an appropriate place to
start such a table.

I'd recommend to test the usual suspects:
Winamp (all versions, yeah people still use this?), FooBar, XMMS, XMMS2,
MPD, vlc, avplay (libav), mplayer, Amarok, web browsers, ?
http://icecast.org/apps/#players for a couple more.

I'm sure we'd find a couple offenders in there. Famously Chrome (blink)
is still broken on chained Ogg, including Opus.


> On Fri, Nov 21, 2014 at 7:49 AM, "Thomas B. R?cker" <thomas at ruecker.fi
> <mailto:thomas at ruecker.fi>> wrote:
>
>     On 11/21/2014 01:45 PM, Steve Matzura wrote:
>     > Logs indicate everything's running correctly, my player says I'm
>     > connected, and the Web page for the server says it's playing files,
>     > but there's no audio. Strange. Any thoughts?
>
>     Which player are you using? If it's not a web browser, then most
>     desktop
>     players are notoriously horrible at content-type sensing (they ignore
>     HTTP headers and go for "file extension"), so make sure your
>     mountpoint
>     name ends in ".ogg".
>
>     > Did I possibly convert
>     > the MP3's to Ogg Vorbis incorrectly?
>
>     Do the files play back directly fine? e.g. using ogg123, vlc, or
>     avplay
>

Cheers

Thomas



From lion at lion.leolix.org  Fri Nov 21 15:59:42 2014
From: lion at lion.leolix.org (Philipp Schafft)
Date: Fri, 21 Nov 2014 15:59:42 +0000
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <alpine.DEB.2.02.1411211703250.3835@voldemort.home>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
	<546F53C7.2010902@ruecker.fi>
	<alpine.DEB.2.02.1411211703250.3835@voldemort.home>
Message-ID: <20141121155953.E5AC212CFE@grassland.keep-cool.org>

flum,

developer here :)

On Fri, 2014-11-21 at 17:06 +0200, Geoff Shang wrote:
> On Fri, 21 Nov 2014, "Thomas B. R?cker" wrote:
> 
> > On 11/21/2014 02:21 PM, Geoff Shang wrote:
> >> I would like to request that this be configurable somehow.  I agree
> >> that this is undesirable under most circumstances, but there are
> >> situations where this is required.
> >
> > It has been requested before and the answer is still the same, we have
> > it on our radar and it will happen in the future. If someone wants to
> > make sure it's in the $next_release, then possible avenues are:
> > - sending a patch (after discussing how to approach this, see below)
> > - sponsoring development of a patch (I'd expect this to be in the 0.5-2h
> > range)
> 
> How much money would be needed??

I talked with Mr. R?cker about this one.
We are going to have some other changes in the auth code soon^TM.
This may be related. So we aren't exactly sure how your request fits in
best.
So best delay that question to when I know what to do.

> > I'm partial to KISS and just put a big switch in (option 1).
> > Just to be clear, *anyone* with mountpoint credentials is then able to
> > mess with metadata from anywhere... We disabled this completely for a
> > good reason (leaving it open to the administrator account).
> 
> Oh I didn't realise the admin account could override this.  This makes it 
> less pressing, though still nice to have.

What is your schedule? How fast do you need it? Could we target a fix
for in about a week?

Also: would it be ok for you to have a global user that is allowed to do
that or does it need to be the source user or does it need to be any
source user (anyone allowed to stream to that mountpoint)?

That is a very important question to answer the above!

Thank you and have a good evening!

-- 
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/20141121/6dcb0d0b/attachment.sig>

From geoff at QuiteLikely.com  Fri Nov 21 16:34:21 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 18:34:21 +0200 (IST)
Subject: [Icecast] Metadata configurablity in Icecast
In-Reply-To: <20141121155953.E5AC212CFE@grassland.keep-cool.org>
References: <alpine.DEB.2.02.1411211606280.3835@voldemort.home>
	<546F53C7.2010902@ruecker.fi>
	<alpine.DEB.2.02.1411211703250.3835@voldemort.home>
	<20141121155953.E5AC212CFE@grassland.keep-cool.org>
Message-ID: <alpine.DEB.2.02.1411211831420.3835@voldemort.home>

On Fri, 21 Nov 2014, Philipp Schafft wrote:

> What is your schedule? How fast do you need it? Could we target a fix
> for in about a week?

Sorry, I didn't mean to cause a panic.

I don't have an immediate need for this feature.  I know others do, or at 
least might, and have always felt this should be configurable ever since 
it was first implemented.  I've never run an affected version in 
production so it has never affected me, but with the recent security 
fixes making me think about it and the metadata thing having been
  mentioned a few times lately, I finally spoke up.

Geoff.



From sm at noisynotes.com  Fri Nov 21 16:49:12 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 11:49:12 -0500
Subject: [Icecast] Software running, but no audio
In-Reply-To: <546F42E1.5050307@ruecker.fi>
References: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>
	<546F42E1.5050307@ruecker.fi>
Message-ID: <34ru6a9mel8ihvm1qh21ef20p6l8d57hpf@4ax.com>

On Fri, 21 Nov 2014 13:49:21 +0000, you wrote:

>On 11/21/2014 01:45 PM, Steve Matzura wrote:
>> Logs indicate everything's running correctly, my player says I'm
>> connected, and the Web page for the server says it's playing files,
>> but there's no audio. Strange. Any thoughts? 
>
>Which player are you using? If it's not a web browser, then most desktop
>players are notoriously horrible at content-type sensing (they ignore
>HTTP headers and go for "file extension"), so make sure your mountpoint
>name ends in ".ogg".

It's Winamp, and naming the mount point with .OGG could be a problem.
We may have to revert to IceS 0.4 because normally the audio stream is
in MP3 format, but when IceS takes over when there is no live
programming, it requires the files be in Ogg Vorbis now. I suspected
this would be a problem for us. I thought that if files were in Ogg
format, IceS would send them to Icecast and Icecast would re-encode
them or otherwise handle them appropriately.


From geoff at QuiteLikely.com  Fri Nov 21 16:54:29 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 21 Nov 2014 18:54:29 +0200 (IST)
Subject: [Icecast] Software running, but no audio
In-Reply-To: <34ru6a9mel8ihvm1qh21ef20p6l8d57hpf@4ax.com>
References: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>
	<546F42E1.5050307@ruecker.fi>
	<34ru6a9mel8ihvm1qh21ef20p6l8d57hpf@4ax.com>
Message-ID: <alpine.DEB.2.02.1411211852040.3835@voldemort.home>

On Fri, 21 Nov 2014, Steve Matzura wrote:

> It's Winamp, and naming the mount point with .OGG could be a problem.
> We may have to revert to IceS 0.4 because normally the audio stream is
> in MP3 format, but when IceS takes over when there is no live
> programming, it requires the files be in Ogg Vorbis now.

Ices 0.4 and Ices 2 were always considered separate programs and don't 
really duplicate the features of each other.  So yes, Ices 0.4 is what you 
want.

Icecast doesn't do any encoding or transcoding.  If you want to do that, 
you'll need to use some kind of transcoding utility.  But using Ices 0.4 
will likely work better in your situation.

Geoff.



From sm at noisynotes.com  Fri Nov 21 18:04:44 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 13:04:44 -0500
Subject: [Icecast] Software running, but no audio
In-Reply-To: <alpine.DEB.2.02.1411211852040.3835@voldemort.home>
References: <iagu6ata3hel258sh1kkosg5rnlp2g0ch5@4ax.com>
	<546F42E1.5050307@ruecker.fi>
	<34ru6a9mel8ihvm1qh21ef20p6l8d57hpf@4ax.com>
	<alpine.DEB.2.02.1411211852040.3835@voldemort.home>
Message-ID: <4lvu6a9tkvd1oblo05au7jrm5ej2e404im@4ax.com>

Affirmative. I'm off to do the deed now. Should I remove the old and
then build from source?

On Fri, 21 Nov 2014 18:54:29 +0200 (IST), you wrote:

>On Fri, 21 Nov 2014, Steve Matzura wrote:
>
>> It's Winamp, and naming the mount point with .OGG could be a problem.
>> We may have to revert to IceS 0.4 because normally the audio stream is
>> in MP3 format, but when IceS takes over when there is no live
>> programming, it requires the files be in Ogg Vorbis now.
>
>Ices 0.4 and Ices 2 were always considered separate programs and don't 
>really duplicate the features of each other.  So yes, Ices 0.4 is what you 
>want.
>
>Icecast doesn't do any encoding or transcoding.  If you want to do that, 
>you'll need to use some kind of transcoding utility.  But using Ices 0.4 
>will likely work better in your situation.
>
>Geoff.
>
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast


From sm at noisynotes.com  Fri Nov 21 21:10:56 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Fri, 21 Nov 2014 16:10:56 -0500
Subject: [Icecast] Building IceS 0.4
Message-ID: <6n9v6ah772epgj08vh22tjnradehrog2ho@4ax.com>

I've been through this once before, and passing the proverbial camel
through the eye of the proverbial needle seemed easier.

$ ./configure
...
configure:20721: checking for pkg-config
configure:20739: found /usr/bin/pkg-config
configure:20752: result: /usr/bin/pkg-config
configure:20768: /usr/bin/pkg-config couldn't find libshout. Try
adjusting PKG_CONFIG_PATH.
configure:20774: checking for shout-config
configure:20805: result: no
configure:21103: error: Could not find a usable libshout

I have /usr/lib64/libshout.so.3 present. Is this not the correct one?


From sm at noisynotes.com  Sat Nov 22 17:47:47 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Sat, 22 Nov 2014 12:47:47 -0500
Subject: [Icecast] Installing IceS 0.4 Binaries
Message-ID: <osi17a1urcsr4golduacp4ljg7fb6qpn46@4ax.com>

Since I'm getting nowhere with trying to build IceS 0.4 from source on
a Fedora 20 (Heisenbug) system, I thought I'd look for a binary
installation package. I found one, but it has lots of dependencies,
including Lame, which has 22 dependencies all on its own. I went
through this once before and made a right mess of things. Is there not
a complete package that can be installed that includes all the
interdependencies, or two or three that solve all the dependency
problems without making a huge mess?


From Cat_Changeling at yahoo.com  Mon Nov 24 08:31:33 2014
From: Cat_Changeling at yahoo.com (LordFeline)
Date: Mon, 24 Nov 2014 00:31:33 -0800
Subject: [Icecast] Building IceS 0.4
References: <6n9v6ah772epgj08vh22tjnradehrog2ho@4ax.com>
Message-ID: <EA31F742315A4351B7A4D3D2544CEC49@D51SS>

Somehow I had the impressions
that IceS 0.4 Either would not compile under a 64 bit OS
Or was not compatible with a 64 bit OS In General

I would Love to hear I Was Wrong....

That Ices 2 Sends ogg streams I can handle
But that it Won't Read mp3 makes it Non-viable for me
I can't afford to replace the extensive mp3 Library

----- Original Message ----- 
From: "Steve Matzura" <sm at noisynotes.com>
To: "ic" <icecast at xiph.org>
Sent: Friday, November 21, 2014 1:10 PM
Subject: [Icecast] Building IceS 0.4


> I've been through this once before, and passing the proverbial camel
> through the eye of the proverbial needle seemed easier.
> 
> $ ./configure
> ...
> configure:20721: checking for pkg-config
> configure:20739: found /usr/bin/pkg-config
> configure:20752: result: /usr/bin/pkg-config
> configure:20768: /usr/bin/pkg-config couldn't find libshout. Try
> adjusting PKG_CONFIG_PATH.
> configure:20774: checking for shout-config
> configure:20805: result: no
> configure:21103: error: Could not find a usable libshout
> 
> I have /usr/lib64/libshout.so.3 present. Is this not the correct one?
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From sm at noisynotes.com  Tue Nov 25 15:25:15 2014
From: sm at noisynotes.com (Steve Matzura)
Date: Tue, 25 Nov 2014 10:25:15 -0500
Subject: [Icecast] Building IceS 0.4
In-Reply-To: <EA31F742315A4351B7A4D3D2544CEC49@D51SS>
References: <6n9v6ah772epgj08vh22tjnradehrog2ho@4ax.com>
	<EA31F742315A4351B7A4D3D2544CEC49@D51SS>
Message-ID: <bk797ahlade1bokuc5rkk83eqfacgt9ifq@4ax.com>

I wound up finding and using an IceS augmentation called Centova Cast,
which built, made and installed without a single error on my 64-bit
system. It's IceS 0.4 with a couple additions. It's running now and
behaving as it should, so this might be a solution for you as well.
The install script is intense. It downloads everything you need,
resolves dependencies, installs them, logs everything to the console,
and generally just works out great for my needs.

On Mon, 24 Nov 2014 00:31:33 -0800, you wrote:

>Somehow I had the impressions
>that IceS 0.4 Either would not compile under a 64 bit OS
>Or was not compatible with a 64 bit OS In General
>
>I would Love to hear I Was Wrong....
>
>That Ices 2 Sends ogg streams I can handle
>But that it Won't Read mp3 makes it Non-viable for me
>I can't afford to replace the extensive mp3 Library
>
>----- Original Message ----- 
>From: "Steve Matzura" <sm at noisynotes.com>
>To: "ic" <icecast at xiph.org>
>Sent: Friday, November 21, 2014 1:10 PM
>Subject: [Icecast] Building IceS 0.4
>
>
>> I've been through this once before, and passing the proverbial camel
>> through the eye of the proverbial needle seemed easier.
>> 
>> $ ./configure
>> ...
>> configure:20721: checking for pkg-config
>> configure:20739: found /usr/bin/pkg-config
>> configure:20752: result: /usr/bin/pkg-config
>> configure:20768: /usr/bin/pkg-config couldn't find libshout. Try
>> adjusting PKG_CONFIG_PATH.
>> configure:20774: checking for shout-config
>> configure:20805: result: no
>> configure:21103: error: Could not find a usable libshout
>> 
>> I have /usr/lib64/libshout.so.3 present. Is this not the correct one?
>> _______________________________________________
>> 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 Cat_Changeling at yahoo.com  Tue Nov 25 16:27:32 2014
From: Cat_Changeling at yahoo.com (LordFeline)
Date: Tue, 25 Nov 2014 08:27:32 -0800
Subject: [Icecast] Building IceS 0.4
References: <6n9v6ah772epgj08vh22tjnradehrog2ho@4ax.com><EA31F742315A4351B7A4D3D2544CEC49@D51SS>
	<bk797ahlade1bokuc5rkk83eqfacgt9ifq@4ax.com>
Message-ID: <B2C5208A0A28448E8BB7C5C0ACD2C0F4@D51SS>

Excellent :D
Thank You Very Much For the Pointer

----- Original Message ----- 
From: "Steve Matzura" <sm at noisynotes.com>
To: "Icecast streaming server user discussions" <icecast at xiph.org>
Sent: Tuesday, November 25, 2014 7:25 AM
Subject: Re: [Icecast] Building IceS 0.4


>I wound up finding and using an IceS augmentation called Centova Cast,
> which built, made and installed without a single error on my 64-bit
> system. It's IceS 0.4 with a couple additions. It's running now and
> behaving as it should, so this might be a solution for you as well.
> The install script is intense. It downloads everything you need,
> resolves dependencies, installs them, logs everything to the console,
> and generally just works out great for my needs.
> 
> On Mon, 24 Nov 2014 00:31:33 -0800, you wrote:
> 
>>Somehow I had the impressions
>>that IceS 0.4 Either would not compile under a 64 bit OS
>>Or was not compatible with a 64 bit OS In General
>>
>>I would Love to hear I Was Wrong....
>>
>>That Ices 2 Sends ogg streams I can handle
>>But that it Won't Read mp3 makes it Non-viable for me
>>I can't afford to replace the extensive mp3 Library
>>
>>----- Original Message ----- 
>>From: "Steve Matzura" <sm at noisynotes.com>
>>To: "ic" <icecast at xiph.org>
>>Sent: Friday, November 21, 2014 1:10 PM
>>Subject: [Icecast] Building IceS 0.4
>>
>>
>>> I've been through this once before, and passing the proverbial camel
>>> through the eye of the proverbial needle seemed easier.
>>> 
>>> $ ./configure
>>> ...
>>> configure:20721: checking for pkg-config
>>> configure:20739: found /usr/bin/pkg-config
>>> configure:20752: result: /usr/bin/pkg-config
>>> configure:20768: /usr/bin/pkg-config couldn't find libshout. Try
>>> adjusting PKG_CONFIG_PATH.
>>> configure:20774: checking for shout-config
>>> configure:20805: result: no
>>> configure:21103: error: Could not find a usable libshout
>>> 
>>> I have /usr/lib64/libshout.so.3 present. Is this not the correct one?
>>> _______________________________________________
>>> 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 support at psrfm.org.au  Thu Nov 27 06:04:01 2014
From: support at psrfm.org.au (PSRFM Support)
Date: Thu, 27 Nov 2014 17:04:01 +1100
Subject: [Icecast] Streaming Stats Problem
Message-ID: <001a01d00a07$f0e6f0e0$d2b4d2a0$@org.au>

I run IceCast 2.3.2 at Port Stephens FM radio station for streaming our
broadcast feed. Most things work fine but there is a small glitch somewhere
that seems to drop the 'Source Level Stats' information after a few days.
The application must be stopped then started again to reconnect the 'Source
Level Stats'. It used to work fine some time back but not now.

 

The main reason for the need for these stats is that they are requested from
our studio music player (Station Playlist Studio) that collects current
listener data for display on the studio computer showing the number of
current listeners. 

 

I have not found a solution for this version 2.3.2 of IceCast. I have tried
to download and install a newer IceCast version 2.4.0 and 2.4.1, in the hope
that a patch has been provided, but when I expand the zip files there is no
executable file that runs the new version.

 

What am I doing wrong? I hope someone can help.

 

Thanks

 

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141127/ee2209ff/attachment.htm>

From epirat07 at gmail.com  Thu Nov 27 06:34:50 2014
From: epirat07 at gmail.com (Marvin Scholz)
Date: Thu, 27 Nov 2014 07:34:50 +0100
Subject: [Icecast] Streaming Stats Problem
In-Reply-To: <001a01d00a07$f0e6f0e0$d2b4d2a0$@org.au>
References: <001a01d00a07$f0e6f0e0$d2b4d2a0$@org.au>
Message-ID: <F26E096D-3744-4D7D-93CB-464022AAF815@gmail.com>

> I run IceCast 2.3.2 at Port Stephens FM radio station for streaming 
> our
> broadcast feed. Most things work fine but there is a small glitch 
> somewhere
> that seems to drop the 'Source Level Stats' information after a few 
> days.

It might be possible that this is a bug in 2.3.2, it would be great if 
you could
try out a recent version (2.4.1).

> but when I expand the zip files there is no
> executable file that runs the new version.

Please note that we dropped the Windows Service and GUI, to start 
Icecast you need to
run the icecast.bat file. (The config is located at the current dir, in 
the etc folder
and you might want to replace it with your config file.)


From 0turn1 at gmail.com  Thu Nov 27 10:21:09 2014
From: 0turn1 at gmail.com (Scott Winterstein)
Date: Thu, 27 Nov 2014 11:21:09 +0100
Subject: [Icecast] Streaming Stats Problem
In-Reply-To: <001a01d00a07$f0e6f0e0$d2b4d2a0$@org.au>
References: <001a01d00a07$f0e6f0e0$d2b4d2a0$@org.au>
Message-ID: <CA+3r0CJepSMy06Dx-yJtJ9FZW0-qWCxyVimU7tKC_zkvowvD+w@mail.gmail.com>

When you say source level stats... are you saying that you have a separate
"Thing" doing this and it suddenly disconnects at some point? Or is it part
of IceCast?


Mit freundlichen Gr??en
Scott Winterstein

EMAIL: 0turn1 at gmail dot com

On Thu, Nov 27, 2014 at 7:04 AM, PSRFM Support <support at psrfm.org.au> wrote:

> I run IceCast 2.3.2 at Port Stephens FM radio station for streaming our
> broadcast feed. Most things work fine but there is a small glitch somewhere
> that seems to drop the ?Source Level Stats? information after a few days.
> The application must be stopped then started again to reconnect the ?Source
> Level Stats?. It used to work fine some time back but not now.
>
>
>
> The main reason for the need for these stats is that they are requested
> from our studio music player (Station Playlist Studio) that collects
> current listener data for display on the studio computer showing the number
> of current listeners.
>
>
>
> I have not found a solution for this version 2.3.2 of IceCast. I have
> tried to download and install a newer IceCast version 2.4.0 and 2.4.1, in
> the hope that a patch has been provided, but when I expand the zip files
> there is no executable file that runs the new version.
>
>
>
> What am I doing wrong? I hope someone can help.
>
>
>
> Thanks
>
>
>
> John
>
> _______________________________________________
> 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/20141127/36a2bd44/attachment.htm>

From awi3 at live.com  Thu Nov 27 21:49:25 2014
From: awi3 at live.com (Alan Bowness)
Date: Thu, 27 Nov 2014 21:49:25 +0000
Subject: [Icecast] icecast2.xml or darkice.cfg?
Message-ID: <DUB111-DS14E1E4B719D1A3BBA64F8CEF710@phx.gbl>

Hi there,

I?m a bit stuck, not sure if I should be configuring the icecast.xml, or if I?m doing something wrong in the darkice.cfg.

Works perfect streaming from its self, but as soon as I add a shoutcast stream, it breaks ? commenting out the icecast section in darkice.cfg I have tried various combinations of configurations with no luck.

I am testing the possibilities in streaming to an on-line shoutcast server listen2myradio.com, I?ve input all the Ip?s, ports and passwords, yet, I still get an error ? from reports on the web it is a user/password/ports problem? not sure why, would I have to configure the .xml for the server or relay to the on-line server settings? Last time I changed the xml, it broke it.

I?ve a workaround but it means using an XP machine with winamp, and the shoutcast plugin at the remote location, which connects to my icecast stream, then winamp streams that to the on-line server, it?s a bit of a pain to say the least.

I?ve icecast installed (with darkice) on a raspberry pi on the mobile network that I would like to boot up, then stream direct to the on-line servers without user input, so that I can stream live audio from a remote location.

Hoping you could be of assistance.

Regards
Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20141127/da90d021/attachment.htm>

From thomas at ruecker.fi  Thu Nov 27 22:12:24 2014
From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 27 Nov 2014 22:12:24 +0000
Subject: [Icecast] icecast2.xml or darkice.cfg?
In-Reply-To: <DUB111-DS14E1E4B719D1A3BBA64F8CEF710@phx.gbl>
References: <DUB111-DS14E1E4B719D1A3BBA64F8CEF710@phx.gbl>
Message-ID: <5477A1C8.6090809@ruecker.fi>

On 11/27/2014 09:49 PM, Alan Bowness wrote:
> Hi there,
>  
> I?m a bit stuck, not sure if I should be configuring the icecast.xml,
> or if I?m doing something wrong in the darkice.cfg.
>  
> Works perfect streaming from its self, but as soon as I add a
> shoutcast stream, it breaks ? commenting out the icecast section in
> darkice.cfg I have tried various combinations of configurations with
> no luck.

I'm not sure what your problem is exactly. If it is with Icecast not
accepting a stream, then you should check the Icecast error.log.

I don't remember details, but I seem to remember darkice is not very
keen on verbose logging. Have you considered using a different source
client like Ices2?

If your problem is with Shoutcast, then we obviously can't help you.


Cheers

Thomas


From awi3 at live.com  Thu Nov 27 23:26:33 2014
From: awi3 at live.com (Alan Bowness)
Date: Thu, 27 Nov 2014 23:26:33 +0000
Subject: [Icecast] icecast2.xml or darkice.cfg?
In-Reply-To: <5477A1C8.6090809@ruecker.fi>
References: <DUB111-DS14E1E4B719D1A3BBA64F8CEF710@phx.gbl>
	<5477A1C8.6090809@ruecker.fi>
Message-ID: <DUB111-DS403FDF55BAC3A8E3683F4DEF710@phx.gbl>

Thanks for the prompt reply Thomas,
Well as an amateur, and newbie, I would not know reading logs does not mean 
anything to me as I have no idea what it means when I can actually find 
them, this is why I am so confused. Not too sure how to check the logs, 
maybe obvious to some, but alas I'm not quite acquainted with the walking 
yet.
I have searched for a very long time with issues streaming to a shoutcast 
server via icecast, just can't find anything out about it.
If I were to stream using icecast, would it be the icecast.xml I would have 
to configure for the shoutcast server, or.. just the darkice.cfg?

Icecast is working like a dream streaming live audio to anything that 
connects to it (the pi), just trying to push that live stream to a shoutcast 
server via the darkice.cfg.. I'm wondering if I should point anything from 
the icecast.xml to the shoutcast server, but last time I did that it broke - 
wasn't sure what I was doing anyway.

I may have to try something else I guess, but I hope I don't fox-up anything 
by  doing that, I've spent days configuring the little raspberry pi, hate to 
start all over. eesh..

Thanks any way
Alan

-----Original Message----- 
From: "Thomas B. R?cker"
Sent: Thursday, November 27, 2014 10:12 PM
To: icecast at xiph.org
Subject: Re: [Icecast] icecast2.xml or darkice.cfg?

On 11/27/2014 09:49 PM, Alan Bowness wrote:
> Hi there,
>
> I?m a bit stuck, not sure if I should be configuring the icecast.xml,
> or if I?m doing something wrong in the darkice.cfg.
>
> Works perfect streaming from its self, but as soon as I add a
> shoutcast stream, it breaks ? commenting out the icecast section in
> darkice.cfg I have tried various combinations of configurations with
> no luck.

I'm not sure what your problem is exactly. If it is with Icecast not
accepting a stream, then you should check the Icecast error.log.

I don't remember details, but I seem to remember darkice is not very
keen on verbose logging. Have you considered using a different source
client like Ices2?

If your problem is with Shoutcast, then we obviously can't help you.


Cheers

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



From geoff at QuiteLikely.com  Fri Nov 28 08:11:37 2014
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Fri, 28 Nov 2014 10:11:37 +0200 (IST)
Subject: [Icecast] icecast2.xml or darkice.cfg?
In-Reply-To: <DUB111-DS403FDF55BAC3A8E3683F4DEF710@phx.gbl>
References: <DUB111-DS14E1E4B719D1A3BBA64F8CEF710@phx.gbl>
	<5477A1C8.6090809@ruecker.fi>
	<DUB111-DS403FDF55BAC3A8E3683F4DEF710@phx.gbl>
Message-ID: <alpine.DEB.2.02.1411281003580.3835@voldemort.home>

On Thu, 27 Nov 2014, Alan Bowness wrote:

> I have searched for a very long time with issues streaming to a shoutcast
> server via icecast, just can't find anything out about it.
> If I were to stream using icecast, would it be the icecast.xml I would have
> to configure for the shoutcast server, or.. just the darkice.cfg?

Icecast isn't able to relay streams on to Shoutcast servers.

You've got two options.

1.  If you are able to configure the Shoutcast server, you can configure 
it to tune into your Icecast server just like any listener and relay the 
stream that way.  this is the best solution if you can do it as you only 
need to send the source once, but it requires you to be able to configure 
the Shoutcast server which you may not be able to do.

2.  If 1 isn't possible, you can configure Darkice to send to both 
servers.  simply include a [shoutcast-0] section in your config file along 
with the [icecast2-0] section that presumably already appears.

Note that darkice will encode this stream separately so the Pi will need 
to be able to encode two audio streams in real-time.

HTH,
Geoff.



From awi3 at live.com  Fri Nov 28 09:46:09 2014
From: awi3 at live.com (Alan Bowness)
Date: Fri, 28 Nov 2014 09:46:09 +0000
Subject: [Icecast] icecast2.xml or darkice.cfg?
In-Reply-To: <alpine.DEB.2.02.1411281003580.3835@voldemort.home>
References: <DUB111-DS14E1E4B719D1A3BBA64F8CEF710@phx.gbl><5477A1C8.6090809@ruecker.fi><DUB111-DS403FDF55BAC3A8E3683F4DEF710@phx.gbl>
	<alpine.DEB.2.02.1411281003580.3835@voldemort.home>
Message-ID: <DUB111-DS378827DDB02C3CEB48C714EF7E0@phx.gbl>

Thank you Geoff,

I think I will give that option 1 a go later.

As option 2 will not have it, even if I comment out the Icecast section, and 
just have the shoutcast section; i've tried different combination of config 
in that section and  get presented with various connection errors.

The two servers which I have access to, one of which I do know that there is 
a relay option, so I will check that out, this could be the answer I am 
looking for.
I will let you know how I get on with that option.

Thank you very much!

Regards
Alan


-----Original Message----- 
From: Geoff Shang
Sent: Friday, November 28, 2014 8:11 AM
To: Icecast streaming server user discussions
Subject: Re: [Icecast] icecast2.xml or darkice.cfg?

On Thu, 27 Nov 2014, Alan Bowness wrote:

> I have searched for a very long time with issues streaming to a shoutcast
> server via icecast, just can't find anything out about it.
> If I were to stream using icecast, would it be the icecast.xml I would 
> have
> to configure for the shoutcast server, or.. just the darkice.cfg?

Icecast isn't able to relay streams on to Shoutcast servers.

You've got two options.

1.  If you are able to configure the Shoutcast server, you can configure
it to tune into your Icecast server just like any listener and relay the
stream that way.  this is the best solution if you can do it as you only
need to send the source once, but it requires you to be able to configure
the Shoutcast server which you may not be able to do.

2.  If 1 isn't possible, you can configure Darkice to send to both
servers.  simply include a [shoutcast-0] section in your config file along
with the [icecast2-0] section that presumably already appears.

Note that darkice will encode this stream separately so the Pi will need
to be able to encode two audio streams in real-time.

HTH,
Geoff.

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