From mberger.tks2001 at fh-sbg.ac.at  Thu Dec  2 19:13:12 2004
From: mberger.tks2001 at fh-sbg.ac.at (Mathias Berger)
Date: Thu, 02 Dec 2004 20:13:12 +0100
Subject: [Icecast] icecast dies regulary
Message-ID: <41AF6948.7000504@fh-sbg.ac.at>

Hi,

I am running Icecast 2.1.0 on a Debian Sarge with a 2.6.8 Kernel.

After upgrading to the new version i have the problem that the icecast2
process. It is regularly dying after running 20-26 hours.

There are no messages in the icecast logfile nor in any other logfile.
The only message, which is written to the shell which started the
process, is

xsltApplyOneTemplate: template was not compiled
xsltSaveResultTo : unknown ouput method

Any ideas ?
Thanks in advance for your help!

Mathias

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

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

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

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

     <hostname>gjallar.radio-x-stream.at</hostname>

     <listen-socket>
         <port>80</port>
     </listen-socket>

     <!--<master-server>127.0.0.1</master-server>-->
     <!--<master-server-port>8001</master-server-port>-->
     <!--<master-update-interval>120</master-update-interval>-->
     <!--<master-password>hackme</master-password>-->
     <!--
     <relay>
         <server>127.0.0.1</server>
         <port>8001</port>
         <mount>/example.ogg</mount>
         <local-mount>/different.ogg</local-mount>

         <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
     </relay>
     -->

     <!-- Only define a <mount> section if you want to use advanced options,
          like alternative usernames or passwords
     <mount>
         <mount-name>/example-complex.ogg</mount-name>

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

         <max-listeners>1</max-listeners>
         <dump-file>/tmp/dump-example1.ogg</dump-file>
         <fallback-mount>/example2.ogg</fallback-mount>
     </mount>
     -->

     <fileserve>1</fileserve>

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

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

         <!-- Aliases: treat requests for 'source' path as being for
'dest' path
              May be made specific to a port or bound address using the
"port"
              and "bind-address" attributes.
           -->
         <!--
         <alias source="/foo" dest="/bar"/>
           -->
     </paths>

     <logging>
         <accesslog>access.log</accesslog>
         <errorlog>error.log</errorlog>
         <loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
     </logging>

     <security>
         <chroot>1</chroot>
         <changeowner>
             <user>icecast2</user>
             <group>icecast</group>
         </changeowner>
     </security>
</icecast>
########################




From karl at xiph.org  Thu Dec  2 20:32:50 2004
From: karl at xiph.org (Karl Heyes)
Date: 02 Dec 2004 20:32:50 +0000
Subject: [Icecast] icecast dies regulary
In-Reply-To: <41AF6948.7000504@fh-sbg.ac.at>
References: <41AF6948.7000504@fh-sbg.ac.at>
Message-ID: <1102019570.29603.7.camel@bogus.hackers.club>

On Thu, 2004-12-02 at 19:13, Mathias Berger wrote:
> Hi,
> 
> I am running Icecast 2.1.0 on a Debian Sarge with a 2.6.8 Kernel.
> 
> After upgrading to the new version i have the problem that the icecast2
> process. It is regularly dying after running 20-26 hours.

Check how it exits, ie do you get a core file (ulimit -c), if so build
icecast with debug, retest then send us the backtrace from the core.

> There are no messages in the icecast logfile nor in any other logfile.
> The only message, which is written to the shell which started the
> process, is
> 
> xsltApplyOneTemplate: template was not compiled
> xsltSaveResultTo : unknown ouput method

you should see plenty of messages in the log file, if not then you
really need to determine why logging is not working.

> Any ideas ?
> Thanks in advance for your help!

explain how icecast is being used, are relays involved, are mp3 streams
involved etc.  The references to xslt above would indicate some access
to the web interface of icecast.  Those error message are from libxslt
so that may indicate an .xsl file that has been changed, if so then make
sure it's valid.

karl.




From adam at xs4all.nl  Thu Dec  2 20:35:48 2004
From: adam at xs4all.nl (adam)
Date: Thu, 2 Dec 2004 21:35:48 +0100 (CET)
Subject: [Icecast] xiph
Message-ID: <20041202213450.D83240-100000@xs6.xs4all.nl>


hey all,

does anyone know what happened to the plan to overhaul the xiph website?

adam



Adam Hyde
~/.nz

r a d i o q u a l i a
http://www.radioqualia.net
Free as in 'media'



From giles at xiph.org  Thu Dec  2 21:21:33 2004
From: giles at xiph.org (Ralph Giles)
Date: Thu, 2 Dec 2004 13:21:33 -0800
Subject: [Icecast] xiph
In-Reply-To: <20041202213450.D83240-100000@xs6.xs4all.nl>
References: <20041202213450.D83240-100000@xs6.xs4all.nl>
Message-ID: <20041202212133.GA21219@ghostscript.com>

On Thu, Dec 02, 2004 at 09:35:48PM +0100, adam wrote:

> does anyone know what happened to the plan to overhaul the xiph website?

We hired someone, and Monty has been working with them on the new 
design. Unfortunately, the pro bono discount they gave us means
we don't get first priority on their time, so the back-and-forth
is taking a while.

So, some progress, but nothing to show.

 -r


From mberger.tks2001 at fh-sbg.ac.at  Fri Dec  3 12:30:12 2004
From: mberger.tks2001 at fh-sbg.ac.at (Mathias Berger)
Date: Fri, 03 Dec 2004 13:30:12 +0100
Subject: [Icecast] icecast dies regulary
In-Reply-To: <1102019570.29603.7.camel@bogus.hackers.club>
References: <41AF6948.7000504@fh-sbg.ac.at>
	<1102019570.29603.7.camel@bogus.hackers.club>
Message-ID: <41B05C54.9020100@fh-sbg.ac.at>

Hi Karl!

Thanks for your quick reply!

Karl Heyes wrote:

> On Thu, 2004-12-02 at 19:13, Mathias Berger wrote:
> 
>>Hi,
>>
>>I am running Icecast 2.1.0 on a Debian Sarge with a 2.6.8 Kernel.
>>
>>After upgrading to the new version i have the problem that the icecast2
>>process. It is regularly dying after running 20-26 hours.
> 
> 
> Check how it exits, ie do you get a core file (ulimit -c), if so build
> icecast with debug, retest then send us the backtrace from the core.
> 
No, there is no core file.

> 
>>There are no messages in the icecast logfile nor in any other logfile.
>>The only message, which is written to the shell which started the
>>process, is
>>
>>xsltApplyOneTemplate: template was not compiled
>>xsltSaveResultTo : unknown ouput method
> 
> 
> you should see plenty of messages in the log file, if not then you
> really need to determine why logging is not working.

Of course, there are a lot of messages in the logfile, but none of them 
can be related to the crash of the server. Or at least I cannot see any 
relation.

> 
> 
>>Any ideas ?
>>Thanks in advance for your help!
> 
> 
> explain how icecast is being used, are relays involved, are mp3 streams
> involved etc.  The references to xslt above would indicate some access
> to the web interface of icecast.  Those error message are from libxslt
> so that may indicate an .xsl file that has been changed, if so then make
> sure it's valid.

Icecast gets its data from darkice, which produces 6 streams (Three MP3 
and three OGG). At the moment there are no relays involved, but i'd like 
to activate them as soon as possible. Furthermore, I am using MRTG to do 
some statistics. Another computer is requesting every 5 minutes a xsl 
file for every stream and one xsl file to get the number of all listeners.

The file for all streams looks like this:
############
<xsl:stylesheet xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" 
version = "1.0" >
<xsl:output method="text" indent="yes" />
<xsl:template match = "/icestats" >
<xsl:value-of select="clients" />
</xsl:template>
</xsl:stylesheet>
############

And one of the files for each streams looks like this:
############
<xsl:stylesheet xmlns:xsl = "http://www.w3.org/1999/XSL/Transform" 
version = "1.0" >
<xsl:output method="text" indent="yes" />
<xsl:template match = "/icestats" >
<xsl:for-each select="source">
<xsl:if test="@mount='/live-hq.ogg'">
<xsl:value-of select="listeners" />
</xsl:if>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
############
I am no XML specialist, these files work and i hope that they are not 
the reason why icecast isn't working properly.

I didn't change the other xml files.

Mathias


From xiphmont at xiph.org  Fri Dec  3 05:12:41 2004
From: xiphmont at xiph.org (Monty)
Date: Fri, 3 Dec 2004 00:12:41 -0500
Subject: [Icecast] xiph
In-Reply-To: <20041202212133.GA21219@ghostscript.com>
References: <20041202213450.D83240-100000@xs6.xs4all.nl>
	<20041202212133.GA21219@ghostscript.com>
Message-ID: <20041203051241.GA20136@xiph.org>




On Thu, Dec 02, 2004 at 01:21:33PM -0800, Ralph Giles wrote:
> On Thu, Dec 02, 2004 at 09:35:48PM +0100, adam wrote:
> 
> > does anyone know what happened to the plan to overhaul the xiph website?
> 
> We hired someone, and Monty has been working with them on the new 
> design. Unfortunately, the pro bono discount they gave us means
> we don't get first priority on their time, so the back-and-forth
> is taking a while.
> 
> So, some progress, but nothing to show.

Well, we do have something to show, just not public things :-)

Monty


From carsten at chatlabel.de  Sun Dec  5 15:56:41 2004
From: carsten at chatlabel.de (Carsten Henkel)
Date: Sun, 5 Dec 2004 16:56:41 +0100
Subject: [Icecast] client-timeout
Message-ID: <43157788.20041205165641@chatlabel.de>

hi together,

  we use icecast 2.1 and have a big problem with the client-timeout. if
  our dj?s chance from one to another, all our listeners are
  disconected. i have found in the documentation at the point client-timeout
  "This does not seem to be used."
  is there an alternate way to hold the listeners at dj chance ?
  have a lot of thanks for your help.

  have a nice day

-- 
Mit freundlichen Gr?ssen
Carsten Henkel                          mailto:carsten at chatlabel.de


Wird das Nachdenken ?ber irgend ein Problem auf die lange Bank geschoben, dann bleibt erfahrungsgem?? keine Zeit, das Problem ?berhaupt gr?ndlich zudurchdenken. (C. West Churmann ) 

dieser Text ist zuf?llig gew?hlt und hat nichts mit dem Empf?nger der e-Mail zu tun.

Carsten Henkel
Passauer Stra?e 7
94577 Winzer
tel.: 0049 (0)180-3684398-360
fax.: 0049 (0)180-3684398-039

http://chatlabel.de
http://radio.chatlabel.de



From karl at xiph.org  Sun Dec  5 16:21:14 2004
From: karl at xiph.org (Karl Heyes)
Date: 05 Dec 2004 16:21:14 +0000
Subject: [Icecast] client-timeout
In-Reply-To: <43157788.20041205165641@chatlabel.de>
References: <43157788.20041205165641@chatlabel.de>
Message-ID: <1102263673.10887.5.camel@bogus.hackers.club>

On Sun, 2004-12-05 at 15:56, Carsten Henkel wrote:
> hi together,
> 
>   we use icecast 2.1 and have a big problem with the client-timeout. if
>   our dj?s chance from one to another, all our listeners are
>   disconected. i have found in the documentation at the point client-timeout
>   "This does not seem to be used."
>   is there an alternate way to hold the listeners at dj chance ?
>   have a lot of thanks for your help.

The use of fallback mounts or defining a relay that is local should
suffice for most people.

karl.




From webmaster at quadmore.com  Sun Dec  5 20:45:09 2004
From: webmaster at quadmore.com (Bertrand Szoghy)
Date: Sun, 05 Dec 2004 15:45:09 -0500
Subject: [Icecast] permissions, permissions
Message-ID: <1102279509.5066.9.camel@localhost>

Hello,

Clueless newbie using ices 0.4 and icecast 2.

Situation: a small closed network, no worries about security.

Error I am bumping into:
[devprog1 at localhost ices-0.4]$ ices
Logfile opened
Playing /home/devprog1/mp3/01.mp3
Error during send: Mount failed on http://127.0.0.1:8000/ices, error:
Login failed

Following are my two config files, could anyone help me out?

TIA,
Bert

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

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

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

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

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

    <!-- You can use these two if you only want a single listener -->
    <!--<port>8000</port> -->
    <!--<bind-address>127.0.0.1</bind-address>-->

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

    <!--<master-server>127.0.0.1</master-server>-->
    <!--<master-server-port>8001</master-server-port>-->
    <!--<master-update-interval>120</master-update-interval>-->
    <!--<master-password>hackme</master-password>-->
    <!--
    <relay>
        <server>127.0.0.1</server>
        <port>8001</port>
        <mount>/example.ogg</mount>
        <local-mount>/different.ogg</local-mount>

        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>
    -->

    <!-- Only define a <mount> section if you want to use advanced
options,
         like alternative usernames or passwords
    <mount>
        <mount-name>/example-complex.ogg</mount-name>

        <username>devprog1</username>
        <password>mypassword</password>

        <max-listeners>1</max-listeners>
        <dump-file>/tmp/dump-example1.ogg</dump-file>
        <burst-size>65536</burst-size>
        <fallback-mount>/example2.ogg</fallback-mount>
        <authentication type="htpasswd">
                <option name="filename" value="myauth"/>
                <option name="allow_duplicate_users" value="0"/>
        </authentication>
    </mount>
    -->

    <fileserve>1</fileserve>

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

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

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

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
      	<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
    </logging>

    <security>
        <chroot>0</chroot>
        <!--
        <changeowner>
            <user>nobody</user>
            <group>nogroup</group>
        </changeowner>
        -->
    </security>
</icecast>




<?xml version="1.0"?>
<ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices">
  <Playlist>
    <!-- This is the filename used as a playlist when using the builtin 
	 playlist handler. -->
    <File>/root/reference/software/icecast/ices-0.4/playlist.txt</File>
    <!-- Set this to 0 if you don't want to randomize your playlist, and
to
	 1 if you do. -->
    <Randomize>1</Randomize>
    <!-- One of builtin, perl, or python. -->
    <Type>builtin</Type>
    <!-- Module name to pass to the playlist handler if using  perl or
python.
	 If you use the builtin playlist handler then this is ignored -->
    <Module>ices</Module>
    <!-- Set this to the number of seconds to crossfade between tracks.
         Leave out or set to zero to disable crossfading (the default).
    <Crossfade>5</Crossfade>
    -->
  </Playlist>

  <Execution>
    <!-- Set this to 1 if you want ices to launch in the background as a
         daemon -->
    <Background>0</Background>
    <!-- Set this to 1 if you want to see more verbose output from ices
-->
    <Verbose>1</Verbose>
    <!-- This directory specifies where ices should put the logfile, cue
file
	 and pid file (if daemonizing). Don't use /tmp if you have l33t h4x0rz
         on your server. -->
    <BaseDirectory>/tmp</BaseDirectory>
  </Execution>

  <Stream>
    <Server>
      <!-- Hostname or ip of the icecast server you want to connect to
-->
      <Hostname>localhost</Hostname>
      <!-- Port of the same -->
      <Port>8000</Port>
      <!-- Encoder password on the icecast server -->
      <Password>mypassword</Password>
      <!-- Header protocol to use when communicating with the server.
           Shoutcast servers need "icy", icecast 1.x needs "xaudiocast",
and
	   icecast 2.x needs "http". -->
      <Protocol>http</Protocol>
    </Server>

    <!-- The name of the mountpoint on the icecast server --> 
    <Mountpoint>/ices</Mountpoint>
    <!-- The name of the dumpfile on the server for your stream. DO NOT
set
	 this unless you know what you're doing.
    <Dumpfile>ices.dump</Dumpfile>
    -->
    <!-- The name of you stream, not the name of the song! -->
    <Name>mp3</Name>
    <!-- Genre of your stream, be it rock or pop or whatever -->
    <Genre>Physics</Genre>
    <!-- Longer description of your stream -->
    <Description>mp3 Lectures on Physics</Description>
    <!-- URL to a page describing your stream -->
    <URL>http://localhost/</URL>
    <!-- 0 if you don't want the icecast server to publish your stream
on
	 the yp server, 1 if you do -->
    <Public>0</Public>

    <!-- Stream bitrate, used to specify bitrate if reencoding,
otherwise
	 just used for display on YP and on the server. Try to keep it
	 accurate -->
    <Bitrate>128</Bitrate>
    <!-- If this is set to 1, and ices is compiled with liblame support,
	 ices will reencode the stream on the fly to the stream bitrate. -->
    <Reencode>0</Reencode>
    <!-- Number of channels to reencode to, 1 for mono or 2 for stereo
-->
    <!-- Sampe rate to reencode to in Hz. Leave out for LAME's best
choice
    <Samplerate>44100</Samplerate>
    -->
    <Channels>1</Channels>
  </Stream>
</ices:Configuration>


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

From zotyalpb at freeweb.hu  Mon Dec  6 00:50:11 2004
From: zotyalpb at freeweb.hu (ZoTyA)
Date: Mon, 6 Dec 2004 01:50:11 +0100
Subject: [Icecast] On demand relay in icecast 2?
Message-ID: <06df01c4db2d$b3439ae0$0101a8c0@foo>

> On Sun, 2004-02-15 at 19:52, Joern Nettingsmeier wrote:
> > Michael Smith wrote:
> > > On Thursday 12 February 2004 03:05, v b wrote:
> > >
> > >>I'm using this on icecat 1.3.12 but it doesn't seem to work with
icecast
> > >>2.0.0. The relay starts as soon as icecast is started and does not
drop,
> > >>even if there are no clients. I've been over and over the docs and
can't
> > >>figure out what I'm doing wrong.
> > >
> > > Icecast2 does not currently support on-demand relaying.
> >
> > pity. are you planning to implement it, or are there reasons apart
> > from lack of time or interest?
> > i'd very much like to see this feature re-appear.

> If you are not too bothered about running more experimental code, then
> try my mods, I've added this weekend.

> http://www.xiph.org/~karl/icecast-2.0-kh26.tar.gz

> just add <on-demand>1</on-demand> to the relay definition. The bulk of
> the infrastructure to support on-demand relays should be going in CVS as
> it really deals with something else. The extra work for implementing
> on-demand specifically needs to be discussed before going into CVS


Hi!

I wanna ask when will be the on-demand relaying in the "stable" release?

I use debian sarge (testing) with icecast 2.1.0-1 currently.


ZoTyA




From zotyalpb at freemail.hu  Mon Dec  6 00:56:39 2004
From: zotyalpb at freemail.hu (ZoTyA)
Date: Mon, 6 Dec 2004 01:56:39 +0100
Subject: [Icecast] On demand relay in icecast 2?
Message-ID: <06fe01c4db2e$83e618d0$0101a8c0@foo>

> On Sun, 2004-02-15 at 19:52, Joern Nettingsmeier wrote:
> > Michael Smith wrote:
> > > On Thursday 12 February 2004 03:05, v b wrote:
> > >
> > >>I'm using this on icecat 1.3.12 but it doesn't seem to work with
icecast
> > >>2.0.0. The relay starts as soon as icecast is started and does not
drop,
> > >>even if there are no clients. I've been over and over the docs and
can't
> > >>figure out what I'm doing wrong.
> > >
> > > Icecast2 does not currently support on-demand relaying.
> >
> > pity. are you planning to implement it, or are there reasons apart
> > from lack of time or interest?
> > i'd very much like to see this feature re-appear.

> If you are not too bothered about running more experimental code, then
> try my mods, I've added this weekend.

> http://www.xiph.org/~karl/icecast-2.0-kh26.tar.gz

> just add <on-demand>1</on-demand> to the relay definition. The bulk of
> the infrastructure to support on-demand relays should be going in CVS as
> it really deals with something else. The extra work for implementing
> on-demand specifically needs to be discussed before going into CVS


Hi!

I wanna ask when will be the on-demand relaying in the "stable" release?

I use debian sarge (testing) with icecast 2.1.0-1 currently.


ZoTyA




From andy at benow.ca  Mon Dec  6 05:52:04 2004
From: andy at benow.ca (Andrew Taylor)
Date: Sun, 05 Dec 2004 22:52:04 -0700
Subject: [Icecast] Authentication and relays
Message-ID: <41B3F384.3090707@benow.ca>

Hello,

Just installed 2.1.0, and it seems to be working well.  I have a problem 
I thought user auth on 2.1.0 would fix, namely,  I want to control 
access to an icecast instance which is the source for the primary 
broadcast icecast.  [backstory: a few months ago, the stream was 
originally broadcasting directly from a box in the engineering room, 
encoding from a booth line.  Listeners would connect directly to this 
box to listen.  After a month broadcasting with this arrangement it 
became apparent that we were using too much of the overprepared and 
expensive university bandwidth (5 9s, etc), and procured, configured and 
initiated broadcast from another machine in a data center.  This new 
machine relays from the old machine in the engineering room and is the 
primary broadcast box for the station (cjsw.com).]  The problem is that 
users are still connecting directly to the (private) relay box, and not 
the new coloc box.    What I wish to do is to deny access to 
(non-relaying) listeners on the relay.  I was hoping to use the 2.1.0 
auth for this, but there is no <user> and <password> configuration for 
relays.  Another solution would be to rename the original relay mount 
points and adjust the public broadcaster settings accordingly, but I've 
found that the name of the mountpoint on the relay is used as the 
mountpoint on the relayer (ie, changing the source mount point to 
/new-mount.ogg causes the mount on the relaying box to change to 
/new-mount.ogg and not maintain /mount.ogg name, despite being specified 
in <local-mount>).

Have any dev's any advice?  Have these problems had light shone on them 
before?

Thanks,

Andy Taylor
(benow.ca/cjsw.com)

P.S. 2.0 has been a champ, handling months on continous broadcast, 40+ 
listeners at a time without a hiccup.  The foundation for great 
improvements in open broadcasting!




From adam at xs4all.nl  Mon Dec  6 09:31:49 2004
From: adam at xs4all.nl (adam)
Date: Mon, 6 Dec 2004 10:31:49 +0100 (CET)
Subject: [Icecast] ices, jack
Message-ID: <20041206103031.P74891-100000@xs6.xs4all.nl>

alo

i have seen some mention of an ices patch with support for jack...anyone
know where i can get this?

adam




From karl at xiph.org  Mon Dec  6 14:42:59 2004
From: karl at xiph.org (Karl Heyes)
Date: 06 Dec 2004 14:42:59 +0000
Subject: [Icecast] ices, jack
In-Reply-To: <20041206103031.P74891-100000@xs6.xs4all.nl>
References: <20041206103031.P74891-100000@xs6.xs4all.nl>
Message-ID: <1102344179.10887.11.camel@bogus.hackers.club>

On Mon, 2004-12-06 at 09:31, adam wrote:
> alo
> 
> i have seen some mention of an ices patch with support for jack...anyone
> know where i can get this?

The latest is in SVN under http://svn.xiph.org/icecast/branches/kh and
tarballs are available in http://mediacast1.com/~karl.  You will need
the libshout which is available there as well, I haven't fully tested
the patch for using libshout trunk yet.

karl.



From andy at earthsong.free-online.co.uk  Mon Dec  6 17:12:54 2004
From: andy at earthsong.free-online.co.uk (andy)
Date: Mon, 06 Dec 2004 17:12:54 +0000
Subject: [Icecast] Re: ices, jack
References: <20041206103031.P74891-100000@xs6.xs4all.nl>
	<1102344179.10887.11.camel@bogus.hackers.club>
Message-ID: <pan.2004.12.06.17.12.54.356527@earthsong.free-online.co.uk>

On Mon, 06 Dec 2004 14:42:59 +0000, Karl Heyes wrote:

> On Mon, 2004-12-06 at 09:31, adam wrote:
>> alo
>> 
>> i have seen some mention of an ices patch with support for jack...anyone
>> know where i can get this?
> 
> The latest is in SVN under http://svn.xiph.org/icecast/branches/kh and
> tarballs are available in http://mediacast1.com/~karl.  You will need
> the libshout which is available there as well, I haven't fully tested
> the patch for using libshout trunk yet.
> 
> karl.

I can't get this to compile on my machine - it's saying it can't find the
m4 directory. I've tried copying the m4 dir from the directory above to
the ices dir, which gets it a bit further, but then it's not finding
src/log/Makefile.in




From karl at xiph.org  Mon Dec  6 19:16:19 2004
From: karl at xiph.org (Karl Heyes)
Date: 06 Dec 2004 19:16:19 +0000
Subject: [Icecast] Re: ices, jack
In-Reply-To: <pan.2004.12.06.17.12.54.356527@earthsong.free-online.co.uk>
References: <20041206103031.P74891-100000@xs6.xs4all.nl>
	<1102344179.10887.11.camel@bogus.hackers.club>
	<pan.2004.12.06.17.12.54.356527@earthsong.free-online.co.uk>
Message-ID: <1102360578.10887.41.camel@bogus.hackers.club>

On Mon, 2004-12-06 at 17:12, andy wrote:
> On Mon, 06 Dec 2004 14:42:59 +0000, Karl Heyes wrote:
> 
> > On Mon, 2004-12-06 at 09:31, adam wrote:
> >> alo
> >> 
> >> i have seen some mention of an ices patch with support for jack...anyone
> >> know where i can get this?
> > 
> > The latest is in SVN under http://svn.xiph.org/icecast/branches/kh and
> > tarballs are available in http://mediacast1.com/~karl.  You will need
> > the libshout which is available there as well, I haven't fully tested
> > the patch for using libshout trunk yet.
> > 
> > karl.
> 
> I can't get this to compile on my machine - it's saying it can't find the
> m4 directory. I've tried copying the m4 dir from the directory above to
> the ices dir, which gets it a bit further, but then it's not finding
> src/log/Makefile.in

which one ? libshout/ices svn/tarball

I've just unpacked the ices tarball and run ./configure and it seems ok

karl.




From andy at earthsong.free-online.co.uk  Mon Dec  6 20:48:45 2004
From: andy at earthsong.free-online.co.uk (andy)
Date: Mon, 06 Dec 2004 20:48:45 +0000
Subject: [Icecast] Re: Re: ices, jack
References: <20041206103031.P74891-100000@xs6.xs4all.nl>
	<1102344179.10887.11.camel@bogus.hackers.club>
	<pan.2004.12.06.17.12.54.356527@earthsong.free-online.co.uk>
	<1102360578.10887.41.camel@bogus.hackers.club>
Message-ID: <pan.2004.12.06.20.48.44.44408@earthsong.free-online.co.uk>

On Mon, 06 Dec 2004 19:16:19 +0000, Karl Heyes wrote:

> On Mon, 2004-12-06 at 17:12, andy wrote:
>> On Mon, 06 Dec 2004 14:42:59 +0000, Karl Heyes wrote:
>> 
>> > On Mon, 2004-12-06 at 09:31, adam wrote:
>> >> alo
>> >> 
>> >> i have seen some mention of an ices patch with support for jack...anyone
>> >> know where i can get this?
>> > 
>> > The latest is in SVN under http://svn.xiph.org/icecast/branches/kh and
>> > tarballs are available in http://mediacast1.com/~karl.  You will need
>> > the libshout which is available there as well, I haven't fully tested
>> > the patch for using libshout trunk yet.
>> > 
>> > karl.
>> 
>> I can't get this to compile on my machine - it's saying it can't find the
>> m4 directory. I've tried copying the m4 dir from the directory above to
>> the ices dir, which gets it a bit further, but then it's not finding
>> src/log/Makefile.in
> 
> which one ? libshout/ices svn/tarball
> 
> I've just unpacked the ices tarball and run ./configure and it seems ok
> 
> karl.

it was ices from svn. the tarball is ok.




From danstowell at gmail.com  Tue Dec  7 08:31:29 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Tue, 7 Dec 2004 08:31:29 +0000
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
Message-ID: <286e6b7c0412070031795b742b@mail.gmail.com>

Hi,

I'm setting up icecast2 on a Mac OSX. I can't get it to run because
icecast complains about being unable to start logging - however, I'm
pretty sure the logfiles are accessible. The relevant part of the
config file is:

	<paths>
		<basedir>
			/Users/dan/icecasting
		</basedir>
		<logdir>
			/Users/dan/icecasting/logs
		</logdir>
		<webroot>
			/Users/dan/icecasting/webserving
		</webroot>
	</paths>
	<logging>
		<accesslog>
			icecast2access.log
		</accesslog>
		<errorlog>
			icecast2error.log
		</errorlog>
		<loglevel>
			4
		</loglevel>
	</logging>

Those logfiles are accessible - if I type "ls -l
/Users/dan/icecasting/logs" I get

-rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2access.log
-rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2error.log
-rw-rw-r--  1 dan  admin  1106  6 Dec 23:03 ices.log

Similarly, the "logs" directory is fully writeable. So why is Icecast
finding it impossible to open the files for writing?

I'll be grateful for any hints -
Best,
Dan

-- 
http://www.mcld.co.uk


From robbert at intermatics.nl  Tue Dec  7 12:48:24 2004
From: robbert at intermatics.nl (Robbert van Os)
Date: Tue, 7 Dec 2004 13:48:24 +0100
Subject: [Icecast] streaming stops after 5 seconds or so
Message-ID: <20041207124824.0C97380C026@pop.spill.nl>

Hi there, fellow icecast users. I have just started using icecast and really
like it, but seem to have a small problem for now, let's call it a challange
;)
 
I am using version 2.1.0 and use ices 0.4 to stream my mp3 collection to the
server. They both run on linux (fedora core2) and looks like it is working
ok. But when listening to the stream it stops playing, does anyone perhaps
recognizes this problem?
 
Hope someone can help me out, thx in advance.
 
Kind regards Bannister
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041207/0ff119ea/attachment.htm>

From karl at xiph.org  Tue Dec  7 14:54:00 2004
From: karl at xiph.org (Karl Heyes)
Date: 07 Dec 2004 14:54:00 +0000
Subject: [Icecast] streaming stops after 5 seconds or so
In-Reply-To: <20041207124824.0C97380C026@pop.spill.nl>
References: <20041207124824.0C97380C026@pop.spill.nl>
Message-ID: <1102431239.10887.59.camel@bogus.hackers.club>

On Tue, 2004-12-07 at 12:48, Robbert van Os wrote:
> Hi there, fellow icecast users. I have just started using icecast and
> really like it, but seem to have a small problem for now, let's call
> it a challange ;)
>  
> I am using version 2.1.0 and use ices 0.4 to stream my mp3 collection
> to the server. They both run on linux (fedora core2) and looks like it
> is working ok. But when listening to the stream it stops playing, does
> anyone perhaps recognizes this problem?

It's hard to say why it stopped as we have little information to go on.
The usual reason why a stream stops playing for a listener is because
bitrate from icecast to listener is more than the link can take, causing
the client to lag behind and if that client lags behind too much then
they will be kicked off.

karl.




From oalec at cruzio.com  Tue Dec  7 19:53:12 2004
From: oalec at cruzio.com (Alec VanderWoude)
Date: Tue, 7 Dec 2004 11:53:12 -0800
Subject: [Icecast] Relaying question
Message-ID: <A0719948-4889-11D9-85E1-00306564D772@cruzio.com>


Hello,

I'm fairly new to icecast2, so forgive me if there is an obvious answer 
to this question.
I am using a master server and a relay server. What I would like to to 
do is have the master
server send a live stream encoded as 128 bit mp3 to the relay server, 
and then have the relay
server broadcast that stream as well as a 64 nit mp3 stream. Is this 
possible? Can Ices, Darkice,
or something else take in a live stream from a master server and then 
do the resampling or is
my only option having the master serever do the two different bitrate 
streams and have the relay
server broadcast those two different mount? Any advice would be greatly 
appreciated.

Alec



From karl at xiph.org  Tue Dec  7 20:03:08 2004
From: karl at xiph.org (Karl Heyes)
Date: 07 Dec 2004 20:03:08 +0000
Subject: [Icecast] Relaying question
In-Reply-To: <A0719948-4889-11D9-85E1-00306564D772@cruzio.com>
References: <A0719948-4889-11D9-85E1-00306564D772@cruzio.com>
Message-ID: <1102449788.10887.81.camel@bogus.hackers.club>

On Tue, 2004-12-07 at 19:53, Alec VanderWoude wrote:
> Hello,
> 
> I'm fairly new to icecast2, so forgive me if there is an obvious answer 
> to this question.
> I am using a master server and a relay server. What I would like to to 
> do is have the master
> server send a live stream encoded as 128 bit mp3 to the relay server, 
> and then have the relay
> server broadcast that stream as well as a 64 nit mp3 stream. Is this 
> possible? Can Ices, Darkice,
> or something else take in a live stream from a master server and then 
> do the resampling or is
> my only option having the master serever do the two different bitrate 
> streams and have the relay
> server broadcast those two different mount? Any advice would be greatly 
> appreciated.

you'll have to re-encode at some point, whether that is at the master
end or slave end is up to you.  You should be able to use something like
curl/wget to grab the stream from icecast and feed it into a source
client like ices for reencoding which then sends the stream back to
icecast under a different mountpoint.

karl.




From corsa at gmx.de  Tue Dec  7 21:35:52 2004
From: corsa at gmx.de (Dirk H)
Date: Tue, 7 Dec 2004 22:35:52 +0100
Subject: [Icecast] Refresh Ices 0.4.?
In-Reply-To: <Pine.LNX.4.61.0411261946060.25164@data.home>
Message-ID: <20041207213338.4CE02286DD7@ns3.osuosl.org>

Geoff Shang wrote:


>>> Actually, it should detect changed playlists
>>> automatically.

>It does, but when I tried doing this, it recognised the changed playlist 
>but picked up at the same place it had been in the old one, rather than 
>going from the top.  So, in my case, after it had played item 5 in the old 
>playlist, it began with item 6 of the new one.  Not quite what I'd wanted, 
>but it was good enough at the time.  Oh and this was Ices 0.3 then.

I use Ices 0.4 with randomized playlist. It does not reload the playlist,
when it is changed. It also does not react on SIGHUP.
Is there any way to tell ices to reload on changed playlist?

In near future I'll hope to use python or perl-module instead of the
internal playlist module. Does someone know a good page with examples?

Dirk

Up-radio.net



From danstowell at gmail.com  Tue Dec  7 21:51:47 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Tue, 7 Dec 2004 21:51:47 +0000
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <56755a70412071303259b11c@mail.gmail.com>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<56755a70412071303259b11c@mail.gmail.com>
Message-ID: <286e6b7c04120713517289bcf3@mail.gmail.com>

running it as myself ("dan") - the same as the owner of the logfiles
and of the containing folder.

i did try running it as root at first, but as you probably know, you
get a warning message if you try to do that.

dan


On Tue, 7 Dec 2004 13:03:08 -0800, Daniel <lpmusix at gmail.com> wrote:
> what user are you running icecast as?
> 
> 
> 
> 
> On Tue, 7 Dec 2004 08:31:29 +0000, Dan Stowell <danstowell at gmail.com> wrote:
> > Hi,
> >
> > I'm setting up icecast2 on a Mac OSX. I can't get it to run because
> > icecast complains about being unable to start logging - however, I'm
> > pretty sure the logfiles are accessible. The relevant part of the
> > config file is:
> >
> >         <paths>
> >                 <basedir>
> >                         /Users/dan/icecasting
> >                 </basedir>
> >                 <logdir>
> >                         /Users/dan/icecasting/logs
> >                 </logdir>
> >                 <webroot>
> >                         /Users/dan/icecasting/webserving
> >                 </webroot>
> >         </paths>
> >         <logging>
> >                 <accesslog>
> >                         icecast2access.log
> >                 </accesslog>
> >                 <errorlog>
> >                         icecast2error.log
> >                 </errorlog>
> >                 <loglevel>
> >                         4
> >                 </loglevel>
> >         </logging>
> >
> > Those logfiles are accessible - if I type "ls -l
> > /Users/dan/icecasting/logs" I get
> >
> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2access.log
> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2error.log
> > -rw-rw-r--  1 dan  admin  1106  6 Dec 23:03 ices.log
> >
> > Similarly, the "logs" directory is fully writeable. So why is Icecast
> > finding it impossible to open the files for writing?
> >
> > I'll be grateful for any hints -
> > Best,
> > Dan
> >
> > --
> > http://www.mcld.co.uk
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> >
> 


-- 
http://www.mcld.co.uk


From oracle at provocation.net  Tue Dec  7 22:14:11 2004
From: oracle at provocation.net (Zenon Panoussis)
Date: Tue, 07 Dec 2004 23:14:11 +0100
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <286e6b7c04120713517289bcf3@mail.gmail.com>
References: <286e6b7c0412070031795b742b@mail.gmail.com>	<56755a70412071303259b11c@mail.gmail.com>
	<286e6b7c04120713517289bcf3@mail.gmail.com>
Message-ID: <41B62B33.3000802@provocation.net>


Dan Stowell wrote:

[icecast can't write to log files]

> running it as myself ("dan") - the same as the owner of the logfiles
> and of the containing folder.

>> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2access.log
>> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2error.log
>> > -rw-rw-r--  1 dan  admin  1106  6 Dec 23:03 ices.log

Who owns the directory containing the logs? Is it "executable" (i.e.
traversible)? By whom?

Z


From danstowell at gmail.com  Tue Dec  7 22:59:58 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Tue, 7 Dec 2004 22:59:58 +0000
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <20041207223655.GA14837@netspace.org>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<56755a70412071303259b11c@mail.gmail.com>
	<286e6b7c04120713517289bcf3@mail.gmail.com>
	<20041207223655.GA14837@netspace.org>
Message-ID: <286e6b7c041207145934aa0044@mail.gmail.com>

On Tue, 7 Dec 2004 17:36:55 -0500, Paul Melnikow <pnm at zephyr.to> wrote:
> On Tue, Dec 07, 2004 at 09:51:47PM +0000, Dan Stowell wrote:
> > running it as myself ("dan") - the same as the owner of the logfiles
> > and of the containing folder.
> >
> > i did try running it as root at first, but as you probably know, you
> > get a warning message if you try to do that.
> 
> have you enabled chroot? if that were the case, logdir would have to be
> relative to basedir rather than the "real" /.

No - here's the relevant section of my config file just to make sure:

	<security>
		<chroot>
			0
		</chroot>
	</security>

Dan


From danstowell at gmail.com  Tue Dec  7 23:02:38 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Tue, 7 Dec 2004 23:02:38 +0000
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <41B62B33.3000802@provocation.net>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<56755a70412071303259b11c@mail.gmail.com>
	<286e6b7c04120713517289bcf3@mail.gmail.com>
	<41B62B33.3000802@provocation.net>
Message-ID: <286e6b7c04120715024bb13cf2@mail.gmail.com>

Zenon Panoussis wrote:
> 
> Dan Stowell wrote:
> 
> [icecast can't write to log files]
> 
> > running it as myself ("dan") - the same as the owner of the logfiles
> > and of the containing folder.
> 
> >> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2access.log
> >> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2error.log
> >> > -rw-rw-r--  1 dan  admin  1106  6 Dec 23:03 ices.log
> 
> Who owns the directory containing the logs? Is it "executable" (i.e.
> traversible)? By whom?

I own it, and everyone can traverse it! i.e.:

drwxrwxrwx  5 dan  admin   170  6 Dec 23:48 logs

Dan


From pnm at zephyr.to  Tue Dec  7 23:10:26 2004
From: pnm at zephyr.to (Paul Melnikow)
Date: Tue, 7 Dec 2004 18:10:26 -0500
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <286e6b7c04120715024bb13cf2@mail.gmail.com>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<56755a70412071303259b11c@mail.gmail.com>
	<286e6b7c04120713517289bcf3@mail.gmail.com>
	<41B62B33.3000802@provocation.net>
	<286e6b7c04120715024bb13cf2@mail.gmail.com>
Message-ID: <20041207231026.GA26809@netspace.org>

On Tue, Dec 07, 2004 at 11:02:38PM +0000, Dan Stowell wrote:
> Zenon Panoussis wrote:
> > 
> > Dan Stowell wrote:
> > 
> > [icecast can't write to log files]
> > 
> > > running it as myself ("dan") - the same as the owner of the logfiles
> > > and of the containing folder.
> > 
> > >> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2access.log
> > >> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2error.log
> > >> > -rw-rw-r--  1 dan  admin  1106  6 Dec 23:03 ices.log
> > 
> > Who owns the directory containing the logs? Is it "executable" (i.e.
> > traversible)? By whom?
> 
> I own it, and everyone can traverse it! i.e.:
> 
> drwxrwxrwx  5 dan  admin   170  6 Dec 23:48 logs

and the parent "icecasting" directory has the same permissions?

can you include the output from the command showing the exact error
message?

p.

-- 
every day is a good day


From danstowell at gmail.com  Tue Dec  7 23:33:54 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Tue, 7 Dec 2004 23:33:54 +0000
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <20041207231026.GA26809@netspace.org>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<56755a70412071303259b11c@mail.gmail.com>
	<286e6b7c04120713517289bcf3@mail.gmail.com>
	<41B62B33.3000802@provocation.net>
	<286e6b7c04120715024bb13cf2@mail.gmail.com>
	<20041207231026.GA26809@netspace.org>
Message-ID: <286e6b7c0412071533128abe9d@mail.gmail.com>

Paul Melnikow <pnm at zephyr.to> wrote:
> On Tue, Dec 07, 2004 at 11:02:38PM +0000, Dan Stowell wrote:
> > Zenon Panoussis wrote:
> > > Dan Stowell wrote:
> > >
> > > [icecast can't write to log files]
> > >
> > > > running it as myself ("dan") - the same as the owner of the logfiles
> > > > and of the containing folder.
> > >
> > > >> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2access.log
> > > >> > -rw-rw-r--  1 dan  admin     0  6 Dec 23:48 icecast2error.log
> > > >> > -rw-rw-r--  1 dan  admin  1106  6 Dec 23:03 ices.log
> > >
> > > Who owns the directory containing the logs? Is it "executable" (i.e.
> > > traversible)? By whom?
> >
> > I own it, and everyone can traverse it! i.e.:
> >
> > drwxrwxrwx  5 dan  admin   170  6 Dec 23:48 logs
> 
> and the parent "icecasting" directory has the same permissions?

Yes, that's right.

> can you include the output from the command showing the exact error
> message?

Here it is:

dan% icecast -c /Users/dan/icecasting/icecast2conf.xml
FATAL: could not open error logging
FATAL: could not open access logging
FATAL: Could not start logging
dan% 

This is icecast 2.0.1 by the way, installed via darwinports.

Thanks
Dan


From msmith at xiph.org  Wed Dec  8 00:15:17 2004
From: msmith at xiph.org (Michael Smith)
Date: Wed, 8 Dec 2004 11:15:17 +1100
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <286e6b7c0412071533128abe9d@mail.gmail.com>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<20041207231026.GA26809@netspace.org>
	<286e6b7c0412071533128abe9d@mail.gmail.com>
Message-ID: <200412081115.17124.msmith@xiph.org>

On Wednesday 08 December 2004 10:33, Dan Stowell wrote:
> Here it is:
>
> dan% icecast -c /Users/dan/icecasting/icecast2conf.xml
> FATAL: could not open error logging
> FATAL: could not open access logging
> FATAL: Could not start logging
> dan%
>
> This is icecast 2.0.1 by the way, installed via darwinports.

2.1 has a clearer error message here, which adds useful information like _why_ 
it failed to open the log file(s). So I'd recommend upgrading.

You can send me your entire config file (with the passwords blanked out :-) 
off-list if you want me to take a closer look.

Mike



From danstowell at gmail.com  Wed Dec  8 08:43:27 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Wed, 8 Dec 2004 08:43:27 +0000
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <20041207234410.GA8815@netspace.org>
References: <286e6b7c0412070031795b742b@mail.gmail.com>
	<56755a70412071303259b11c@mail.gmail.com>
	<286e6b7c04120713517289bcf3@mail.gmail.com>
	<41B62B33.3000802@provocation.net>
	<286e6b7c04120715024bb13cf2@mail.gmail.com>
	<20041207231026.GA26809@netspace.org>
	<286e6b7c0412071533128abe9d@mail.gmail.com>
	<20041207234410.GA8815@netspace.org>
Message-ID: <286e6b7c0412080043742687ee@mail.gmail.com>

On Tue, 7 Dec 2004 18:44:10 -0500, Paul Melnikow <pnm at zephyr.to> wrote:
> On Tue, Dec 07, 2004 at 11:33:54PM +0000, Dan Stowell wrote:
> 
> 
> > Paul Melnikow <pnm at zephyr.to> wrote:
> > > On Tue, Dec 07, 2004 at 11:02:38PM +0000, Dan Stowell wrote:
> > > > Zenon Panoussis wrote:
> > > > > Dan Stowell wrote:
> > > > >
> > > > > [icecast can't write to log files]
> a quick test here suggests that the problem is with the whitespace.
> 
> this works ok for me:
> 
>     <accesslog>icecast2access.log</accesslog>
> 
> but this doesn't do what i'd expect -- i end up with question marks in
> the filename:
> 
>     <accesslog>
>         icecast2access.log
>     </accesslog>

Aha! That does it.
(I'm right in thinking that kind of whitespace isn't supposed to
matter in XML, aren't I?)

Thanks all for your advice. Icecast now running, and I'll upgrade to
2.1 as soon as I'm comfortable with my understanding of it :)

Thanks!
Dan


From oracle at provocation.net  Wed Dec  8 12:02:40 2004
From: oracle at provocation.net (Zenon Panoussis)
Date: Wed, 08 Dec 2004 13:02:40 +0100
Subject: [Icecast] icecast2 setup problem - unable to open logfiles
In-Reply-To: <286e6b7c0412071533128abe9d@mail.gmail.com>
References: <286e6b7c0412070031795b742b@mail.gmail.com>	<56755a70412071303259b11c@mail.gmail.com>	<286e6b7c04120713517289bcf3@mail.gmail.com>	<41B62B33.3000802@provocation.net>	<286e6b7c04120715024bb13cf2@mail.gmail.com>	<20041207231026.GA26809@netspace.org>
	<286e6b7c0412071533128abe9d@mail.gmail.com>
Message-ID: <41B6ED60.1020109@provocation.net>


Dan Stowell wrote:

>> > > Who owns the directory containing the logs? Is it "executable" (i.e.
>> > > traversible)? By whom?

>> > I own it, and everyone can traverse it! i.e.:

Is the path /Users/dan absolute? Did you chroot icecast?

Try 'strace -v -f -s 128 -o garbage icecast' for a few seconds.
Then ^C and 'grep -i 'permission denied' garbage'. If icecast is
trying to put the logs somewhere else, you'll see it there.

Z


From danstowell at gmail.com  Wed Dec  8 22:24:18 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Wed, 8 Dec 2004 22:24:18 +0000
Subject: [Icecast] Serving a playlist.pls / listen.m3u file
Message-ID: <286e6b7c041208142415a43f33@mail.gmail.com>

Hi - I've heard that Icecast provides a fake "playlist file" along the lines of

http://blahblah:8000/listen.m3u
 or
http://blahblah:8000/playlist.pls

because Quicktime can't seem to handle the stream without a playlist
file to wrap it up. (There may be other reasons.) However, I can't
seem to find any documentation about this, and guessing various URLs
on my icecast2.0.1 port comes up with nothing.

Is there such a thing? I can't get my "raw" http://blahblah:8000
stream to open in Quicktime... Perhaps there's a config setting that's
relevant here?

Thanks
Dan

-- 
http://www.mcld.co.uk


From danstowell at gmail.com  Thu Dec  9 00:45:01 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Thu, 9 Dec 2004 00:45:01 +0000
Subject: [Icecast] Re: Serving a playlist.pls / listen.m3u file
In-Reply-To: <286e6b7c041208142415a43f33@mail.gmail.com>
References: <286e6b7c041208142415a43f33@mail.gmail.com>
Message-ID: <286e6b7c0412081645407f97f3@mail.gmail.com>

I think I've answered my own question - I've got a mountpoint at
/flatfour.mp3 and it looks like /flatfour.mp3.m3u automatically serves
up a playlist file.

However, Quicktime player still refuses to handle it properly. I had
to craft my own .pls file for Quicktime to understand, which seems a
shame!

Thanks anyway,
Dan



On Wed, 8 Dec 2004 22:24:18 +0000, Dan Stowell <danstowell at gmail.com> wrote:
> Hi - I've heard that Icecast provides a fake "playlist file" along the lines of
> 
> http://blahblah:8000/listen.m3u
>  or
> http://blahblah:8000/playlist.pls
> 
> because Quicktime can't seem to handle the stream without a playlist
> file to wrap it up. (There may be other reasons.) However, I can't
> seem to find any documentation about this, and guessing various URLs
> on my icecast2.0.1 port comes up with nothing.
> 
> Is there such a thing? I can't get my "raw" http://blahblah:8000
> stream to open in Quicktime... Perhaps there's a config setting that's
> relevant here?
> 
> Thanks
> Dan


From Jason at Weatherserver.net  Thu Dec  9 00:47:58 2004
From: Jason at Weatherserver.net (Jason)
Date: Wed, 8 Dec 2004 19:47:58 -0500
Subject: [Icecast] Re: Serving a playlist.pls / listen.m3u file
References: <286e6b7c041208142415a43f33@mail.gmail.com>
	<286e6b7c0412081645407f97f3@mail.gmail.com>
Message-ID: <000801c4dd88$ba5cc830$1401a8c0@workstation>

Normally you don't put an extention in a mountpoint  it would be /flatfour 
and  /flatfour.m3u
rather then /flatfour.mp3 and /flatfour.mp3.m3u




----- Original Message ----- 
From: "Dan Stowell" <danstowell at gmail.com>
To: <>
Sent: Wednesday, December 08, 2004 7:45 PM
Subject: [Icecast] Re: Serving a playlist.pls / listen.m3u file


>I think I've answered my own question - I've got a mountpoint at
> /flatfour.mp3 and it looks like /flatfour.mp3.m3u automatically serves
> up a playlist file.
>
> However, Quicktime player still refuses to handle it properly. I had
> to craft my own .pls file for Quicktime to understand, which seems a
> shame!
>
> Thanks anyway,
> Dan
>
>
>
> On Wed, 8 Dec 2004 22:24:18 +0000, Dan Stowell <danstowell at gmail.com> 
> wrote:
>> Hi - I've heard that Icecast provides a fake "playlist file" along the 
>> lines of
>>
>> http://blahblah:8000/listen.m3u
>>  or
>> http://blahblah:8000/playlist.pls
>>
>> because Quicktime can't seem to handle the stream without a playlist
>> file to wrap it up. (There may be other reasons.) However, I can't
>> seem to find any documentation about this, and guessing various URLs
>> on my icecast2.0.1 port comes up with nothing.
>>
>> Is there such a thing? I can't get my "raw" http://blahblah:8000
>> stream to open in Quicktime... Perhaps there's a config setting that's
>> relevant here?
>>
>> Thanks
>> Dan
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 





From kent at kent.troymonster.com  Thu Dec  9 01:08:05 2004
From: kent at kent.troymonster.com (Kent)
Date: Wed, 8 Dec 2004 17:08:05 -0800 (PST)
Subject: [Icecast] newbie question
Message-ID: <Pine.LNX.4.58.0412081705320.16783@kent.troymonster.com>


Hello!

I am not new to Icecast, but I am new to this list.  And, for whatever 
reason, I just today discovered the admin stuff.  I think I had played 
with it before and had forgotten about it.

Is there a feature that might cause the IP addr to be resolved on the 
"list clients" page?  That would be neat.

Cheers!
Kent



From danstowell at gmail.com  Thu Dec  9 14:10:32 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Thu, 9 Dec 2004 14:10:32 +0000
Subject: [Icecast] ices0 - restarting the playlist
Message-ID: <286e6b7c04120906106f3f5493@mail.gmail.com>

We've got a 12-hour playlist running in ices0, which we'd like to
start exactly on the hour. If I'm using ices0 in the very basic
playlist mode, is there any way to trigger it to jump back to the
start of the playlist?

Could/should I use a HUP perhaps? Not sure if that would cause a
stream interruption for listeners.

Or would I need to use the python or perl playlist mode?

Thanks
Dan

-- 
http://www.flatfourradio.co.uk


From karl at xiph.org  Thu Dec  9 19:30:02 2004
From: karl at xiph.org (Karl Heyes)
Date: 09 Dec 2004 19:30:02 +0000
Subject: [Icecast] On demand relay in icecast 2?
In-Reply-To: <06df01c4db2d$b3439ae0$0101a8c0@foo>
References: <06df01c4db2d$b3439ae0$0101a8c0@foo>
Message-ID: <1102620601.10887.133.camel@bogus.hackers.club>

On Mon, 2004-12-06 at 00:50, ZoTyA wrote:

> I wanna ask when will be the on-demand relaying in the "stable" release?

That is hard to say. I haven't heard of any reports wrt the on-demand 
for some time in the kh branch. This could be down to the feature not
being used much or maybe it is being used but no one is actually having
a problem with it.

For merging into trunk it's all a question of what things people want,
what has priority and when we should do a release.

karl.




From mark at indymedia.org  Thu Dec  9 19:41:56 2004
From: mark at indymedia.org (mark burdett)
Date: Thu, 9 Dec 2004 11:41:56 -0800
Subject: [Icecast] On demand relay in icecast 2?
In-Reply-To: <1102620601.10887.133.camel@bogus.hackers.club>;
	from karl@xiph.org on Thu, Dec 09, 2004 at 07:30:02PM +0000
References: <06df01c4db2d$b3439ae0$0101a8c0@foo>
	<1102620601.10887.133.camel@bogus.hackers.club>
Message-ID: <20041209114156.C10863@indymedia.org>

I haven't noticed any problems with on-demand relays, if i did i would let you know.

--mark

On Thu, 09 Dec 2004 19:30:02 +0000, Karl Heyes wrote:
> On Mon, 2004-12-06 at 00:50, ZoTyA wrote:
> 
> > I wanna ask when will be the on-demand relaying in the "stable" release?
> 
> That is hard to say. I haven't heard of any reports wrt the on-demand 
> for some time in the kh branch. This could be down to the feature not
> being used much or maybe it is being used but no one is actually having
> a problem with it.
> 
> For merging into trunk it's all a question of what things people want,
> what has priority and when we should do a release.
> 
> karl.
> 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From jdotero at ucsd.edu  Fri Dec 10 00:47:44 2004
From: jdotero at ucsd.edu (Jose Otero)
Date: Thu, 09 Dec 2004 16:47:44 -0800
Subject: [Icecast] icecast2 relaying question
Message-ID: <41B8F230.1090902@ucsd.edu>

I understand there are two types of relays in icecast2.  The master 
relay which relays everything from a source and  a point relay which 
relays a specific mount point from a source.

I have a server which has 3 streams.  I want to relay 2 of them.  How 
can I do this?

Can I define two relays and two mountpoints within the xml config file?

Do i do this in the same relay tag:
<relay>
somehow define both here?
</relay>

or

<relay1>
.
.
.
</relay1>

and

<relay2>
.
.
.
</relay2>

Anyhelp you can give me would be much appreciated.  If you have an 
example, that may work the best.

Thanks for your time.

Jose
www.scansandiego.net


P.S.  Not sure if the replys will automatically go to my email address.  
My web access is flakey right now, so please be sure to reply to my 
email address and this group.  (email:  jdotero(at)ucsd.edu)


From adam at xs4all.nl  Fri Dec 10 05:35:20 2004
From: adam at xs4all.nl (adam)
Date: Fri, 10 Dec 2004 06:35:20 +0100 (CET)
Subject: [Icecast] oss, jack and ices
Message-ID: <20041210063247.Y90541-100000@xs6.xs4all.nl>


hi

i have a remote machine i am running ices (kh branch) on...if i start ices
with the default ices-jack.xml config i get the following:
"Failed to read config file"

I have tried commenting out the line that refers to alsa:
  <!--<param
name="connect">alsa_pcm:capture_1,alsa_pcm:capture_2</param>-->

but no luck...any hints on what i should be doing?

adam




Adam Hyde
~/.nz

r a d i o q u a l i a
http://www.radioqualia.net
Free as in 'media'

contact:
email : adam at xs4all.nl
phone : +64 21 1746 741 (new zealand mobile)




From admin at artem-catv.ru  Fri Dec 10 08:50:30 2004
From: admin at artem-catv.ru (Administrator)
Date: Fri, 10 Dec 2004 18:50:30 +1000
Subject: [Icecast] ices 0.4, pure quality and more...
Message-ID: <1716613825.20041210185030@artem-catv.ru>

Hello everyone,

Few weeks ago I tuned icecast with 7 streams from ices. It plays
static playlists, sorted by genre.
I have 2 problems. First problem: pure quality when reencoding is
turned on. Temporary solution was found. I added one string, to
reencoding code, that points to liblame use better quality. But is
this the one and right solution?
Second problem: Ices (or liblame?) does not properly closes played
mp3's... Few days and the limit of kern.maxfiles is exhausted.
How to fix this problem?

PS: System is FreeBSD 5.3

-- 
Yours,
 Victor                          mailto:admin at artem-catv.ru




From danstowell at gmail.com  Fri Dec 10 10:02:05 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Fri, 10 Dec 2004 10:02:05 +0000
Subject: [Icecast] oss, jack and ices
In-Reply-To: <20041210063247.Y90541-100000@xs6.xs4all.nl>
References: <20041210063247.Y90541-100000@xs6.xs4all.nl>
Message-ID: <286e6b7c041210020222d8802@mail.gmail.com>

Adam,

If it says "failed to read config file" then it's failed to load the
XML file at all, so commenting out one line or the other isn't going
to make any difference. Make sure you're specifying the right path to
the XML file, and that the file and the directory are readable (by the
user that ices runs under)...

Dan


On Fri, 10 Dec 2004 06:35:20 +0100 (CET), adam <adam at xs4all.nl> wrote:
> 
> hi
> 
> i have a remote machine i am running ices (kh branch) on...if i start ices
> with the default ices-jack.xml config i get the following:
> "Failed to read config file"
> 
> I have tried commenting out the line that refers to alsa:
>   <!--<param
> name="connect">alsa_pcm:capture_1,alsa_pcm:capture_2</param>-->
> 
> but no luck...any hints on what i should be doing?
> 
> adam
> 
> Adam Hyde
> ~/.nz
> 
> r a d i o q u a l i a
> http://www.radioqualia.net
> Free as in 'media'
> 
> contact:
> email : adam at xs4all.nl
> phone : +64 21 1746 741 (new zealand mobile)
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


-- 
http://www.mcld.co.uk


From adam at xs4all.nl  Fri Dec 10 12:47:54 2004
From: adam at xs4all.nl (adam)
Date: Fri, 10 Dec 2004 13:47:54 +0100 (CET)
Subject: [Icecast] oss, jack and ices
In-Reply-To: <286e6b7c041210020222d8802@mail.gmail.com>
Message-ID: <20041210134742.U43970-100000@xs6.xs4all.nl>

yip...had done all that


hmmm


adam


On Fri, 10 Dec 2004, Dan Stowell wrote:

> Adam,
>
> If it says "failed to read config file" then it's failed to load the
> XML file at all, so commenting out one line or the other isn't going
> to make any difference. Make sure you're specifying the right path to
> the XML file, and that the file and the directory are readable (by the
> user that ices runs under)...
>
> Dan
>
>
> On Fri, 10 Dec 2004 06:35:20 +0100 (CET), adam <adam at xs4all.nl> wrote:
> >
> > hi
> >
> > i have a remote machine i am running ices (kh branch) on...if i start ices
> > with the default ices-jack.xml config i get the following:
> > "Failed to read config file"
> >
> > I have tried commenting out the line that refers to alsa:
> >   <!--<param
> > name="connect">alsa_pcm:capture_1,alsa_pcm:capture_2</param>-->
> >
> > but no luck...any hints on what i should be doing?
> >
> > adam
> >
> > Adam Hyde
> > ~/.nz
> >
> > r a d i o q u a l i a
> > http://www.radioqualia.net
> > Free as in 'media'
> >
> > contact:
> > email : adam at xs4all.nl
> > phone : +64 21 1746 741 (new zealand mobile)
> >
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> >
>
>
> --
> http://www.mcld.co.uk
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>




Adam Hyde
~/.nz

r a d i o q u a l i a
http://www.radioqualia.net
Free as in 'media'

contact:
email : adam at xs4all.nl
phone : +64 21 1746 741 (new zealand mobile)




From karl at xiph.org  Fri Dec 10 16:21:09 2004
From: karl at xiph.org (Karl Heyes)
Date: 10 Dec 2004 16:21:09 +0000
Subject: [Icecast] icecast2 relaying question
In-Reply-To: <41B8F230.1090902@ucsd.edu>
References: <41B8F230.1090902@ucsd.edu>
Message-ID: <1102695669.10887.155.camel@bogus.hackers.club>

On Fri, 2004-12-10 at 00:47, Jose Otero wrote:
> I understand there are two types of relays in icecast2.  The master 
> relay which relays everything from a source and  a point relay which 
> relays a specific mount point from a source.

icecast can be configured as a slave so that it can relay all the
streams on a master server.

> I have a server which has 3 streams.  I want to relay 2 of them.  How 
> can I do this?
> 
> Can I define two relays and two mountpoints within the xml config file?

yes, strictly speaking there is no limit on the number of relays, but
you do have a limit on the number of active sources.

> <relay1>
> .
> .
> .
> </relay1>
> 
> and
> 
> <relay2>
> .
> .
> .
> </relay2>
> 
> Anyhelp you can give me would be much appreciated.  If you have an 
> example, that may work the best.

just state the the 2 <relay> definitions separately, similar to what you
have above.

karl.




From karl at xiph.org  Fri Dec 10 16:25:13 2004
From: karl at xiph.org (Karl Heyes)
Date: 10 Dec 2004 16:25:13 +0000
Subject: [Icecast] oss, jack and ices
In-Reply-To: <20041210063247.Y90541-100000@xs6.xs4all.nl>
References: <20041210063247.Y90541-100000@xs6.xs4all.nl>
Message-ID: <1102695913.10887.160.camel@bogus.hackers.club>

On Fri, 2004-12-10 at 05:35, adam wrote:
> hi
> 
> i have a remote machine i am running ices (kh branch) on...if i start ices
> with the default ices-jack.xml config i get the following:
> "Failed to read config file"
> 
> I have tried commenting out the line that refers to alsa:
>   <!--<param
> name="connect">alsa_pcm:capture_1,alsa_pcm:capture_2</param>-->
> 
> but no luck...any hints on what i should be doing?

failure to read the xml has typically been down to a <tag> </tag>
mismatch error in the xml config file.  The use of 'xmllint ices.xml'
may indicate a possible cause.

karl.




From tubbs at wispdirect.com  Fri Dec 10 16:32:31 2004
From: tubbs at wispdirect.com (Cody Tubbs (wISPdirect))
Date: Fri, 10 Dec 2004 10:32:31 -0600
Subject: [Icecast] Another relay question...
Message-ID: <41B97B3F.30258.1C7FF1@localhost>

I currently have 3 mountpoints, 128, 56 and 24.  I'm using darkice as 
the source and I'm relaying to another server running icecast2.  I'm 
assuming that darkice is using lame for transcoding the bit-rates on 
the fly and sending 128k/s + 56k/s + 24k/s to the relay host... which 
is using a lot of bandwidth on the source network (which I don't have 
much to spare).  Is there any way to just send one 128k/s 
mountpoint and have the relay side transcode to the bitrates and go 
from there, that way I'm saving 80k/s of upload from the source 
host.
The stream randomly starts to glitch out every once and awhile and 
I'm trying to fix it.  Any pointers would be greatly appreciated.

-- Cody Tubbs    : (Certified Master Linux Administrator)
		 : (Certified Unix Security Specialist)
-- wISPdirect      : http://www.wISPdirect.com
-- Broadway Internet



From karl at xiph.org  Fri Dec 10 16:46:12 2004
From: karl at xiph.org (Karl Heyes)
Date: 10 Dec 2004 16:46:12 +0000
Subject: [Icecast] Another relay question...
In-Reply-To: <41B97B3F.30258.1C7FF1@localhost>
References: <41B97B3F.30258.1C7FF1@localhost>
Message-ID: <1102697171.10887.165.camel@bogus.hackers.club>

On Fri, 2004-12-10 at 16:32, Cody Tubbs (wISPdirect) wrote:
> I currently have 3 mountpoints, 128, 56 and 24.  I'm using darkice as 
> the source and I'm relaying to another server running icecast2.  I'm 
> assuming that darkice is using lame for transcoding the bit-rates on 
> the fly and sending 128k/s + 56k/s + 24k/s to the relay host... which 
> is using a lot of bandwidth on the source network (which I don't have 
> much to spare).  Is there any way to just send one 128k/s 
> mountpoint and have the relay side transcode to the bitrates and go 
> from there, that way I'm saving 80k/s of upload from the source 
> host.
> The stream randomly starts to glitch out every once and awhile and 
> I'm trying to fix it.  Any pointers would be greatly appreciated.

sure, sending the 128k stream works as normal and just have 2 local
transcoders to take the 128k stream from the relay, reencode and push
back to the relay under a different mountpoint.  The likes of
streamtranscoder can do that, but I believe you can use a "curl | ices"
type solution as well.  Not sure about darkice but it may do.

karl




From tubbs at wispdirect.com  Fri Dec 10 16:53:52 2004
From: tubbs at wispdirect.com (Cody Tubbs (wISPdirect))
Date: Fri, 10 Dec 2004 10:53:52 -0600
Subject: [Icecast] Another relay question...
In-Reply-To: <1102697171.10887.165.camel@bogus.hackers.club>
References: <41B97B3F.30258.1C7FF1@localhost>
Message-ID: <41B98040.12318.300B1F@localhost>

Ah so basically you mean catch the 128k stream locally on the relay 
server, and re-source it to localhost while transcoding to the other 
two bitrates?  Basically the 56k and 24k mounts will be delayed 
more than the 128 though I'm assuming (which isnt really a 
problem).

I don't know if the above is what you meant though, but I think it will 
work, I havn't checked out streamtranscoder yet.  Thanks.

-- Cody Tubbs    : (Certified Master Linux Administrator)
		 : (Certified Unix Security Specialist)
-- wISPdirect      : http://www.wISPdirect.com
-- Broadway Internet

On 10 Dec 2004 at 16:46, Karl Heyes wrote:

> On Fri, 2004-12-10 at 16:32, Cody Tubbs (wISPdirect) wrote:
> > I currently have 3 mountpoints, 128, 56 and 24.  I'm using darkice as 
> > the source and I'm relaying to another server running icecast2.  I'm 
> > assuming that darkice is using lame for transcoding the bit-rates on 
> > the fly and sending 128k/s + 56k/s + 24k/s to the relay host... which 
> > is using a lot of bandwidth on the source network (which I don't have 
> > much to spare).  Is there any way to just send one 128k/s 
> > mountpoint and have the relay side transcode to the bitrates and go 
> > from there, that way I'm saving 80k/s of upload from the source 
> > host.
> > The stream randomly starts to glitch out every once and awhile and 
> > I'm trying to fix it.  Any pointers would be greatly appreciated.
> 
> sure, sending the 128k stream works as normal and just have 2 local
> transcoders to take the 128k stream from the relay, reencode and push
> back to the relay under a different mountpoint.  The likes of
> streamtranscoder can do that, but I believe you can use a "curl | ices"
> type solution as well.  Not sure about darkice but it may do.
> 
> karl
> 
> 
> 






From j at v2v.cc  Fri Dec 10 20:56:27 2004
From: j at v2v.cc (j at v2v.cc)
Date: Fri, 10 Dec 2004 21:56:27 +0100
Subject: [Icecast] oss, jack and ices
In-Reply-To: <20041210063247.Y90541-100000@xs6.xs4all.nl>
References: <20041210063247.Y90541-100000@xs6.xs4all.nl>
Message-ID: <1102712187.5078.147.camel@localhost>

hi adam,

On Fri, 2004-12-10 at 06:35 +0100, adam wrote:
> I have tried commenting out the line that refers to alsa:
>   <!--<param
> name="connect">alsa_pcm:capture_1,alsa_pcm:capture_2</param>-->
that has to stay in if you want it to connect to the alsa capture ports
on startup, i usually take it out and use jack.plumbing to make the
connections.

the file in svn works here. 
so if you do not change it it should work,


j



From brendan at xiph.org  Sat Dec 11 00:36:05 2004
From: brendan at xiph.org (Brendan Cully)
Date: Fri, 10 Dec 2004 16:36:05 -0800
Subject: [Icecast] ices 0.4, pure quality and more...
In-Reply-To: <1716613825.20041210185030@artem-catv.ru>
References: <1716613825.20041210185030@artem-catv.ru>
Message-ID: <20041211003605.GA4980@watanabe.local>

On Friday, 10 December 2004 at 18:50, Administrator wrote:
> Hello everyone,
> 
> Few weeks ago I tuned icecast with 7 streams from ices. It plays
> static playlists, sorted by genre.
> I have 2 problems. First problem: pure quality when reencoding is
> turned on. Temporary solution was found. I added one string, to
> reencoding code, that points to liblame use better quality. But is
> this the one and right solution?

probably. What change did you make?

> Second problem: Ices (or liblame?) does not properly closes played
> mp3's... Few days and the limit of kern.maxfiles is exhausted.
> How to fix this problem?

I can't reproduce this. In fact, I run ices continuously and lsof
confirms the only MP3 file with a file descriptor is that of the
currently playing track.


From brendan at xiph.org  Sat Dec 11 00:38:10 2004
From: brendan at xiph.org (Brendan Cully)
Date: Fri, 10 Dec 2004 16:38:10 -0800
Subject: [Icecast] ices0 - restarting the playlist
In-Reply-To: <286e6b7c04120906106f3f5493@mail.gmail.com>
References: <286e6b7c04120906106f3f5493@mail.gmail.com>
Message-ID: <20041211003809.GB4980@watanabe.local>

On Thursday, 09 December 2004 at 14:10, Dan Stowell wrote:
> We've got a 12-hour playlist running in ices0, which we'd like to
> start exactly on the hour. If I'm using ices0 in the very basic
> playlist mode, is there any way to trigger it to jump back to the
> start of the playlist?

There's no way to jump to the start, I'm afraid.

> Could/should I use a HUP perhaps? Not sure if that would cause a
> stream interruption for listeners.

It wouldn't do anything at all.

> Or would I need to use the python or perl playlist mode?

This is the way to go. A module that does only this should be very
easy to write.


From tubbs at wISPdirect.com  Sat Dec 11 12:07:35 2004
From: tubbs at wISPdirect.com (Cody Tubbs (wISPdirect))
Date: Sat, 11 Dec 2004 06:07:35 -0600
Subject: [Icecast] relay question again...
Message-ID: <1102766855.8686.9.camel@sine>

http://www.icecast.org/docs/icecast-2.0.1/icecast2_relay.html

As stated in the above link you can do a single relay, yet
is there a way to change the bitrate on the fly while doing so?

I simply want to stream one 128kbps mountpoint on my slower
server, then have my faster server pick it up, and
relay it in 3 different bitrates/mountpoints... what is the
best way to do this (or ANY way? heh), I can't seem to find the
right tool(s).

Thanks,
CT.



From scoop at hokeynet.net  Sun Dec 12 05:58:16 2004
From: scoop at hokeynet.net (Steven Passmore)
Date: Sat, 11 Dec 2004 21:58:16 -0800
Subject: [Icecast] On demand relay in icecast 2?
Message-ID: <00c801c4e00f$93532ed0$6905a8c0@hokeynet.net>

> I haven't noticed any problems with on-demand relays, if i did i would let 
> you know.
>
> --mark

Does that mean it's available?  I added <on-demand>1</on-demand> to one of 
my relays on a 2.1.0 server but it didn't work.  I have a server I'm 
planning to set up if this functionality becomes active.

Steve P. 



From karl at xiph.org  Sun Dec 12 14:13:43 2004
From: karl at xiph.org (Karl Heyes)
Date: 12 Dec 2004 14:13:43 +0000
Subject: [Icecast] On demand relay in icecast 2?
In-Reply-To: <00c801c4e00f$93532ed0$6905a8c0@hokeynet.net>
References: <00c801c4e00f$93532ed0$6905a8c0@hokeynet.net>
Message-ID: <1102860823.10887.2733.camel@bogus.hackers.club>

On Sun, 2004-12-12 at 05:58, Steven Passmore wrote:
> > I haven't noticed any problems with on-demand relays, if i did i would let 
> > you know.
> >
> > --mark
> 
> Does that mean it's available?  I added <on-demand>1</on-demand> to one of 
> my relays on a 2.1.0 server but it didn't work.  I have a server I'm 
> planning to set up if this functionality becomes active.

on-demand relays are not a feature of 2.1, the feature is only on the
2.1-kh branch at the moment, it is there until I've flushed out the main
issues (which at the moment looks to be done) then it can be merged into
trunk.

If you want to try it out, the source is on 

tar  http://mediacast1.com/~karl
svn  http://svn.xiph.org/icecast/branches/kh/icecast



karl.




From iceuse at wwlang.net  Sun Dec 12 21:57:25 2004
From: iceuse at wwlang.net (Iceuse - Kris)
Date: Sun, 12 Dec 2004 22:57:25 +0100
Subject: [Icecast] Metadata and bad player behaviour : cut sound for short
 time when receiving metadata (kh versions of ices/icecast)
Message-ID: <41BCBEC5.3070300@wwlang.net>

Hello,

I was trying to add metadata to my OGG stream (ices 2,0-kh59, icecast 
2.0-kh51).
It works... but the players are doing a small sound cut at metadata 
reception :
- VLC (maybe 1/3sec cut)
- JORBIS (java. maybe 1/10sec, because I can have set higher priority to 
sound processing and not to comment handling)
(player plateform: Mac OS X 1.3.6)

With VLC... I can say comments are unusable, it's too bad... Maybe if 
the comment change occurs between songs it not so noticeable, but that's 
not very good...
I didn't tried other players.

Did you experienced such problems? I didn't tried icecast 2.1-kh4 yet 
because the version I have is working fine.
Before changing to latest icecast, I would like to know if there is a 
similar trouble with it (I don't say it's an icecast issue, but maybe 
with newer ogg headers are handled correctly by players. Anyway, VLC is 
buggy regarding comments).

BTW, metadata are nicely streamed. I can feed ices with any metadata 
(anything=everything), the player receives it, even for streams 
transcoded by ices from the main stream.

Thanks for you comments,
Regards,
Chris



From bonrry at hotmail.com  Sun Dec 12 02:39:32 2004
From: bonrry at hotmail.com (The Bonrry)
Date: Sun, 12 Dec 2004 03:39:32 +0100
Subject: [Icecast] OGG
Message-ID: <BAY17-F36F2614D4F2E9AE22C64D9D5AA0@phx.gbl>

Just a short mail to " encourage you to add support for OGG files to ices2" 
(from Tunez Install quick start ;-))

It would really be the ultimate powa if ices were able to stream ogg to 
icecast2 using both mp3 & ogg files as input, like oddcast plugin for winamp 
does :-D

All the ways, MANY THANKS for all you've already done for the community :-) 
and best wishes from Paris - France.


@+ bisous

Bonrry




From giles at xiph.org  Sun Dec 12 23:09:59 2004
From: giles at xiph.org (Ralph Giles)
Date: Sun, 12 Dec 2004 15:09:59 -0800
Subject: [Icecast] OGG
In-Reply-To: <BAY17-F36F2614D4F2E9AE22C64D9D5AA0@phx.gbl>
References: <BAY17-F36F2614D4F2E9AE22C64D9D5AA0@phx.gbl>
Message-ID: <20041212230959.GA19052@ghostscript.com>

On Sun, Dec 12, 2004 at 03:39:32AM +0100, The Bonrry wrote:

> Just a short mail to " encourage you to add support for OGG files to ices2" 
> (from Tunez Install quick start ;-))

ices2 has never supported anything else, so we've been happily obliging 
you for 3 years now. :-)

> It would really be the ultimate powa if ices were able to stream ogg to 
> icecast2 using both mp3 & ogg files as input, like oddcast plugin for 
> winamp does :-D

Perhaps you meant to request an mp3 input module that transcodes to ogg 
vorbis?

Glad you like the software,
 -r


From karl at xiph.org  Sun Dec 12 23:23:13 2004
From: karl at xiph.org (Karl Heyes)
Date: 12 Dec 2004 23:23:13 +0000
Subject: [Icecast] Metadata and bad player behaviour : cut sound for
	short time when receiving metadata (kh versions of ices/icecast)
In-Reply-To: <41BCBEC5.3070300@wwlang.net>
References: <41BCBEC5.3070300@wwlang.net>
Message-ID: <1102893792.10887.3329.camel@bogus.hackers.club>

On Sun, 2004-12-12 at 21:57, Iceuse - Kris wrote:
> Hello,
> 
> I was trying to add metadata to my OGG stream (ices 2,0-kh59, icecast 
> 2.0-kh51).
> It works... but the players are doing a small sound cut at metadata 
> reception :
> - VLC (maybe 1/3sec cut)
> - JORBIS (java. maybe 1/10sec, because I can have set higher priority to 
> sound processing and not to comment handling)
> (player plateform: Mac OS X 1.3.6)
> 
> With VLC... I can say comments are unusable, it's too bad... Maybe if 
> the comment change occurs between songs it not so noticeable, but that's 
> not very good...
> I didn't tried other players.

I'm having weird effects with sound in vlc 0.8.1, it keeps speeding up
and slowing down. Does ogg123 have a similar issue.  A possible cause is
that when new headers are received the player may very well reset the
audio interface to the settings in the new header and this could cause
the cut.

For a test, try downloading the stream to file then play the file back.

I haven't used JORBIS myself

> Before changing to latest icecast, I would like to know if there is a 
> similar trouble with it (I don't say it's an icecast issue, but maybe 
> with newer ogg headers are handled correctly by players. Anyway, VLC is 
> buggy regarding comments).

some players are known to have problems with chained bitstreams, my vlc
seems ok with the chaining but screws up on sound output.

There hasn't been much change in the way ogg is handled in the later
releases of icecast-kh, the headers are still handled the same way.

karl.




From papa.schlumpf at my-mail.ch  Sun Dec 12 23:56:24 2004
From: papa.schlumpf at my-mail.ch (Papa Schlumpf)
Date: Mon, 13 Dec 2004 00:56:24 +0100
Subject: [Icecast] Compiling Error
Message-ID: <000a01c4e0a6$3059a1f0$010aa8c0@pcdevelopment>

Hello
I have a little Problem to compile The Icecast2 Server on Linux Suse 9.0
In the Middle of the Compiling Process i became the following Error Message
Checking for xslt Config...No
configure: error: XSLT configuration could not be found

Lib XSLT is installed........
Greets Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041213/79b58037/attachment.htm>

From karl at xiph.org  Mon Dec 13 00:02:12 2004
From: karl at xiph.org (Karl Heyes)
Date: 13 Dec 2004 00:02:12 +0000
Subject: [Icecast] Compiling Error
In-Reply-To: <000a01c4e0a6$3059a1f0$010aa8c0@pcdevelopment>
References: <000a01c4e0a6$3059a1f0$010aa8c0@pcdevelopment>
Message-ID: <1102896131.10887.3409.camel@bogus.hackers.club>

On Sun, 2004-12-12 at 23:56, Papa Schlumpf wrote:
> Hello
> I have a little Problem to compile The Icecast2 Server on Linux Suse
> 9.0
> In the Middle of the Compiling Process i became the following Error
> Message
> Checking for xslt Config...No
> configure: error: XSLT configuration could not be found
>  
> Lib XSLT is installed........
> Greets Chris

The runtime package may be installed, but check if the development is as
well. look for the util xslt-config.

karl.




From iceuse at wwlang.net  Mon Dec 13 09:36:43 2004
From: iceuse at wwlang.net (Iceuse - Kris)
Date: Mon, 13 Dec 2004 10:36:43 +0100
Subject: [Icecast] Metadata and bad player behaviour : cut sound for	short
	time when receiving metadata (kh versions of ices/icecast)
In-Reply-To: <1102893792.10887.3329.camel@bogus.hackers.club>
References: <41BCBEC5.3070300@wwlang.net>
	<1102893792.10887.3329.camel@bogus.hackers.club>
Message-ID: <41BD62AB.4080705@wwlang.net>


>I'm having weird effects with sound in vlc 0.8.1, it keeps speeding up
>and slowing down. Does ogg123 have a similar issue.  A possible cause is
>that when new headers are received the player may very well reset the
>audio interface to the settings in the new header and this could cause
>the cut.
>
>  
>
I few month ago, I was using xmms (I can't set up X11 sound oc mac, so I 
can't use xmms any more), and I never noticed troubles with comments.

>For a test, try downloading the stream to file then play the file back.
>
>  
>
I'll test that.

>I haven't used JORBIS myself
>
>  
>
very nice tool. We can easilly build a beautifull java player around it.

>>Before changing to latest icecast, I would like to know if there is a 
>>similar trouble with it (I don't say it's an icecast issue, but maybe 
>>with newer ogg headers are handled correctly by players. Anyway, VLC is 
>>buggy regarding comments).
>>    
>>
>
>some players are known to have problems with chained bitstreams, my vlc
>seems ok with the chaining but screws up on sound output.
>  
>
I'll try to contact VLC team, because that's not nice at all. At least, 
they should ignore the comments, because they are not displaying them 
(just in a strange way in information window)


Regards,
Chris

>
>  
>



From pem at levillage.org  Mon Dec 13 20:32:00 2004
From: pem at levillage.org (Pierre-Emmanuel Muller)
Date: Mon, 13 Dec 2004 21:32:00 +0100
Subject: [Icecast] Icecast RPM for Fedora Core 3
Message-ID: <41BDFC40.1030709@levillage.org>

Hi all,

I've made an icecast RPM for Fedora Core 3.
It would be nice if someone can test it:
http://pem.levillage.org/icecast-2.1.0-1.i386.rpm

PeM


From ross at stationplaylist.com  Tue Dec 14 03:26:17 2004
From: ross at stationplaylist.com (Ross Levis)
Date: Tue, 14 Dec 2004 16:26:17 +1300
Subject: [Icecast] extended characters
Message-ID: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>

I mentioned this 1 or 2 years back but it's still not fixed.  I presume it's
a Icecast2 server problem.  I'm using the latest Oddcast client, and
my server host Mediacast1 has just updated to the latest Icecast2.

I'm currently streaming a track in Vorbis format called:
M?ire Brennan - I L?thair D?
It shows this correctly in Winamp on the broadcast PC.

On the Icecast Status page, it says the Current Song is:
M?e Brennan - I L?air D?

Listening to the stream (as a listener) in Winamp, it shows this as the
title:

M - I L

Regards,
Ross Levis
http://soulfm.stationplaylist.com/listen.m3u



From msmith at xiph.org  Tue Dec 14 04:04:09 2004
From: msmith at xiph.org (Michael Smith)
Date: Tue, 14 Dec 2004 15:04:09 +1100
Subject: [Icecast] extended characters
In-Reply-To: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>
References: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>
Message-ID: <200412141504.09940.msmith@xiph.org>

On Tuesday 14 December 2004 14:26, Ross Levis wrote:
> I mentioned this 1 or 2 years back but it's still not fixed.  I presume
> it's a Icecast2 server problem.  I'm using the latest Oddcast client, and
> my server host Mediacast1 has just updated to the latest Icecast2.
>
> I'm currently streaming a track in Vorbis format called:
> M?ire Brennan - I L?thair D?
> It shows this correctly in Winamp on the broadcast PC.
>
> On the Icecast Status page, it says the Current Song is:
> M?e Brennan - I L?air D?
>
> Listening to the stream (as a listener) in Winamp, it shows this as the
> title:
>
> M - I L
>

Ross,

I'm pretty sure icecast gets this all correct - though I'm not 100% certain 
about the status page, I think even that is correct.

I strongly suspect that this is an oddcast (or possibly, but less likely, 
winamp) bug. 

I couldn't check this, your stream was playing something with no non-ASCII 
characters at all when I went to have a look. 

If you'd like me to take a closer look, could you send me (off-list, please) 
one of the files you're streaming (the input file), and a capture/dump of the 
stream itself, containing the same track? Just a small section of each would 
be fine - all this metadata is found at the start of the file, so just 
sending the first 100kB would be fine.

Mike



From oddsock at oddsock.org  Tue Dec 14 04:10:55 2004
From: oddsock at oddsock.org (oddsock)
Date: Mon, 13 Dec 2004 22:10:55 -0600
Subject: [Icecast] extended characters
In-Reply-To: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>
References: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>
Message-ID: <6.0.1.1.2.20041213215731.02f55ae0@www.oddsock.org>

well, if I manually update the metadata via oddcast and enter "M? ire 
Brennan - I L??thair D??", then check the icecast2 status page, I see : 
Current Song: M?ire Brennan - I L?thair D?

which I presume is correct.  If I then open this stream with winamp, it 
displays as : M - I L?thair D?.  If I look at the file properties, the 
vorbis winamp plugin tells me there are two comment fields, ARTIST=M and 
TITLE=I L?thair D?.  Oddcastv2 only sent TITLE=M? ire Brennan - I L??thair 
D??, so that tells me that the winamp vorbis input plugin is not handling 
the charset properly.  Frankly I'm suprised that oddcast is actually 
handling it properly, but as far as I can tell (the icecast2 status page 
also shows <artist>M?ire Brennan</artist>
  and <title>I L?thair D?</title>) oddcast is setting the vorbis comments 
properly.  So that pretty much leaves only the vorbis input plugin.

oddsock
At 09:26 PM 12/13/2004, you wrote:
>I mentioned this 1 or 2 years back but it's still not fixed.  I presume it's
>a Icecast2 server problem.  I'm using the latest Oddcast client, and
>my server host Mediacast1 has just updated to the latest Icecast2.
>
>I'm currently streaming a track in Vorbis format called:
>M? ire Brennan - I L??thair D??
>It shows this correctly in Winamp on the broadcast PC.
>
>On the Icecast Status page, it says the Current Song is:
>M???e Brennan - I L???air D? ?
>
>Listening to the stream (as a listener) in Winamp, it shows this as the
>title:
>
>M - I L
>
>Regards,
>Ross Levis
>http://soulfm.stationplaylist.com/listen.m3u
>
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast
>




From oddsock at oddsock.org  Tue Dec 14 04:13:13 2004
From: oddsock at oddsock.org (oddsock)
Date: Mon, 13 Dec 2004 22:13:13 -0600
Subject: [Icecast] extended characters
In-Reply-To: <6.0.1.1.2.20041213215731.02f55ae0@www.oddsock.org>
References: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>
	<6.0.1.1.2.20041213215731.02f55ae0@www.oddsock.org>
Message-ID: <6.0.1.1.2.20041213221220.02f53108@www.oddsock.org>

At 10:10 PM 12/13/2004, you wrote:
>well, if I manually update the metadata via oddcast and enter "M? ire 
>Brennan - I L??thair D??", then check the icecast2 status page, I see : 
>Current Song: M?ire Brennan - I L?thair D?
>
>which I presume is correct.  If I then open this stream with winamp, it 
>displays as : M - I L?thair D?.  If I look at the file properties, the 
>vorbis winamp plugin tells me there are two comment fields, ARTIST=M and 
>TITLE=I L?thair D?.  Oddcastv2 only sent TITLE=M? ire Brennan - I L??thair 
>D??, so that tells me that the winamp vorbis input plugin is not handling 
>the charset properly.

correction, oddcast is sending TITLE=I L?thair D? and ARTIST=M?ire Brennan.


>Frankly I'm suprised that oddcast is actually handling it properly, but as 
>far as I can tell (the icecast2 status page also shows <artist>M?ire 
>Brennan</artist>
>  and <title>I L?thair D?</title>) oddcast is setting the vorbis comments 
> properly.  So that pretty much leaves only the vorbis input plugin.
>
>oddsock
>At 09:26 PM 12/13/2004, you wrote:
>>I mentioned this 1 or 2 years back but it's still not fixed.  I presume it's
>>a Icecast2 server problem.  I'm using the latest Oddcast client, and
>>my server host Mediacast1 has just updated to the latest Icecast2.
>>
>>I'm currently streaming a track in Vorbis format called:
>>M? ire Brennan - I L??thair D??
>>It shows this correctly in Winamp on the broadcast PC.
>>
>>On the Icecast Status page, it says the Current Song is:
>>M???e Brennan - I L???air D? ?
>>
>>Listening to the stream (as a listener) in Winamp, it shows this as the
>>title:
>>
>>M - I L
>>
>>Regards,
>>Ross Levis
>>http://soulfm.stationplaylist.com/listen.m3u
>>
>>_______________________________________________
>>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 oddsock at oddsock.org  Tue Dec 14 04:29:38 2004
From: oddsock at oddsock.org (oddsock)
Date: Mon, 13 Dec 2004 22:29:38 -0600
Subject: [Icecast] extended characters
In-Reply-To: <6.0.1.1.2.20041213215731.02f55ae0@www.oddsock.org>
References: <00ea01c4e18c$ad156cb0$4300a8c0@levis3>
	<6.0.1.1.2.20041213215731.02f55ae0@www.oddsock.org>
Message-ID: <6.0.1.1.2.20041213222237.02ee4a48@www.oddsock.org>

ok, after further review, it looks like it is oddcast that is not handling 
the charset properly.  I dumped an archive of what is being sent (the 
vorbis stream) and ran it through ogginfo, and I get :

User comments section follows...
         TITLE=I L??thair D??
Warning: Illegal UTF-8 sequence in comment 1 (stream 1): invalid sequence

The odd thing is that if I play that archive in winamp, the correct title 
(M?ire Brennan - I L?thair D?) shows, and if I play it in foobar2k, then 
only the TITLE shows (which clued me in on the fact that the vorbis 
comments might be wrong).  Of course, it still shows up properly in the 
status.xsl, which is even stranger.

So the problem is with oddcast and it's lack of handling UNICODE characters 
properly when adding vorbis comments to the stream.  Now fixing it...well, 
that's another story... :)  At least I have a nice reproducible test case.

oddsock
At 10:10 PM 12/13/2004, you wrote:
>well, if I manually update the metadata via oddcast and enter "M? ire 
>Brennan - I L??thair D??", then check the icecast2 status page, I see : 
>Current Song: M?ire Brennan - I L?thair D?
>
>which I presume is correct.  If I then open this stream with winamp, it 
>displays as : M - I L?thair D?.  If I look at the file properties, the 
>vorbis winamp plugin tells me there are two comment fields, ARTIST=M and 
>TITLE=I L?thair D?.  Oddcastv2 only sent TITLE=M? ire Brennan - I L??thair 
>D??, so that tells me that the winamp vorbis input plugin is not handling 
>the charset properly.  Frankly I'm suprised that oddcast is actually 
>handling it properly, but as far as I can tell (the icecast2 status page 
>also shows <artist>M?ire Brennan</artist>
>  and <title>I L?thair D?</title>) oddcast is setting the vorbis comments 
> properly.  So that pretty much leaves only the vorbis input plugin.
>
>oddsock
>At 09:26 PM 12/13/2004, you wrote:
>>I mentioned this 1 or 2 years back but it's still not fixed.  I presume it's
>>a Icecast2 server problem.  I'm using the latest Oddcast client, and
>>my server host Mediacast1 has just updated to the latest Icecast2.
>>
>>I'm currently streaming a track in Vorbis format called:
>>M? ire Brennan - I L??thair D??
>>It shows this correctly in Winamp on the broadcast PC.
>>
>>On the Icecast Status page, it says the Current Song is:
>>M???e Brennan - I L???air D? ?
>>
>>Listening to the stream (as a listener) in Winamp, it shows this as the
>>title:
>>
>>M - I L
>>
>>Regards,
>>Ross Levis
>>http://soulfm.stationplaylist.com/listen.m3u
>>
>>_______________________________________________
>>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 jbebel at ncsu.edu  Tue Dec 14 17:37:26 2004
From: jbebel at ncsu.edu (Joel Ebel)
Date: Tue, 14 Dec 2004 12:37:26 -0500
Subject: [Icecast] Streaming 2 different sources with darkice
Message-ID: <41BF24D6.1050004@ncsu.edu>

I'm looking for ideas here.  This probably will wind up being more of an 
alsa problem, but I thought the people on this list might have been in 
similar circumstances and have ideas for me.

I work at a radio station with both a webcast and FM broadcast.  We want 
to use icecast both for our webcast and as a backup studio to 
transmitter link.  However, the webcast audio needs to be 
post-processed, but the STL needs to be pre-processed because the 
processing gets done at the transmitter.  Our solution to this was to 
get an in-studio AGC to use just for the webcast.  So now we've got two 
different audio streams we need to send to icecast.  We've got an 
M-Audio Delta 66 with the post-processed audio on lines 1 and 2, and the 
pre-processed audio on lines 3 and 4.  I found a .asoundrc that lets me 
use the aliases channel1 and channel2 to address the different inputs, 
and these work fine in darkice.  However, they don't work at the same 
time.  I was running separate instances of darkice, and the second one 
will start, but apparently it can't open the audio device since it's 
locked by the first darkice process, even though it's on a different set 
of inputs.  Is there a good way around this, or does someone have a 
better solution to our broad issue of using icecast as a backup STL?

Thanks,
Joel Ebel


From oddsock at oddsock.org  Tue Dec 14 20:21:01 2004
From: oddsock at oddsock.org (oddsock)
Date: Tue, 14 Dec 2004 14:21:01 -0600
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
Message-ID: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>

Just wanted to let everyone know that we are prepping for a 2.2.0
release of icecast.  Just as before, we are doing Release candidates
first, and if no bugs are reported, these will become the official
release.  We ask that anyone that can, please test the RC and send any
issues or bug-reports to  the mailing list or http://trac.xiph.org/

until the mirrors get updated, please download the release using the
following links :

source distribution:
http://svn.xiph.org/releases/icecast/icecast-2.2.0RC1.tar.gz

win32 binary:
http://svn.xiph.org/releases/icecast/icecast2_win32_2.2.0RC1_setup.exe

eventually, these will be able to be downloaded here:
http://downloads.xiph.org/releases/icecast/

Additionally, to enable theora streaming in icecast, you will need the
most current theora release.  I have created a snapshot you can download
until theora creates an official release.  The snapshot can be
downloaded here :
http://www.oddsock.org/xiph_snapshots/libtheora-unreleased.tar.gz

This is  an optional dependency on icecast, and if you do not have it
installed,  then icecast will build properly, but you will not get
theora support.

Here is a synposis of the changes in 2.2.0

- Theora Video support -

Icecast now supports video streaming via theora.  Currently, we require
the latest (alpha 4) version of libtheora.  This is an optional compile,
so if you don't have theora then icecast will safely ignore it

- Shoutcast style source client support -

Icecast now supports the connection protocol used by the Shoutcast DSP
source client.  This is the same connection protocol used by their NSV
encoding tools. This means that not only can you use the Shoutcast DSP
to stream to icecast, but that you can also stream NSV via their tools.

- AAC is added as a supported streaming format -

Not too many source clients support streaming in this format, but we
support it.

- Cluster password -

Now you can specify a cluster password as a <mount> option in the
config. This will allow you to cluster multiple servers/mounts into a
single listing on the stream directory.  Note that this is different
than "grouping" which groups together streams coming from the same
physical IP and with the same stream name.  Clusters are meant for
relays of the same stream and will only be listed *once* in the stream
directory.  When a listener tunes into a cluster, they will be served an
m3u file with all the clusters for that stream.

- Playlist Log -

This is an option setting that will create an audit trail of metadata
that comes through icecast.  It is a single file that contains
information for all mountpoints.

- Range Support for static files -

We now support seeking in files served off the icecast fserve.

- Metadata Update via Admin -

We now support metadata updates via the admin interface for both MP3 AND
Ogg Vorbis streams.

- Per mount hidden stats and YP prevention -

You many now indicate certains mounts to be excluded (i.e. hidden) from
the main status.xsl page.  This is useful when using local private
relays.  You can also override the YP setting (as in disable) on a
per-mount basis.  Also useful for local private relays.

- Multiple example config files -

We now have multiple config files for you to use as a base.  A "simple"
one for quick-start, and a more detailed "advanced" one with all the
features, as well as a "shoutcast compatable" one, which shows how you'd
config for using the shoutcast DSP.

- Relay user/pass -

You can now specify authentication used by a relay.  This is for the
case where you have listener authentication enabled for a mountpoint,
and want to connect a relay to it.


oddsock




From Jason at Weatherserver.net  Tue Dec 14 20:44:03 2004
From: Jason at Weatherserver.net (Jason)
Date: Tue, 14 Dec 2004 15:44:03 -0500
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
Message-ID: <000a01c4e21d$a5fdf730$1401a8c0@workstation>

3 things
1) is the <mp3-metadata-interval> tag in this version
2) thats cool that nullsoft video works
3) what is Theora






From giles at xiph.org  Tue Dec 14 20:44:07 2004
From: giles at xiph.org (Ralph Giles)
Date: Tue, 14 Dec 2004 12:44:07 -0800
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
Message-ID: <20041214204407.GB24952@ghostscript.com>

On Tue, Dec 14, 2004 at 02:21:01PM -0600, oddsock wrote:

> eventually, these will be able to be downloaded here:
> http://downloads.xiph.org/releases/icecast/

The mirrors have now updated; please use these instead of the svn
server. Note that there are regional aliases as well:

  http://downloads.au.xiph.org/releases/icecast/ or
  http://downloads.us.xiph.org/releases/icecast/

Which may offer you a better transfer rate.

> - Theora Video support -
> 
> Icecast now supports video streaming via theora.  Currently, we require
> the latest (alpha 4) version of libtheora.  This is an optional compile,
> so if you don't have theora then icecast will safely ignore it

Yay video support!!! :-)

 -r


From ddominey86 at gmail.com  Tue Dec 14 20:48:26 2004
From: ddominey86 at gmail.com (Darrell Dominey)
Date: Tue, 14 Dec 2004 17:18:26 -0330
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
Message-ID: <2f3554e6041214124876199245@mail.gmail.com>

found a bug..when i click on update metadata from the admin panel, i
just get an eroor: Could not parse XSLT file

Darrell


On Tue, 14 Dec 2004 14:21:01 -0600, oddsock <oddsock at oddsock.org> wrote:
> Just wanted to let everyone know that we are prepping for a 2.2.0
> release of icecast.  Just as before, we are doing Release candidates
> first, and if no bugs are reported, these will become the official
> release.  We ask that anyone that can, please test the RC and send any
> issues or bug-reports to  the mailing list or http://trac.xiph.org/
> 
> until the mirrors get updated, please download the release using the
> following links :
> 
> source distribution:
> http://svn.xiph.org/releases/icecast/icecast-2.2.0RC1.tar.gz
> 
> win32 binary:
> http://svn.xiph.org/releases/icecast/icecast2_win32_2.2.0RC1_setup.exe
> 
> eventually, these will be able to be downloaded here:
> http://downloads.xiph.org/releases/icecast/
> 
> Additionally, to enable theora streaming in icecast, you will need the
> most current theora release.  I have created a snapshot you can download
> until theora creates an official release.  The snapshot can be
> downloaded here :
> http://www.oddsock.org/xiph_snapshots/libtheora-unreleased.tar.gz
> 
> This is  an optional dependency on icecast, and if you do not have it
> installed,  then icecast will build properly, but you will not get
> theora support.
> 
> Here is a synposis of the changes in 2.2.0
> 
> - Theora Video support -
> 
> Icecast now supports video streaming via theora.  Currently, we require
> the latest (alpha 4) version of libtheora.  This is an optional compile,
> so if you don't have theora then icecast will safely ignore it
> 
> - Shoutcast style source client support -
> 
> Icecast now supports the connection protocol used by the Shoutcast DSP
> source client.  This is the same connection protocol used by their NSV
> encoding tools. This means that not only can you use the Shoutcast DSP
> to stream to icecast, but that you can also stream NSV via their tools.
> 
> - AAC is added as a supported streaming format -
> 
> Not too many source clients support streaming in this format, but we
> support it.
> 
> - Cluster password -
> 
> Now you can specify a cluster password as a <mount> option in the
> config. This will allow you to cluster multiple servers/mounts into a
> single listing on the stream directory.  Note that this is different
> than "grouping" which groups together streams coming from the same
> physical IP and with the same stream name.  Clusters are meant for
> relays of the same stream and will only be listed *once* in the stream
> directory.  When a listener tunes into a cluster, they will be served an
> m3u file with all the clusters for that stream.
> 
> - Playlist Log -
> 
> This is an option setting that will create an audit trail of metadata
> that comes through icecast.  It is a single file that contains
> information for all mountpoints.
> 
> - Range Support for static files -
> 
> We now support seeking in files served off the icecast fserve.
> 
> - Metadata Update via Admin -
> 
> We now support metadata updates via the admin interface for both MP3 AND
> Ogg Vorbis streams.
> 
> - Per mount hidden stats and YP prevention -
> 
> You many now indicate certains mounts to be excluded (i.e. hidden) from
> the main status.xsl page.  This is useful when using local private
> relays.  You can also override the YP setting (as in disable) on a
> per-mount basis.  Also useful for local private relays.
> 
> - Multiple example config files -
> 
> We now have multiple config files for you to use as a base.  A "simple"
> one for quick-start, and a more detailed "advanced" one with all the
> features, as well as a "shoutcast compatable" one, which shows how you'd
> config for using the shoutcast DSP.
> 
> - Relay user/pass -
> 
> You can now specify authentication used by a relay.  This is for the
> case where you have listener authentication enabled for a mountpoint,
> and want to connect a relay to it.
> 
> oddsock
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


From oddsock at oddsock.org  Tue Dec 14 20:56:37 2004
From: oddsock at oddsock.org (oddsock)
Date: Tue, 14 Dec 2004 14:56:37 -0600
Subject: [Icecast] update metadata problem
In-Reply-To: <2f3554e6041214124876199245@mail.gmail.com>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<2f3554e6041214124876199245@mail.gmail.com>
Message-ID: <6.0.1.1.2.20041214145442.02f75ee8@www.oddsock.org>

At 02:48 PM 12/14/2004, you wrote:
>found a bug..when i click on update metadata from the admin panel, i
>just get an eroor: Could not parse XSLT file
>
>Darrell

what platform ? can you turn on icecast debugging post any related info 
?  I am unable to reproduce this problem.  Provide as many details as you 
can about your stream (type, source client, etc..)

oddsock 




From karl at xiph.org  Tue Dec 14 21:15:46 2004
From: karl at xiph.org (Karl Heyes)
Date: 14 Dec 2004 21:15:46 +0000
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <000a01c4e21d$a5fdf730$1401a8c0@workstation>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<000a01c4e21d$a5fdf730$1401a8c0@workstation>
Message-ID: <1103058944.10887.8749.camel@bogus.hackers.club>

On Tue, 2004-12-14 at 20:44, Jason wrote:
> 3 things
> 1) is the <mp3-metadata-interval> tag in this version

no

> 2) thats cool that nullsoft video works

yeah it is.

> 3) what is Theora

A video codec that is used in Ogg

karl.



From Jason at Weatherserver.net  Tue Dec 14 21:18:31 2004
From: Jason at Weatherserver.net (Jason)
Date: Tue, 14 Dec 2004 16:18:31 -0500
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org><000a01c4e21d$a5fdf730$1401a8c0@workstation>
	<1103058944.10887.8749.camel@bogus.hackers.club>
Message-ID: <001501c4e222$767e4a50$1401a8c0@workstation>

Windows Version
I'm testing the NSV. I used the shoutcast Compatible config file, the server 
is setup and running, the encoder is encoding.

If I use winamp and connect to http://smtp.weatherserver.net:8001/stream 
It says i'm connected but shows me no video.

Is that the right URL to connect too? 





From oddsock at oddsock.org  Tue Dec 14 21:38:45 2004
From: oddsock at oddsock.org (oddsock)
Date: Tue, 14 Dec 2004 15:38:45 -0600
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <001501c4e222$767e4a50$1401a8c0@workstation>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<000a01c4e21d$a5fdf730$1401a8c0@workstation>
	<1103058944.10887.8749.camel@bogus.hackers.club>
	<001501c4e222$767e4a50$1401a8c0@workstation>
Message-ID: <6.0.1.1.2.20041214151957.02fc0a98@www.oddsock.org>

Looks like I missed a config file entry for the shoutcast-compat.xml, 
you'll need to add :

<shoutcast-mount>/stream.nsv</shoutcast-mount>

to your config. It needs to exist at the main root level... for context 
here is where I have it :

     <directory>
         <yp-url-timeout>15</yp-url-timeout>
         <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
     </directory>
     <shoutcast-mount>/stream.nsv</shoutcast-mount>
     <hostname>localhost</hostname>

all NSV mounts must end in .nsv, and since you cannot specify the 
mountpoint in the NSV encoding tools, you are required to provide this as a 
config entry.

oddsock
At 03:18 PM 12/14/2004, you wrote:
>Windows Version
>I'm testing the NSV. I used the shoutcast Compatible config file, the 
>server is setup and running, the encoder is encoding.
>
>If I use winamp and connect to http://smtp.weatherserver.net:8001/stream 
>It says i'm connected but shows me no video.
>
>Is that the right URL to connect too?
>
>
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast
>




From Jason at Weatherserver.net  Tue Dec 14 22:13:17 2004
From: Jason at Weatherserver.net (Jason)
Date: Tue, 14 Dec 2004 17:13:17 -0500
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org><000a01c4e21d$a5fdf730$1401a8c0@workstation><1103058944.10887.8749.camel@bogus.hackers.club><001501c4e222$767e4a50$1401a8c0@workstation>
	<6.0.1.1.2.20041214151957.02fc0a98@www.oddsock.org>
Message-ID: <000701c4e22a$1d086610$1401a8c0@workstation>

Perfect,  works good now..


----- Original Message ----- 
From: "oddsock" <oddsock at oddsock.org>
To: <>
Sent: Tuesday, December 14, 2004 4:38 PM
Subject: Re: [Icecast] Icecast 2.2.0 RC1 Announcement


> Looks like I missed a config file entry for the shoutcast-compat.xml, 
> you'll need to add :
>
> <shoutcast-mount>/stream.nsv</shoutcast-mount>
>
> to your config. It needs to exist at the main root level... for context 
> here is where I have it :
>
>     <directory>
>         <yp-url-timeout>15</yp-url-timeout>
>         <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
>     </directory>
>     <shoutcast-mount>/stream.nsv</shoutcast-mount>
>     <hostname>localhost</hostname>
>
> all NSV mounts must end in .nsv, and since you cannot specify the 
> mountpoint in the NSV encoding tools, you are required to provide this as 
> a config entry.
>
> oddsock
> At 03:18 PM 12/14/2004, you wrote:
>>Windows Version
>>I'm testing the NSV. I used the shoutcast Compatible config file, the 
>>server is setup and running, the encoder is encoding.
>>
>>If I use winamp and connect to http://smtp.weatherserver.net:8001/stream 
>>It says i'm connected but shows me no video.
>>
>>Is that the right URL to connect too?
>>
>>
>>_______________________________________________
>>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 Jason at Weatherserver.net  Tue Dec 14 23:30:19 2004
From: Jason at Weatherserver.net (Jason)
Date: Tue, 14 Dec 2004 18:30:19 -0500
Subject: [Icecast] RC1 xslt error
Message-ID: <000001c4e234$e7097530$1401a8c0@workstation>

Using Suse 9.2 when I run ./configure I get configure: error: XSLT configuration could not be found

libxslt-1.1.12-1
libxml2-2.6.16-1
Is Installed.   

Can anyone help with this, I normally run the win32 versions.





 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Weather @ 6:28pm * Temp: -17.0 ?C * Humidity 51 % * Wind: NW @ 6 km/h
 Baro: 1027.04 kPa Rising * Vis: 19 km * Sky: Overcast * Weather: ---

 =-=-=-= Website: http://www.WeatherServer.net =-=-=-=-=-=-=-=
 Southern Ontario Weather Email Alerts, Closed Road Alerts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041214/297b0032/attachment.htm>

From karl at xiph.org  Tue Dec 14 23:38:22 2004
From: karl at xiph.org (Karl Heyes)
Date: 14 Dec 2004 23:38:22 +0000
Subject: [Icecast] RC1 xslt error
In-Reply-To: <000001c4e234$e7097530$1401a8c0@workstation>
References: <000001c4e234$e7097530$1401a8c0@workstation>
Message-ID: <1103067501.10887.8751.camel@bogus.hackers.club>

On Tue, 2004-12-14 at 23:30, Jason wrote:
> Using Suse 9.2 when I run ./configure I get configure: error: XSLT
> configuration could not be found
>  
> libxslt-1.1.12-1
> libxml2-2.6.16-1
> Is Installed.   
>  
> Can anyone help with this, I normally run the win32 versions.

those are just the runtime files, install the -devel packages as well

karl.




From oddsock at oddsock.org  Tue Dec 14 23:41:16 2004
From: oddsock at oddsock.org (oddsock)
Date: Tue, 14 Dec 2004 17:41:16 -0600
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <2f3554e6041214124876199245@mail.gmail.com>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<2f3554e6041214124876199245@mail.gmail.com>
Message-ID: <6.0.1.1.2.20041214173619.02f81a30@www.oddsock.org>

At 02:48 PM 12/14/2004, you wrote:
>found a bug..when i click on update metadata from the admin panel, i
>just get an eroor: Could not parse XSLT file
>
>Darrell
looks like I missed updatemetadata.xsl in the windows build.. I've fixed it 
and update the binary release.  Download it again and try again. (Note that 
it may not have propagated to the mirrors as yet).  Sorry about that...

oddsock 




From geoff at hitsandpieces.net  Wed Dec 15 06:53:15 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Wed, 15 Dec 2004 16:53:15 +1000
Subject: [Icecast] Prevent client disconnecting fallen-too-far-behind
In-Reply-To: <001c01c4d4cb$6aec57e0$6829a8c0@hvdr>
References: <001c01c4d4cb$6aec57e0$6829a8c0@hvdr>
Message-ID: <Pine.LNX.4.61.0412151650330.32545@data.home>

Hi:

Sorry, can't remember if you solved this or not.

Henk van de Ridder wrote:

> Does anybody know how I can configure icecast so it doesn't disconnect a
> client which "has fallen too far behind".
>
> We are using icecast2.01 streaming software for our church home-listening
> system.
> Our client we use a netgem-netbox.
> We are streaming 25kbps MP3 on V90-56kbps modem connection

A likely problem here is that 56K modems can only *upload* at 33.6.  For 
such a connection, a 25kbps stream may be a bit marginal.   Of course, if 
you're using a bigger pipe to send to icecast then ignore this.

Geoff.


-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From dihelson at yahoo.com  Wed Dec 15 10:31:36 2004
From: dihelson at yahoo.com (Mr Dihelson Mendonca)
Date: Wed, 15 Dec 2004 07:31:36 -0300 (ART)
Subject: [Icecast] Compatible Players - Windows Media BAD trying to open...
Message-ID: <20041215103136.58692.qmail@web54505.mail.yahoo.com>

hello, All,

I runa webradio on Icecast and Shoutcast also, but got
many compaints of listeners who tell me that they
can't listen to the broadcasts on Icecast, because,
SOMETIMES, although they already installed Winamp5,
when they click on the link, Windows Media player, or
Worst: PowerDVD is trying to open the ogg file. Any
tips ??

And I'd like to know if there's any Embedded player
code which could use on a website in order to play
Icecast. Common people don't like to have to download
things in order to listen to a station, when they can
hear many other using only Windows Media Player...

Is there any news concerning Windows Media to play ogg
Files ??

Thanks in advance,
Dihelson mendon?a


__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger 
http://br.download.yahoo.com/messenger/ 


From danstowell at gmail.com  Wed Dec 15 13:15:48 2004
From: danstowell at gmail.com (Dan Stowell)
Date: Wed, 15 Dec 2004 13:15:48 +0000
Subject: [Icecast] Compatible Players - Windows Media BAD trying to open...
In-Reply-To: <20041215103136.58692.qmail@web54505.mail.yahoo.com>
References: <20041215103136.58692.qmail@web54505.mail.yahoo.com>
Message-ID: <286e6b7c041215051557a98726@mail.gmail.com>

Dihelson,

Read my tutorial here:
http://www.mcld.co.uk/flatfour/player/about/

I hope it helps! It does exactly what you ask, using Quicktime
embedded in a webpage. Our stream is MP3 rather than Ogg but the
process should be the same.

The only problem is that many people don't have the Ogg codec
installed in Quicktime... you'd need to tell them how to install the
qt ogg plugin from http://qtcomponents.sourceforge.net/

Dan


On Wed, 15 Dec 2004 07:31:36 -0300 (ART), Mr Dihelson Mendonca
<dihelson at yahoo.com> wrote:
> hello, All,
> 
> I runa webradio on Icecast and Shoutcast also, but got
> many compaints of listeners who tell me that they
> can't listen to the broadcasts on Icecast, because,
> SOMETIMES, although they already installed Winamp5,
> when they click on the link, Windows Media player, or
> Worst: PowerDVD is trying to open the ogg file. Any
> tips ??
> 
> And I'd like to know if there's any Embedded player
> code which could use on a website in order to play
> Icecast. Common people don't like to have to download
> things in order to listen to a station, when they can
> hear many other using only Windows Media Player...
> 
> Is there any news concerning Windows Media to play ogg
> Files ??
> 
> Thanks in advance,
> Dihelson mendon?a
> 
> 
> __________________________________________________
> Converse com seus amigos em tempo real com o Yahoo! Messenger
> http://br.download.yahoo.com/messenger/
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


-- 
http://www.mcld.co.uk


From henk.vande.ridder at solcon.nl  Wed Dec 15 20:18:41 2004
From: henk.vande.ridder at solcon.nl (Henk van de Ridder)
Date: Wed, 15 Dec 2004 21:18:41 +0100
Subject: [Icecast] RE: RE: Prevent client disconnecting fallen-too-far-behind
Message-ID: <001501c4e2e3$475801a0$6829a8c0@hvdr>

Hello Geoff,

Thank you for answering.
The problem is partly solved by setting the queue size from 100k to 500k

The problem is not the upload, there we use DSL.
The problem is the download part of our clients (Netgem-netbox, with 56k
modem)

With kind regards,
Henk


Geoff wrote:

> Sorry, can't remember if you solved this or not.
>
> Henk van de Ridder wrote:
>
> > Does anybody know how I can configure icecast so it doesn't disconnect a
> > client which "has fallen too far behind".
> >
> > We are using icecast2.01 streaming software for our church
home-listening
> > system.
> > Our client we use a netgem-netbox.
> > We are streaming 25kbps MP3 on V90-56kbps modem connection
>
> A likely problem here is that 56K modems can only *upload* at 33.6.  For
> such a connection, a 25kbps stream may be a bit marginal.   Of course, if
> you're using a bigger pipe to send to icecast then ignore this.
>
> Geoff.




From geoff at hitsandpieces.net  Thu Dec 16 06:47:02 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Thu, 16 Dec 2004 16:47:02 +1000
Subject: [Icecast] Compatible Players - Windows Media BAD trying to open...
In-Reply-To: <20041215103136.58692.qmail@web54505.mail.yahoo.com>
References: <20041215103136.58692.qmail@web54505.mail.yahoo.com>
Message-ID: <Pine.LNX.4.61.0412161628240.32545@data.home>

Mr Dihelson Mendonca wrote:

> Is there any news concerning Windows Media to play ogg
> Files ??

There is.  The filters that are under most active development, IIRC, have 
only had HTTP streaming added recently and this might not be available in 
the latest binary release, but I might be wrong on this.  Anyway, it does 
appear to be in SVN.

Releases: http://www.illiminable.com/ogg/
Source: http://svn.xiph.org/trunk/oggdsf/

Geoff.



From jaromil at dyne.org  Thu Dec 16 12:37:16 2004
From: jaromil at dyne.org (jaromil)
Date: Thu, 16 Dec 2004 13:37:16 +0100
Subject: [Icecast] MuSE 0.9.1 codename STREAMTIME
Message-ID: <20041216123716.GB22600@dyne.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


    annunciazio' annunciazio'!

          dyne.org autoproduzioni & the FreakNet Medialab

                       proudly present:

           __  __       ____  _____    ___   ___   _
          |  \/  |_   _/ ___|| ____|  / _ \ / _ \ / |
          | |\/| | | | \___ \|  _|   | | | | (_) || |
          | |  | | |_| |___) | |___  | |_| |\__, || |
          |_|  |_|\__,_|____/|_____|  \___(_) /_(_)_|
                                  codename STREAMTIME


 this is RASTA SOFTWARE, Jah Rastafari Livity bless your freedom!

             :: the Multiple Streaming Engine ::
                    http://muse.dyne.org


This application is being developed in the hope to provide the Free
Software community a user friendly tool for network audio streaming,
making life easier for indypendent free speech radios wanting to
stream via http on icecast servers.

MuSE is an application for mixing, encoding, and network streaming of
sound: it can transmit an audio signal by mixing together sound taken
from files or also network, recursively remixing more MuSE streams.

MuSE can simultaneously mix up to 6 encoded audio bitstreams (from
files or network, ogg, mp3, wav and other common sound formats), plus
an input signal from microphone.

MuSE offers an intuitive interfaces to be operated in realtime, while
it can also run slick from the Unix commandline.

MuSE is employed in the http://www.streamtime.org project to foster the
creation of free community radios in Baghdad - the Tigris Project



==== WHAT'S NEW?

This release introduces several fixes in terms of stability and operability, so
everyone is recommended to upgrade!

:: FIXES
- - Ogg/Vorbis network streams can now be played and mixed
- - Ncurses console is fixed for proper streaming operation
- - Audio device handling has been rewritten
- - FIFO pipes have been cleaned up
- - continuous playmode and commandline encoder options have been fixed
- - encoding of vorbis is now CBR and works with various samplerates

:: EXPERIMENTAL FEATURES
these features are introduced by this release, alltough they are not fully
functional: experienced testing and contributions are very welcome!
- - porting to OSX
- - Jack support
- - time based scheduler for radio automation
- - Peer 2 peer streaming to Freedomnet/Proton




***** Supported servers:

You can use MuSE to stream both MP3 or Ogg/Vorbis sound format to a
broadcast server, which means that for doing an online radio you still
need to setup yours, or find one that let you stream.

Such servers can be seen like antennas which amplify your signal and
redistribute it to listeners. there are free software implementations
of such technology! the ones supported by MuSE are:

- - Icecast2 - http://icecast.org - can stream OGG & MP3
- - Litestream - http://litestream.org - can stream MP3
- - Darwin - http://developer.apple.com/darwin/projects/streaming
- - Shoutcast - http://shoutcast.com - non free, runs on win32
- - Freedomnet/Proton - ftp://ftp.dyne.org/freedomnet/proton - P2P


***** Supported players:

MuSE streams via http, it doesn't uses multicast technology, nor
RTP/RTSP, to have the widest possible range of compatible players.
You can listen audio produced by MuSE from almost every personal
computer and operating system, using one or more of the following:

- - xmms - http://www.xmms.org - for GNU/Linux, *BSD, Sun, etc.
- - mpg123 - http://www.mpg123.de - for various UNIX systems
- - itunes - http://www.apple.com/itunes - on MacOSX
- - zinf - http://www.zinf.org - on GNU/Linux and Win32
- - winamp - http://www.winamp.com - on all Win platforms
- - MuSE itself! ;)

and even more players: something should be also allready available for
handeld devices and embedded systems as well.


***** Libraries:

- - LAME (optional)
  Lame can be installed but is no more needed, in particular
  libmp3lame and the header lame.h must be properly installed.

- - OGG VORBIS (optional)
  You can compile and install libogg and libvorbis on your machine
  before compiling MuSE; the configure script will recognize them and
  include support for decoding and mixing of .ogg files.

- - GTK+ (optional) + libxml and glib
  if libgtk and all the related libraries are present, MuSE will
  compile the GTK+ graphic user interface for interactive use and
  additional fun.

- - NCURSES (optional)
  if libncurses is present, MuSE will compile a text console
  interactive interface to be used into ASCII terminals.

- - SNDFILE (optional)
  if libsndfile is present then you'll be able to play uncompressed
  sound files like wav, aiff, snd, voc, pvf, mat, au, sf etc.


***** Compile and install:

- - you can get latest version of lame: (if you already have lame and
  libmp3lame jump to point 2, after checking that version is >3.89)
  with 'lame --version'
  or download it from www.mp3dev.org/mp3 and follow the simple
  instructions to get installed this wonderful GPL mp3 encoder.

- - install libogg and libvorbis:
  http://www.xiph.org/ogg/vorbis/index.html

if you don't install any of the above, MuSE will be a simple player.

- - compile: cd MuSE-x.x.x ; ./configure (or try ./configure --help to
  have listed some compile options) ; make ; make install

*** RPM and Slackware TGZ binary packages are also made available on
    ftp://ftp.dyne.org/muse/releases

*** MuSE is also available on a couple of *NIX distributions, consult your
package manager as a binary version could be already provided by it. The
following distributions are known to include MuSE:
FreeBSD, Gentoo, NetBSD, Debian and of course [dyne:bolic]

***** need help to run GNU/Linux? don't worry! try http://dynebolic.org
      liveCD distribution for radio streaming, by the same author of MuSE





***** MUCH MORE DOCUMENTATION!

tutorials and manuals are available on http://muse.dyne.org <-----





***** Report bugs

BUG REPORTING is REALLY APPRECIATED! BUT TAKE CARE TO DO IT WELL:
please ALWAYS REPORT the muse --version you are running and possibly
run the binary with gdb giving us the backtrace of the error.

if you understand the above, please go to http://bugs.dyne.org and
submit a BUG!!!




===== AUTHORS

MuSE is copyleft (c) 2000-2004 by Denis "jaromil" Rojo

MuSE's GTK+ GUI is copyleft (c) 2001-2004 by Antonino "nightolo" Radici

MuSE's NCURSES GUI is copyleft (c) 2002-2004 by Luca "rubik" Profico

MuSE's first GUI is copyleft (c) 2000-2001 by August Black

included resampling algos are copyleft (c) 2002 by Matteo "MoP" Nastasi

MuSE's scheduler included code copyleft (c) 2004 by Eugen Melinte

part of the redistributed code is copyright by the respective authors,
please refer to the AUTHORS file and to the supplied sourcecode for
further information and to COPYING for the full license.

MANY THANKS for experienced testing and documentation go to Adam, Michel
(radio Lora), Doub, Aubergine and Tresnar .

the following organizations had supported development:
PUBLIC VOICE Lab ........ [ http://www.pvl.at ]
SERVUS.AT ............... [ http://www.servus.at ]

If you are part of an institution of cultural association, or even a
business organization regularly employing free software, please consider
to sponsor this project! it is good visibility for you and great help
for us to keep on developing this tool that is freely available and
widely used by radio stations across the world.


***** PLEASE SUPPORT US!
                                                                                                                                     
This whole software was built by autonomous efforts and occasionally
supported by non-profit organizations, while the development currently
relies on the political believing of MuSE's authors, that there should
be such a tool and it should be freely available to people willing to
do online radio.


:: PLEASE HELP PORTING MuSE on the OSX platform!
This task is very important since there is no equivalent free software
on the Arple platform that can let people stream online radio.
If you can afford to donate us some money let us know, we also need
new and old working hardware, especially a MAC G3 or G4 machine is
needed in order to complete the OSX porting, please donate if you can!

contact us on http://dyne.org/hackers_contact.php
or send online donations via paypal.com to jaromil \@\ dyne.org
and remember to visit the google ads on the pages, it helps ;)


The MuSE development team is also avaliable to run formation courses
about usage, customization and reuse/abuse of free and open source
software - it offers as well support and warranty, development of
software solutions and consulting.

There were a number of workshops allready done around Europe on free
and opensource network radio streaming by the hackers @ dyne.org
if you want to organize one you're very welcome to contact us!
this way you can also help us develop more free software.

THANKS, a thousand flowers will blossom!




== DISCLAIMER

This source code is free software; you can redistribute it and/or
modify it under the terms of the GNU Public License as published
by the Free Software Foundation; either version 2 of the License,
or (at your option) any later version.

This source code is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Please refer to the GNU Public License for more details.

You should have received a copy of the GNU Public License along with
this source code; if not, write to:
Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.



ciao

- -- 
 jaromil,  dyne.org rasta coder,  http://rastasoft.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Cryptographically signed mail, see http://gnupg.org

iD8DBQFBwYF8WLCC1ltubZcRAqGyAJ9EubGKBZoTIsaGD4uTQvxrRIRRCgCfb4/3
3JB1CjLWPAvvvF1PKuQbZhU=
=UmSk
-----END PGP SIGNATURE-----


From mike at altrion.org  Fri Dec 17 03:07:09 2004
From: mike at altrion.org (Mike Whitaker)
Date: Fri, 17 Dec 2004 03:07:09 +0000
Subject: [Icecast] MP3 streaming from icecast2 -> WMP
Message-ID: <BD9EEA60-4FD8-11D9-B76D-0030658F78FC@altrion.org>

Anyone conceive of any reason why I should have a stream that 
RealPlayer and iTunes have no problem with, but MP9 refuses to play: 
just sits there dumbly having loaded the .m3u that points to it, 
ignoring the play button?



From oddsock at oddsock.org  Fri Dec 17 03:42:32 2004
From: oddsock at oddsock.org (oddsock)
Date: Thu, 16 Dec 2004 21:42:32 -0600
Subject: [Icecast] MP3 streaming from icecast2 -> WMP
In-Reply-To: <BD9EEA60-4FD8-11D9-B76D-0030658F78FC@altrion.org>
References: <BD9EEA60-4FD8-11D9-B76D-0030658F78FC@altrion.org>
Message-ID: <6.0.1.1.2.20041216214124.01ed0ec0@www.oddsock.org>

At 09:07 PM 12/16/2004, you wrote:
>Anyone conceive of any reason why I should have a stream that RealPlayer 
>and iTunes have no problem with, but MP9 refuses to play: just sits there 
>dumbly having loaded the .m3u that points to it, ignoring the play button?
>
>_____________________________

hrmmm...what does the generated .m3u contain ? Did you set your <hostname> 
parameter properly in your icecast config ? I just tested mp3 steaming with 
WMP10, and it worked like a charm...

oddsock




From adam at xs4all.nl  Fri Dec 17 04:23:27 2004
From: adam at xs4all.nl (adam)
Date: Fri, 17 Dec 2004 05:23:27 +0100 (CET)
Subject: [Icecast] thanks
Message-ID: <20041217051901.V14368-100000@xs6.xs4all.nl>


hi,

for those that havent tried the jack-ices combo that is available from
Karl Heyes branch of the xiph svn (
http://svn.xiph.org/icecast/branches/kh ), I recommend it...it feels like
a massive jump forward in streaming apps as it breaks down the barriers
between 'player' apps and encoders....such a small step in some ways,
but the world it opens up for streaming is exciting...

Thanks to Karl and however else developed it :)

adam



From funkytwig at gmail.com  Fri Dec 17 15:52:57 2004
From: funkytwig at gmail.com (Ben Edwards)
Date: Fri, 17 Dec 2004 15:52:57 +0000
Subject: [Icecast] Setting up a source client
Message-ID: <32b873ff04121707528d6bf0a@mail.gmail.com>

We have access to an icecast server and i beleve we need to set up a
source client.  Had a look on the website but docs seem to be mainly
concerned with setting up a server.  What i really want is something
that i can use in conjunction with Jack Audio conection Kit.  any
pointers would be great.

If its any help I am using the DeMuDi 1.2.0. Linux distribution.

ben
-- 
Ben Edwards - Poole, UK, England
WARNING:This email contained partisan views - dont ever accuse me of
using the veneer of objectivity
If you have a problem emailing me use
http://www.gurtlush.org.uk/profiles.php?uid=4
(email address this email is sent from may be defunct)


From mike at altrion.org  Fri Dec 17 16:02:02 2004
From: mike at altrion.org (Mike Whitaker)
Date: Fri, 17 Dec 2004 16:02:02 +0000
Subject: [Icecast] MP3 streaming from icecast2 -> WMP
In-Reply-To: <6.0.1.1.2.20041216214124.01ed0ec0@www.oddsock.org>
References: <BD9EEA60-4FD8-11D9-B76D-0030658F78FC@altrion.org>
	<6.0.1.1.2.20041216214124.01ed0ec0@www.oddsock.org>
Message-ID: <FD49272E-5044-11D9-B76D-0030658F78FC@altrion.org>


On 17 Dec 2004, at 03:42, oddsock wrote:

> At 09:07 PM 12/16/2004, you wrote:
>> Anyone conceive of any reason why I should have a stream that 
>> RealPlayer and iTunes have no problem with, but MP9 refuses to play: 
>> just sits there dumbly having loaded the .m3u that points to it, 
>> ignoring the play button?
>>
>> _____________________________
>
> hrmmm...what does the generated .m3u contain ? Did you set your 
> <hostname> parameter properly in your icecast config ? I just tested 
> mp3 steaming with WMP10, and it worked like a charm...


I am a clot.

The m3u (one I'd hand generated) contained 
http://oursite.com:8000:/live1

Interestingly, neither Real nor iTunes apparently barf on the extra 
colon.



From iceuse at wwlang.net  Fri Dec 17 19:08:59 2004
From: iceuse at wwlang.net (Iceuse - Kris)
Date: Fri, 17 Dec 2004 20:08:59 +0100
Subject: [Icecast] Compatible Players - Windows Media BAD trying to open...
In-Reply-To: <286e6b7c041215051557a98726@mail.gmail.com>
References: <20041215103136.58692.qmail@web54505.mail.yahoo.com>
	<286e6b7c041215051557a98726@mail.gmail.com>
Message-ID: <41C32ECB.4030407@wwlang.net>

Hello,
this plugin enables users to play static ogg file, but I've never been 
able to play a stream with it and iTunes or QT.
Do you managed to play ogg streams with it?

regards,
Chris

Dan Stowell wrote:

>Dihelson,
>
>Read my tutorial here:
>http://www.mcld.co.uk/flatfour/player/about/
>
>I hope it helps! It does exactly what you ask, using Quicktime
>embedded in a webpage. Our stream is MP3 rather than Ogg but the
>process should be the same.
>
>The only problem is that many people don't have the Ogg codec
>installed in Quicktime... you'd need to tell them how to install the
>qt ogg plugin from http://qtcomponents.sourceforge.net/
>
>Dan
>



From Jason at Weatherserver.net  Sat Dec 18 00:30:22 2004
From: Jason at Weatherserver.net (Jason)
Date: Fri, 17 Dec 2004 19:30:22 -0500
Subject: [Icecast] 2 Questions
Message-ID: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>

1) Is it possible when using the mp3 steam not to have the ( data ) in the tag line like you can do with ogg
2) Can the meta-tag-refresh tag which is in the 2.0KH58 be put in the new 2.2.0 version.


Thanks


 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Weather @ 7:26pm * Temp: -18.8 ?C * Humidity 46 % * Wind: WSW @ 6 km/h
 Baro: 1027.04 kPa Steady * Vis: 14 km * Sky: Clear * Weather: ---

 =-=-=-= Website: http://www.WeatherServer.net =-=-=-=-=-=-=-=
 Southern Ontario Weather Email Alerts, Closed Road Alerts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041217/c9b11f1c/attachment.htm>

From dihelson at yahoo.com  Sat Dec 18 01:00:19 2004
From: dihelson at yahoo.com (Mr Dihelson Mendonca)
Date: Fri, 17 Dec 2004 22:00:19 -0300 (ART)
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>
Message-ID: <20041218010019.63338.qmail@web54509.mail.yahoo.com>

Helo, fellows,

Although I have researched a lot about this matter I
still didn't find any good solution.

The problem with Icecast OGG system is that common
people doesn't want to download any other software in
order to listen to a radio station, even a plugin...

People doesn't like to have to download Quicktime, nor
Winamp. They already have Windows Media Player on
their computers, so they already listen to LAUNCHCAST
for instance...

I agree that Ogg files quality have no comparison with
the old Mp3. Ogg mono files at 32k - 44.1khz is very
near CD quality. I would become a satisfied listener
with radios at 32k -44.1khz.

The problem is making Windows media Player to play it!
And this may not have any solution.

I got to solve this problem on Shoutcast systems which
broadcast in MP3. I got to make WMP play the MP3
stream very easy, without a listener having to
download anything.
If people want to know how, I suggest looking my
website:

www.portaldojazz.com

I have Icecast streams also, which have much more
quality, but I can see, I have 10 listeners of
MP3-WMP, while having 1 Icecast listener, and I guess
the only explanation to this is that people listen to
it with WMP.


[]'s
Dihelson mendon?a



	
	
		
_______________________________________________________ 
Yahoo! Acesso Gr?tis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet r?pida e gr?tis


From giles at xiph.org  Sat Dec 18 01:11:35 2004
From: giles at xiph.org (Ralph Giles)
Date: Fri, 17 Dec 2004 17:11:35 -0800
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <20041218010019.63338.qmail@web54509.mail.yahoo.com>
References: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>
	<20041218010019.63338.qmail@web54509.mail.yahoo.com>
Message-ID: <20041218011135.GD32378@ghostscript.com>

On Fri, Dec 17, 2004 at 10:00:19PM -0300, Mr Dihelson Mendonca wrote:

> The problem with Icecast OGG system is that common
> people doesn't want to download any other software in
> order to listen to a radio station, even a plugin...

Of course. But that's not the whole story. Microsoft only
supports MP3 because so many people listen to mp3 radio
stations and files. And before Window Media Player played
MP3, everyone had winamp installed because the nearest 
teenager (if I may) had installed it as a way to listen to 
cool--or at least free--music.

So, the more content is available in ogg, and the more
good and popular content that is available *only* in ogg,
the more people will install the players, and the more
vendors will ship support so their customers won't have
to.

> The problem is making Windows media Player to play it!
> And this may not have any solution.

There are plugins at http://www.illiminable.com/ogg/
you might give those a try.

Hopefully once they're stablized we can finally get
on the autodownload program and all this will go away.
Although people tell me it doesn't actually work.

 -r


From kent at kent.troymonster.com  Sat Dec 18 06:33:15 2004
From: kent at kent.troymonster.com (Kent)
Date: Fri, 17 Dec 2004 22:33:15 -0800 (PST)
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <20041218010019.63338.qmail@web54509.mail.yahoo.com>
References: <20041218010019.63338.qmail@web54509.mail.yahoo.com>
Message-ID: <Pine.LNX.4.58.0412172232050.10532@kent.troymonster.com>


This is a player that I use on my site.  It works well with Ogg and mp3.  
I have tested it with windoze, Fedora, and Netscape/SunOS.

http://www.javazoom.net/jlgui/jlgui.html

Cheers!
Kent


On Fri, 17 Dec 2004, Mr Dihelson Mendonca wrote:

> Helo, fellows,
> 
> Although I have researched a lot about this matter I
> still didn't find any good solution.
> 
> The problem with Icecast OGG system is that common
> people doesn't want to download any other software in
> order to listen to a radio station, even a plugin...
> 
> People doesn't like to have to download Quicktime, nor
> Winamp. They already have Windows Media Player on
> their computers, so they already listen to LAUNCHCAST
> for instance...
> 
> I agree that Ogg files quality have no comparison with
> the old Mp3. Ogg mono files at 32k - 44.1khz is very
> near CD quality. I would become a satisfied listener
> with radios at 32k -44.1khz.
> 
> The problem is making Windows media Player to play it!
> And this may not have any solution.
> 
> I got to solve this problem on Shoutcast systems which
> broadcast in MP3. I got to make WMP play the MP3
> stream very easy, without a listener having to
> download anything.
> If people want to know how, I suggest looking my
> website:
> 
> www.portaldojazz.com
> 
> I have Icecast streams also, which have much more
> quality, but I can see, I have 10 listeners of
> MP3-WMP, while having 1 Icecast listener, and I guess
> the only explanation to this is that people listen to
> it with WMP.
> 
> 
> []'s
> Dihelson mendon?a
> 
> 
> 
> 	
> 	
> 		
> _______________________________________________________ 
> Yahoo! Acesso Gr?tis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet r?pida e gr?tis
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


From dihelson at yahoo.com  Sat Dec 18 08:41:37 2004
From: dihelson at yahoo.com (Mr Dihelson Mendonca)
Date: Sat, 18 Dec 2004 05:41:37 -0300 (ART)
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <Pine.LNX.4.58.0412172232050.10532@kent.troymonster.com>
Message-ID: <20041218084137.51980.qmail@web54503.mail.yahoo.com>

Hello, Kent,

Indeed, I already knew this plugin. It works. The
problem with it (I don't know if you got to solve), is
that every time the listener wants to hear with it,
he/she has to confirm the JAVA certificate. 
I was told that in order to Sign this certificate, I
would need to pay U$400,00 for 2 years...

Wow!

Perhaps big enterprises could do it, my station is
very small...

Where are your site? I'd like to see it working!

Thank you.

[]'s
Dihelson



 --- Kent <kent at kent.troymonster.com> escreveu: 
> 
> This is a player that I use on my site.  It works
> well with Ogg and mp3.  
> I have tested it with windoze, Fedora, and
> Netscape/SunOS.
> 
> http://www.javazoom.net/jlgui/jlgui.html
> 
> Cheers!
> Kent
> 
> 
> On Fri, 17 Dec 2004, Mr Dihelson Mendonca wrote:
> 
> > Helo, fellows,
> > 
> > Although I have researched a lot about this matter
> I
> > still didn't find any good solution.
> > 
> > The problem with Icecast OGG system is that common
> > people doesn't want to download any other software
> in
> > order to listen to a radio station, even a
> plugin...
> > 
> > People doesn't like to have to download Quicktime,
> nor
> > Winamp. They already have Windows Media Player on
> > their computers, so they already listen to
> LAUNCHCAST
> > for instance...
> > 
> > I agree that Ogg files quality have no comparison
> with
> > the old Mp3. Ogg mono files at 32k - 44.1khz is
> very
> > near CD quality. I would become a satisfied
> listener
> > with radios at 32k -44.1khz.
> > 
> > The problem is making Windows media Player to play
> it!
> > And this may not have any solution.
> > 
> > I got to solve this problem on Shoutcast systems
> which
> > broadcast in MP3. I got to make WMP play the MP3
> > stream very easy, without a listener having to
> > download anything.
> > If people want to know how, I suggest looking my
> > website:
> > 
> > www.portaldojazz.com
> > 
> > I have Icecast streams also, which have much more
> > quality, but I can see, I have 10 listeners of
> > MP3-WMP, while having 1 Icecast listener, and I
> guess
> > the only explanation to this is that people listen
> to
> > it with WMP.
> > 
> > 
> > []'s
> > Dihelson mendon?a
> > 
> > 
> > 
> > 	
> > 	
> > 		
> >
>
_______________________________________________________
> 
> > Yahoo! Acesso Gr?tis - Instale o discador do
> Yahoo! agora. http://br.acesso.yahoo.com/ - Internet
> r?pida e gr?tis
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> > 
>  


	
	
		
_______________________________________________________ 
Yahoo! Acesso Gr?tis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet r?pida e gr?tis


From geoff at hitsandpieces.net  Sat Dec 18 12:24:50 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Sat, 18 Dec 2004 22:24:50 +1000
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <20041218011135.GD32378@ghostscript.com>
References: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>
	<20041218010019.63338.qmail@web54509.mail.yahoo.com>
	<20041218011135.GD32378@ghostscript.com>
Message-ID: <Pine.LNX.4.61.0412182220570.20900@data.home>

Ralph Giles wrote:

> Of course. But that's not the whole story. Microsoft only
> supports MP3 because so many people listen to mp3 radio
> stations and files. And before Window Media Player played
> MP3, everyone had winamp installed because the nearest
> teenager (if I may) had installed it as a way to listen to
> cool--or at least free--music.

Very true.  And WMP had support for MP3 files before it properly supported 
MP3 streaming.  Same with RealPLayer.  They added it because there was 
overwhelming user demand for it.

BTW: You can use the access log to determine whether or not your hypothesis 
is actually correct.  It stores the useragent header, if memory serves. 
You may well find that people are selecting MP3 because it's what they know 
- most people have heard of it, even if they've no idea what it is.  It's 
best to know your problem before you try to solve it.

Geoff.



-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From iceuse at wwlang.net  Sat Dec 18 16:44:26 2004
From: iceuse at wwlang.net (Iceuse - Kris)
Date: Sat, 18 Dec 2004 17:44:26 +0100
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <20041218143601.64312.qmail@web54504.mail.yahoo.com>
References: <20041218143601.64312.qmail@web54504.mail.yahoo.com>
Message-ID: <41C45E6A.5000306@wwlang.net>

Easy... when I made this java applet :
http://rbg.online.stalig.net/jplayer/radio-bro-gwened.html

I used a signed lib from jorbis without modifying it. I just made a 
subclass of JOrbisPlayer which change the behaviour for what I wanted.

I can provide my wall JBuilder project for those interested to use it.
Easy way:
- just change the html file to feed it with your ogg stream url
- do what you want in JStaligPlayer.java
Works on Mac (tester on 10.3.6 java 1.4.2), Win, Linux
I strongly recommand to rename JStaligPlayer in whatever you want.

The idea is to used the signed Jar provided by jorbis... nicely signed 
so we don't need to accept certificates or other several times : once is 
enought.
Please avoid any changed to this jar (this breaks the signature). Use 
the subclass of mainclass to add your code. (or find a way to get a 
signed jar).

Full jbuilder projet is here :
http://radio.stalig.com/downloads/JStaligPlayer-Plugin.zip
It will stay here a few weeks.

Regards,
Chris

Mr Dihelson Mendonca wrote:

>Yes, Kris,
>
>But how to do it ???
>
>All these JAVA players I have tried has the
>certificate problem. How to overcome that ?
>
>If you have any applets and Code which doesn't need
>anything than the listener click on it and begin to
>listen, please, send to me, I want to do some
>experiments on my little station!!
>
>Thanks in advance,
>Dihelson
>
>
>
> --- Iceuse - Kris <iceuse at wwlang.net> escreveu: 
>  
>
>>Hello,
>>But the advantage of a java player is that in a
>>500Kb file to download, 
>>you can provide listeners a very good player... It
>>takes seconds to 
>>download compared to any update of WMP or Real or
>>others which is 5Mo 
>>(at least)
>>
>>But with Java, the trouble is mainly users don't
>>have  a java on their 
>>machine...
>>by default no Windows has java and it's 15Mb to
>>download !
>>
>>The best way is to explain as much as possible that
>>it is in the 
>>interest of the listeners to make efforts to
>>download that stuff to be 
>>able to listen at ogg streams...
>>and maybe a WAVE sample comparing a 32k OGG and a
>>32K MP3 would help. 
>>I'll do that on my web site soon....
>>
>>
>>Chris
>>
>>Mr Dihelson Mendonca wrote:
>>    
>>



From kent at troymonster.com  Sat Dec 18 04:46:09 2004
From: kent at troymonster.com (Kent Nyberg)
Date: Fri, 17 Dec 2004 20:46:09 -0800
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <20041218011135.GD32378@ghostscript.com>
References: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>	<20041218010019.63338.qmail@web54509.mail.yahoo.com>
	<20041218011135.GD32378@ghostscript.com>
Message-ID: <41C3B611.80002@troymonster.com>

An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041217/adff23c0/attachment.htm>

From raizyr at mindspring.com  Mon Dec 20 15:16:13 2004
From: raizyr at mindspring.com (Raizyr)
Date: Mon, 20 Dec 2004 10:16:13 -0500
Subject: [Icecast] Ices 0.4 failing to write to cuefile
Message-ID: <41C6ECBD.3040904@mindspring.com>

I'm hoping someone can help with this problem.  I've got two sources 
using dynamic playlists via the perl playlist module, they work fine for 
a time,  and then the cuefile stops being updated,  logs show this error:

Could not open cuefile [/var/log/ices0/cjradio/ices.cue] for writing, 
cuefile not updated!

The file is still owned by the ices user and is still writable by owner, 
but Ices cant open it.  The stream continues to play,  but the metadata 
sent to the listeners is still the unchanged info in the cuefile.

Any ideas?

-- 
-Chris <raizyr at fatratz.com>
-------------
<a href="http://www.spreadfirefox.com/?q=affiliates&amp;id=45903&amp;t=1">Get Firefox!</a>



From lemmingsml at nerim.fr  Mon Dec 20 16:21:41 2004
From: lemmingsml at nerim.fr (EISELE Pascal)
Date: Mon, 20 Dec 2004 17:21:41 +0100
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
Message-ID: <41C6FC15.2030608@nerim.fr>

Great Job ! ;)
Are you planning to :
- correct the metadata problem when you're relaying an icecast v1 server 
? (our radio totaly depend on icecast v1...)
- add an option to enable backup streams only when the primary one is 
done ? I mean that if a defined two mountpoint that are relaying 
different stream (from a primary and a secondary server) and define the 
backup option to the second mountpoint, it should be great if the 
relaying starts and stop only when needed (when the backup option is used)
- add a function to switch listeners between too mountpoints ? (such as 
icecast v1)
- add a telnet interface (such as icecast v1)
Bests regards,

PE


oddsock a ?crit :

> Just wanted to let everyone know that we are prepping for a 2.2.0
> release of icecast.  Just as before, we are doing Release candidates
> first, and if no bugs are reported, these will become the official
> release.  We ask that anyone that can, please test the RC and send any
> issues or bug-reports to  the mailing list or http://trac.xiph.org/
>
> until the mirrors get updated, please download the release using the
> following links :
>
> source distribution:
> http://svn.xiph.org/releases/icecast/icecast-2.2.0RC1.tar.gz
>
> win32 binary:
> http://svn.xiph.org/releases/icecast/icecast2_win32_2.2.0RC1_setup.exe
>
> eventually, these will be able to be downloaded here:
> http://downloads.xiph.org/releases/icecast/
>
> Additionally, to enable theora streaming in icecast, you will need the
> most current theora release.  I have created a snapshot you can download
> until theora creates an official release.  The snapshot can be
> downloaded here :
> http://www.oddsock.org/xiph_snapshots/libtheora-unreleased.tar.gz
>
> This is  an optional dependency on icecast, and if you do not have it
> installed,  then icecast will build properly, but you will not get
> theora support.
>
> Here is a synposis of the changes in 2.2.0
>
> - Theora Video support -
>
> Icecast now supports video streaming via theora.  Currently, we require
> the latest (alpha 4) version of libtheora.  This is an optional compile,
> so if you don't have theora then icecast will safely ignore it
>
> - Shoutcast style source client support -
>
> Icecast now supports the connection protocol used by the Shoutcast DSP
> source client.  This is the same connection protocol used by their NSV
> encoding tools. This means that not only can you use the Shoutcast DSP
> to stream to icecast, but that you can also stream NSV via their tools.
>
> - AAC is added as a supported streaming format -
>
> Not too many source clients support streaming in this format, but we
> support it.
>
> - Cluster password -
>
> Now you can specify a cluster password as a <mount> option in the
> config. This will allow you to cluster multiple servers/mounts into a
> single listing on the stream directory.  Note that this is different
> than "grouping" which groups together streams coming from the same
> physical IP and with the same stream name.  Clusters are meant for
> relays of the same stream and will only be listed *once* in the stream
> directory.  When a listener tunes into a cluster, they will be served an
> m3u file with all the clusters for that stream.
>
> - Playlist Log -
>
> This is an option setting that will create an audit trail of metadata
> that comes through icecast.  It is a single file that contains
> information for all mountpoints.
>
> - Range Support for static files -
>
> We now support seeking in files served off the icecast fserve.
>
> - Metadata Update via Admin -
>
> We now support metadata updates via the admin interface for both MP3 AND
> Ogg Vorbis streams.
>
> - Per mount hidden stats and YP prevention -
>
> You many now indicate certains mounts to be excluded (i.e. hidden) from
> the main status.xsl page.  This is useful when using local private
> relays.  You can also override the YP setting (as in disable) on a
> per-mount basis.  Also useful for local private relays.
>
> - Multiple example config files -
>
> We now have multiple config files for you to use as a base.  A "simple"
> one for quick-start, and a more detailed "advanced" one with all the
> features, as well as a "shoutcast compatable" one, which shows how you'd
> config for using the shoutcast DSP.
>
> - Relay user/pass -
>
> You can now specify authentication used by a relay.  This is for the
> case where you have listener authentication enabled for a mountpoint,
> and want to connect a relay to it.
>
>
> oddsock
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>




From lemmingsml at nerim.fr  Mon Dec 20 16:26:16 2004
From: lemmingsml at nerim.fr (EISELE Pascal)
Date: Mon, 20 Dec 2004 17:26:16 +0100
Subject: [Icecast] icecast2 relaying question
In-Reply-To: <41B8F230.1090902@ucsd.edu>
References: <41B8F230.1090902@ucsd.edu>
Message-ID: <41C6FD28.8030702@nerim.fr>

Hi,

You can do what you said.
Example :

 <relay>
        <server>xxxxxxx.letsgozik.com</server>
        <port>13103</port>
        <mount>/letsgozik</mount>
        <local-mount>/letsgozik-HiQ</local-mount>
    </relay>

    <relay>
        <server>xxxxxxx.letsgozik.com</server>
        <port>131455</port>
        <mount>/letsgozik-LowQ</mount>
        <local-mount>/letsgozik-LowQ</local-mount>
    </relay>

Jose Otero a ?crit :

> I understand there are two types of relays in icecast2.  The master 
> relay which relays everything from a source and  a point relay which 
> relays a specific mount point from a source.
>
> I have a server which has 3 streams.  I want to relay 2 of them.  How 
> can I do this?
>
> Can I define two relays and two mountpoints within the xml config file?
>
> Do i do this in the same relay tag:
> <relay>
> somehow define both here?
> </relay>
>
> or
>
> <relay1>
> .
> .
> .
> </relay1>
>
> and
>
> <relay2>
> .
> .
> .
> </relay2>
>
> Anyhelp you can give me would be much appreciated.  If you have an 
> example, that may work the best.
>
> Thanks for your time.
>
> Jose
> www.scansandiego.net
>
>
> P.S.  Not sure if the replys will automatically go to my email 
> address.  My web access is flakey right now, so please be sure to 
> reply to my email address and this group.  (email:  jdotero(at)ucsd.edu)
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>




From oddsock at oddsock.org  Mon Dec 20 16:36:42 2004
From: oddsock at oddsock.org (oddsock)
Date: Mon, 20 Dec 2004 10:36:42 -0600
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <41C6FC15.2030608@nerim.fr>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<41C6FC15.2030608@nerim.fr>
Message-ID: <6.0.1.1.2.20041220103221.03152f40@www.oddsock.org>

At 10:21 AM 12/20/2004, you wrote:
>Great Job ! ;)
>Are you planning to :
>- correct the metadata problem when you're relaying an icecast v1 server ? 
>(our radio totaly depend on icecast v1...)

we don't support icecast 1.x.  The question is, why are you dependent on it ?

>- add an option to enable backup streams only when the primary one is done 
>? I mean that if a defined two mountpoint that are relaying different 
>stream (from a primary and a secondary server) and define the backup 
>option to the second mountpoint, it should be great if the relaying starts 
>and stop only when needed (when the backup option is used)

I think you are describing on-demand relays, and karl has that in his 
branch.. I'd suggest you testing it out if that's something you need or use.

>- add a function to switch listeners between too mountpoints ? (such as 
>icecast v1)

icecast 2.x has had this for a long time.

>- add a telnet interface (such as icecast v1)

we now use a web-based interface.  I doubt we will be implementing the 
telnet based one again unless someone contributes it.

oddsock 




From karl at xiph.org  Mon Dec 20 16:46:34 2004
From: karl at xiph.org (Karl Heyes)
Date: 20 Dec 2004 16:46:34 +0000
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <41C6FC15.2030608@nerim.fr>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<41C6FC15.2030608@nerim.fr>
Message-ID: <1103561192.9035.531.camel@bogus.hackers.club>

On Mon, 2004-12-20 at 16:21, EISELE Pascal wrote:
> Great Job ! ;)
> Are you planning to :
> - correct the metadata problem when you're relaying an icecast v1 server 
> ? (our radio totaly depend on icecast v1...)

2 queries on this...

What is the metadata problem that you are referring to ?
What is making you depend on icecast v1 ?

> - add an option to enable backup streams only when the primary one is 
> done ? I mean that if a defined two mountpoint that are relaying 
> different stream (from a primary and a secondary server) and define the 
> backup option to the second mountpoint, it should be great if the 
> relaying starts and stop only when needed (when the backup option is used)

This sounds like the on-demand relay setting I have in my branch, if it
is then it won't be in 2.2 but should be merged afterwards

> - add a function to switch listeners between too mountpoints ? (such as 
> icecast v1)

the moveclients[.xsl] interface can already do that. 

> - add a telnet interface (such as icecast v1)

There hasn't been any call for a telnet interface, the web interface
suffices for most people.

karl.




From msmith at xiph.org  Mon Dec 20 23:27:17 2004
From: msmith at xiph.org (Michael Smith)
Date: Tue, 21 Dec 2004 10:27:17 +1100
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <41C6FC15.2030608@nerim.fr>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<41C6FC15.2030608@nerim.fr>
Message-ID: <200412211027.17871.msmith@xiph.org>

On Tuesday 21 December 2004 03:21, EISELE Pascal wrote:
> Great Job ! ;)
> Are you planning to :
> - correct the metadata problem when you're relaying an icecast v1 server
> ? (our radio totaly depend on icecast v1...)

Are you planning on reporting a bug here? Because we've never heard of any 
problem with this... As far as I know, this works fine. 

> - add an option to enable backup streams only when the primary one is
> done ? I mean that if a defined two mountpoint that are relaying
> different stream (from a primary and a secondary server) and define the
> backup option to the second mountpoint, it should be great if the
> relaying starts and stop only when needed (when the backup option is used)

On-demand relays won't be in this release, they are planned for a future 
release.

> - add a function to switch listeners between too mountpoints ? (such as
> icecast v1)

This was in both 2.0 and 2.1, and will be in 2.2. 

> - add a telnet interface (such as icecast v1)

No, very unlikely to ever be added. However, you can issue the appropriate 
HTTP commands for everything in the admin interface using a telnet client if 
you really, really, want to. HTTP is simple!

Mike



From oddsock at oddsock.org  Tue Dec 21 00:06:55 2004
From: oddsock at oddsock.org (oddsock)
Date: Mon, 20 Dec 2004 18:06:55 -0600
Subject: [Icecast] oddcastv3-jack
Message-ID: <6.0.1.1.2.20041220180411.03189a68@www.oddsock.org>

just wanted to let everyone know that I have a version of oddcastv3 that 
runs as a jack client (http://jackit.sourceforge.net).  I'd appreciate any 
feedback (good OR bad) from those that are using jack...

download it here : 
http://www.oddsock.org/tools/oddcastv3_jack/oddcastv3-jack-snapshot.tar.gz

oddsock




From paulley at gmail.com  Tue Dec 21 01:26:21 2004
From: paulley at gmail.com (Aaron Paulley)
Date: Mon, 20 Dec 2004 20:26:21 -0500
Subject: [Icecast] Tracking bandwidth used of individual mountpoints?
Message-ID: <df1af8c904122017265d1746f9@mail.gmail.com>

Is it possible to somehow meter and log the bandwidth used by
individual mountpoints? I'm using mrtg to monitor the whole server,
but I'd like to know which mountpoints are creating the most traffic
so I can offer better-priced streaming packages to users who really
aren't using all that much bandwidth. And also to be able to charge
more for users who use way much more bandwidth than they are supposed
to be using. As things stand right now, I can't differentiate the
different mountpoint streams' bandwidth usage.

Thanks,
Aaron


From lemmingsml at nerim.fr  Tue Dec 21 09:09:47 2004
From: lemmingsml at nerim.fr (EISELE Pascal)
Date: Tue, 21 Dec 2004 10:09:47 +0100
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <6.0.1.1.2.20041220103221.03152f40@www.oddsock.org>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>	<41C6FC15.2030608@nerim.fr>
	<6.0.1.1.2.20041220103221.03152f40@www.oddsock.org>
Message-ID: <41C7E85B.9010402@nerim.fr>

First, thanks for all your answers ! ;)

oddsock a ?crit :

> At 10:21 AM 12/20/2004, you wrote:
>
>> Great Job ! ;)
>> Are you planning to :
>> - correct the metadata problem when you're relaying an icecast v1 
>> server ? (our radio totaly depend on icecast v1...)
>
>
> we don't support icecast 1.x.  The question is, why are you dependent 
> on it ?

I should declare a bug but I've read many mail in icecast at xiph.org ML 
talking about this kind of problem. So I was thinking that someone have 
already work on this.
The problem is that "song title" is not relayed between our icecast v1 
server and our icecast v2 relay.
I need icecast 1 because all our system is using it....
I've created many scripts to :
- transcode (re-encode) a stream to another bitrate/format
- a script to switch between our two stream (one for live event and the 
other for automatic scheduling)
Moreover we are using ices for icecast 1 with a lot a script to get 
title, switch playlists, etc...





From karl at xiph.org  Tue Dec 21 15:26:35 2004
From: karl at xiph.org (Karl Heyes)
Date: 21 Dec 2004 15:26:35 +0000
Subject: [Icecast] Icecast 2.2.0 RC1 Announcement
In-Reply-To: <41C7E85B.9010402@nerim.fr>
References: <6.0.1.1.2.20041214141541.02f3e930@www.oddsock.org>
	<41C6FC15.2030608@nerim.fr>
	<6.0.1.1.2.20041220103221.03152f40@www.oddsock.org>
	<41C7E85B.9010402@nerim.fr>
Message-ID: <1103642795.9035.1909.camel@bogus.hackers.club>

On Tue, 2004-12-21 at 09:09, EISELE Pascal wrote:

> I should declare a bug but I've read many mail in icecast at xiph.org ML 
> talking about this kind of problem. So I was thinking that someone have 
> already work on this.

any references to those messages, those are archived at
http://lists.xiph.org/pipermail/

> The problem is that "song title" is not relayed between our icecast v1 
> server and our icecast v2 relay.

I don't know if in-stream mp3 metadata streaming was in icecast1, but
the protocol makes the client ask for it
eg <relay-shoutcast-metadata>1</relay-shoutcast-metadata>

> I need icecast 1 because all our system is using it....
> I've created many scripts to :
> - transcode (re-encode) a stream to another bitrate/format
> - a script to switch between our two stream (one for live event and the 
> other for automatic scheduling)
> Moreover we are using ices for icecast 1 with a lot a script to get 
> title, switch playlists, etc...

ices can talk to icecast 2

karl.




From karl at xiph.org  Tue Dec 21 15:33:29 2004
From: karl at xiph.org (Karl Heyes)
Date: 21 Dec 2004 15:33:29 +0000
Subject: [Icecast] Tracking bandwidth used of individual mountpoints?
In-Reply-To: <df1af8c904122017265d1746f9@mail.gmail.com>
References: <df1af8c904122017265d1746f9@mail.gmail.com>
Message-ID: <1103643209.9035.1921.camel@bogus.hackers.club>

On Tue, 2004-12-21 at 01:26, Aaron Paulley wrote:
> Is it possible to somehow meter and log the bandwidth used by
> individual mountpoints? I'm using mrtg to monitor the whole server,
> but I'd like to know which mountpoints are creating the most traffic
> so I can offer better-priced streaming packages to users who really
> aren't using all that much bandwidth. And also to be able to charge
> more for users who use way much more bandwidth than they are supposed
> to be using. As things stand right now, I can't differentiate the
> different mountpoint streams' bandwidth usage.

we could add stats for this sort of thing, can you raise a request for
this on trac.xiph.org

karl.




From mat.harris at genestate.com  Tue Dec 21 16:07:22 2004
From: mat.harris at genestate.com (Mat Harris)
Date: Tue, 21 Dec 2004 16:07:22 +0000
Subject: [Icecast] Tracking bandwidth used of individual mountpoints?
In-Reply-To: <1103643209.9035.1921.camel@bogus.hackers.club>
References: <df1af8c904122017265d1746f9@mail.gmail.com>
	<1103643209.9035.1921.camel@bogus.hackers.club>
Message-ID: <20041221160722.GA2410@genestate.com>

On Tue, Dec 21, 2004 at 03:33:29 +0000, Karl Heyes wrote:
> On Tue, 2004-12-21 at 01:26, Aaron Paulley wrote:
> > Is it possible to somehow meter and log the bandwidth used by
> > individual mountpoints? I'm using mrtg to monitor the whole server,
> > but I'd like to know which mountpoints are creating the most traffic
> > so I can offer better-priced streaming packages to users who really
> > aren't using all that much bandwidth. And also to be able to charge
> > more for users who use way much more bandwidth than they are supposed
> > to be using. As things stand right now, I can't differentiate the
> > different mountpoint streams' bandwidth usage.
> 
> we could add stats for this sort of thing, can you raise a request for
> this on trac.xiph.org
> 
> karl.

i'd like to second this. it's a feature i would be very please to see.

mat

-- 
Cats land on their feet. 
Toast lands jellyside down.
A cat glued to some jelly toast will hover in quantum indecision

Yes, of course it's the right cabl [le0: NO CARRIER]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041221/835e9019/attachment.sig>

From danielsoma at hotmail.com  Tue Dec 21 17:28:21 2004
From: danielsoma at hotmail.com (Daniel Soma)
Date: Tue, 21 Dec 2004 14:28:21 -0300
Subject: [Icecast] hello i have a  problem
Message-ID: <BAY1-F3168F22C7C3999B91D6140D4A30@phx.gbl>

i was following a thread fron this mailing list ,a web embed player  for ogg 
stream
i am in a =  situation  , need a player or a way to play  stream that no 
require java -for download plugin , is heavy -
i like to know how revsolve he problem or get a solution}
sorry , I am Argentino ,i don?t speak english just i read a bit and now i?m 
writing
dani

_________________________________________________________________
MSN Amor: busca tu ? naranja http://latam.msn.com/amor/



From oddsock at oddsock.org  Tue Dec 21 21:14:53 2004
From: oddsock at oddsock.org (oddsock)
Date: Tue, 21 Dec 2004 15:14:53 -0600
Subject: [Icecast] Icecast 2.2.0 Announcement
Message-ID: <6.0.1.1.2.20041221151231.03113568@www.oddsock.org>

We've just released 2.2 of Icecast...it may take a bit for the website to 
be updated and propagated.  For those who want to download the new release, 
it can be found here : http://downloads.us.xiph.org/releases/icecast/

Thanks to all who have helped test!

The Icecast Development Team




From Jason at Weatherserver.net  Wed Dec 22 01:05:50 2004
From: Jason at Weatherserver.net (Jason)
Date: Tue, 21 Dec 2004 20:05:50 -0500
Subject: [Icecast] Stream Online Script
Message-ID: <000701c4e7c2$634fc3a0$1401a8c0@workstation>

Anyone have or know of scripting that can be put on a website to show if a mountpoint/stream is online or not?



 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Weather @ 8:04pm - Temp: -16.1 ?C - WindChill -16.1 ?C - Humidity 0 % - Wind: ESE @ 5 km/h
 Baro: 1015.04 kPa Rising - Vis: 14 km - Sky: Overcast - Weather: ---

 =-=-=-= Website: http://www.WeatherServer.net =-=-=-=-=-=-=-=
 Southern Ontario Weather Email Alerts, Closed Road Alerts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041221/bee20f51/attachment.htm>

From pnm at zephyr.to  Wed Dec 22 02:11:27 2004
From: pnm at zephyr.to (Paul Melnikow)
Date: Tue, 21 Dec 2004 21:11:27 -0500
Subject: [Icecast] Stream Online Script
In-Reply-To: <000701c4e7c2$634fc3a0$1401a8c0@workstation>
References: <000701c4e7c2$634fc3a0$1401a8c0@workstation>
Message-ID: <20041222021127.GA24469@netspace.org>

On Tue, Dec 21, 2004 at 08:05:50PM -0500, Jason wrote:
> Anyone have or know of scripting that can be put on a website to show
> if a mountpoint/stream is online or not?
> 

i have a python script that gives mountpoint status (including numbers
of listeners). you could pipe the output through grep or wc -l depending
on what you're interested in.

	http://www.zephyr.to/icecast/icecast2-status

to make this work, you'll have to put the icecast2 admin password in
this file -- depending on your server setup, this may or may not be
doable in a secure way.

hope this is useful :)

peace
p.

-- 
every day is a good day


From adam at xs4all.nl  Wed Dec 22 03:00:05 2004
From: adam at xs4all.nl (adam)
Date: Wed, 22 Dec 2004 04:00:05 +0100 (CET)
Subject: [Icecast] theora streaming
Message-ID: <20041222035925.K22280-100000@xs6.xs4all.nl>


any clues on how to test 2.2 with theora are much appreciated

adam




From giles at xiph.org  Wed Dec 22 04:37:59 2004
From: giles at xiph.org (Ralph Giles)
Date: Tue, 21 Dec 2004 20:37:59 -0800
Subject: [Icecast] theora streaming
In-Reply-To: <20041222035925.K22280-100000@xs6.xs4all.nl>
References: <20041222035925.K22280-100000@xs6.xs4all.nl>
Message-ID: <20041222043759.GA28934@ghostscript.com>

On Wed, Dec 22, 2004 at 04:00:05AM +0100, adam wrote:

> any clues on how to test 2.2 with theora are much appreciated

the ffmpeg2theora page has some examples for how to get streaming going. 
Those work great if you're happy on the commandline. (except of course 
you can use the 2.2 release instead of the experimental icecast-kh 
branch like it says. :-)

   http://www.v2v.cc/~j/ffmpeg2theora/examples.html

HTH,
 -r


From oddsock at oddsock.org  Wed Dec 22 05:38:39 2004
From: oddsock at oddsock.org (oddsock)
Date: Tue, 21 Dec 2004 23:38:39 -0600
Subject: [Icecast] Theora streaming guide...
Message-ID: <6.0.1.1.2.20041221233649.032d16c8@www.oddsock.org>

After getting a whole mess of "Hey, Video streaming! Pretty sweet, How do I 
do it ?!?!" type questions, I decided to write up a small guide to getting 
started with it.  This is just based off my own experiences while doing the 
testing for the 2.2 icecast release.

http://www.oddsock.org/guides/video.php

oddsock




From jerret at gmail.com  Wed Dec 22 05:49:10 2004
From: jerret at gmail.com (Jerret Kinsman)
Date: Tue, 21 Dec 2004 21:49:10 -0800
Subject: [Icecast] Using stdin with ezstream
Message-ID: <df01641b04122121493e9944dc@mail.gmail.com>

Sorry to bother you guys but I couldn't find the answer to my problem
anywhere else.

I've installed ezstream_win32_0.1.1_setup.exe to my Windows XP box and
I am trying to  use the stdin streaming functionality w/ IceCast v2.2.
ezstream works well when I set the filename to a file, however, it
does not work with stdin.

With filename=stdin the source_client_connections stat in IceCast is
equal to 1, however, the sources stat is equal to 0.

I'm assuming that playing a file on Windows Media player/other clients
play to stdin.

If you have any ideas/pointers I would really appreciate it.

Thanks,
Jerret


From geoff at hitsandpieces.net  Wed Dec 22 06:00:33 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Wed, 22 Dec 2004 16:00:33 +1000
Subject: [Icecast] Using stdin with ezstream
In-Reply-To: <df01641b04122121493e9944dc@mail.gmail.com>
References: <df01641b04122121493e9944dc@mail.gmail.com>
Message-ID: <Pine.LNX.4.61.0412221554450.25093@data.home>

Jerret Kinsman wrote:

> I'm assuming that playing a file on Windows Media player/other clients
> play to stdin.

Not usually, anyway.  If you play something using WMP or any other player, 
it'll play to the soundcard.  Don't get standard input/output mixed up with 
soundcard input/output, they're two entirely different beasts and need not 
at all be related.

If you want to be able to stream whatever your soundcard plays, eztream is 
probably not the tool for you.  The simplest thing I can think of is to use 
streamtranscoder from oddsock.org in its linein mode.  Or you could use 
oddcast DSP and a line recorder with your favourite player.  Then all you'd 
need to do is configure your soundcard to record whatever it plays, and 
exactly how you do that will be dependent on your soundcard and what they 
call stuff.  But Windows volume Control is the place to sort this stuff 
out.

If you did actually mean Standard Input, then unless you've got something 
to process said files, there's probably not a lot to be gained by using 
standard input.  Maybe tell us what you're trying to do and we can take it 
from there.

Geoff.



From danielsoma at hotmail.com  Wed Dec 22 12:06:41 2004
From: danielsoma at hotmail.com (Daniel Soma)
Date: Wed, 22 Dec 2004 09:06:41 -0300
Subject: [Icecast] Re:Re :ihave a problem
Message-ID: <BAY1-F1EB253C521FC15A740E34D4A40@phx.gbl>

hi Adam
Thank you for your fast answer
I affraid that I don?t point? to the right problem
I need a solution for all case , user don?t need install anything and dont 
know that player is default
just click and go that is the problem , how to do?
i think in a java player , minimal ,lite o something similar
for windows users i put in the page a xmplay with a .pls pointing tu server, 
is a temporary solution
for linux users xmms is the most used and dont have problem
i dont think for mac users (i am sorry , accept sugerencias)but a java was 
my intention

in this need help
exist a solution, sure ,have a lot streams in the net and no everybody 
drive?  PC


Have a good christmas,you too



Hi Dani

You write English very well :)

If you use Linux then you can use XMMS to play Ogg streams. Otherwise use
Winamp for Microsoft Windows. I am not ssure what player in Mac supports
Ogg though.

Have a good christmas :)

adam


On Tue, 21 Dec 2004, Daniel Soma wrote:

>i was following a thread fron this mailing list ,a web embed player  for 
>ogg
>stream
>i am in a =  situation  , need a player or a way to play  stream that no
>require java -for download plugin , is heavy -
>i like to know how revsolve he problem or get a solution}
>sorry , I am Argentino ,i don?t speak english just i read a bit and now i?m
>writing
>dani
>

_________________________________________________________________
Charla con tus amigos en l?nea mediante MSN Messenger: 
http://messenger.latam.msn.com/



From bjorn at digitalsouth.net.nz  Wed Dec 22 12:51:03 2004
From: bjorn at digitalsouth.net.nz (Bjorn Patterson)
Date: Thu, 23 Dec 2004 01:51:03 +1300
Subject: [Icecast] A Question
Message-ID: <20041222125100.4C6749C855@nemissius.digitalsouth.net.nz>

Heya,
just a question is it possible to do a make install to a diffrent dir than
the defualt
 
_________________________________________________
Regards: 
Bjorn Patterson

Digitalsouth Networks
Technician 
Phone: 021 2674751 
Fax: (03) 2157121 
HYPERLINK "http://www.digitalsouth.net.nz/"http://www.digitalsouth.net.nz
 
[ When replying to this, please include a copy of the original message. ]
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.3 - Release Date: 12/21/2004
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041223/877858c5/attachment.htm>

From mp at xmission.com  Wed Dec 22 17:33:11 2004
From: mp at xmission.com (Myke Place)
Date: Wed, 22 Dec 2004 10:33:11 -0700
Subject: [Icecast] AAC encoders?
Message-ID: <20041222173310.GA3441@xmission.com>

Now that Icecast 2.2 supports AAC encoded streams, I'm looking around
for an encoder that will take raw-audio->AAC for a live stream on a
Linux platform. I glanced at the docs for Darkice and StreamTranscoder
as well as some other 3rd-party apps listed on icecast.org but none seem
to encode to AAC.

Any suggestions?

-mp


From oddsock at oddsock.org  Wed Dec 22 17:36:48 2004
From: oddsock at oddsock.org (oddsock)
Date: Wed, 22 Dec 2004 11:36:48 -0600
Subject: [Icecast] AAC encoders?
In-Reply-To: <20041222173310.GA3441@xmission.com>
References: <20041222173310.GA3441@xmission.com>
Message-ID: <6.0.1.1.2.20041222113517.03313d48@www.oddsock.org>

http://www.oddsock.org/tools/oddcastv3_jack/

That will do it...you'll need to install jack and find something to feed 
your raw audio into jack, but I'm pretty sure all that's available...

For AAC encoding, you will need to download libfaac before installing 
oddcastv3_jack...

oddsock

At 11:33 AM 12/22/2004, you wrote:
>Now that Icecast 2.2 supports AAC encoded streams, I'm looking around
>for an encoder that will take raw-audio->AAC for a live stream on a
>Linux platform. I glanced at the docs for Darkice and StreamTranscoder
>as well as some other 3rd-party apps listed on icecast.org but none seem
>to encode to AAC.
>
>Any suggestions?
>
>-mp
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast




From karl at xiph.org  Wed Dec 22 17:57:19 2004
From: karl at xiph.org (Karl Heyes)
Date: 22 Dec 2004 17:57:19 +0000
Subject: [Icecast] A Question
In-Reply-To: <20041222125100.4C6749C855@nemissius.digitalsouth.net.nz>
References: <20041222125100.4C6749C855@nemissius.digitalsouth.net.nz>
Message-ID: <1103738239.9035.3531.camel@bogus.hackers.club>

On Wed, 2004-12-22 at 12:51, Bjorn Patterson wrote:
> Heya,
> just a question is it possible to do a make install to a diffrent dir
> than the defualt

The usual procedure is

configure --prefix=/different/place

however depending on your setup and the installations of dependencies
you may need to set other flags like --with-ogg or maybe environment
vars like OGG_PREFIX

karl.




From briana at windwireless.net  Wed Dec 22 18:01:26 2004
From: briana at windwireless.net (Brian W. Antoine)
Date: Wed, 22 Dec 2004 10:01:26 -0800
Subject: [Icecast] ices-0.4 Reencode problems
Message-ID: <6.0.0.22.2.20041222095402.0241f880@mxa.windwireless.net>

   Since the mailing list archives are a bit difficult to go through at the
moment, I'll go ahead and simply ask.  If I fire up ices-0.4 with reencode
enabled, at pretty much the end of every song I get an error:

bitstream problem: resyncing...

   Occasionally it will also throw in a:

mpg123: Can't rewind stream by NNN bits!

   And eventually after a dozen songs or so I'll get a rash of:

Error during send: Libshout reported send error, disconnecting: Socket error

   and it will close the connection and try to re-open it, only to get the
same error again.  I'm running lame-3.96.1, libshout-2.0 and icecast-2.2.0,
though it did it with icecast-2.1.0 also.  It will run without a hitch if
I don't turn reencoding on.

   Anybody else seeing this kind of thing?



From paulley at gmail.com  Wed Dec 22 18:48:38 2004
From: paulley at gmail.com (Aaron Paulley)
Date: Wed, 22 Dec 2004 13:48:38 -0500
Subject: [Icecast] Recommnded system
Message-ID: <df1af8c9041222104855e1870c@mail.gmail.com>

Can't find any recommended system specs on the website.

What are they? Will it run well on a Celeron 1GHz? How about a 700Mhz?

I'm asking because the company I'm hosting through is running a
special on 700Mhz and 1Ghz servers, and if Icecast will run on these,
I may just go ahead and lease 4-5 more to move my icecast stuff onto
dedicated servers.


From oddsock at oddsock.org  Wed Dec 22 19:14:43 2004
From: oddsock at oddsock.org (oddsock)
Date: Wed, 22 Dec 2004 13:14:43 -0600
Subject: [Icecast] Recommnded system
In-Reply-To: <df1af8c9041222104855e1870c@mail.gmail.com>
References: <df1af8c9041222104855e1870c@mail.gmail.com>
Message-ID: <6.0.1.1.2.20041222130900.03309740@www.oddsock.org>

At 12:48 PM 12/22/2004, you wrote:
>Can't find any recommended system specs on the website.
>
>What are they? Will it run well on a Celeron 1GHz? How about a 700Mhz?

we don't have any specific specs, but icecast will run on some very low-end 
systems.    As far as CPU goes, icecast takes very little CPU, it's all 
I/O, and mostly network read and writes.  So either of those class servers 
should run fine.  Most always, the limiting factor is the network interface.

oddsock 




From mp at xmission.com  Wed Dec 22 19:39:44 2004
From: mp at xmission.com (Myke Place)
Date: Wed, 22 Dec 2004 12:39:44 -0700
Subject: [Icecast] Recommnded system
In-Reply-To: <df1af8c9041222104855e1870c@mail.gmail.com>
References: <df1af8c9041222104855e1870c@mail.gmail.com>
Message-ID: <20041222193944.GA4533@xmission.com>

I run Icecast 2.1 on a 733Mhz machine with 7 streams that push about
12Mbit/sec in total and the machine is basically idle. 

I've also pushed nearly 600 concurrent streams (60+Mbit/sec) off a
dual-Celeron box without a hitch.

-mp

* Aaron Paulley (paulley at gmail.com) [041222 11:48] spake thusly:
> Can't find any recommended system specs on the website.
> 
> What are they? Will it run well on a Celeron 1GHz? How about a 700Mhz?
> 
> I'm asking because the company I'm hosting through is running a
> special on 700Mhz and 1Ghz servers, and if Icecast will run on these,
> I may just go ahead and lease 4-5 more to move my icecast stuff onto
> dedicated servers.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


From mike at linuxlink.com  Wed Dec 22 19:36:26 2004
From: mike at linuxlink.com (Michael H. Collins)
Date: Wed, 22 Dec 2004 13:36:26 -0600
Subject: [Icecast] Recommnded system
In-Reply-To: <6.0.1.1.2.20041222130900.03309740@www.oddsock.org>
References: <df1af8c9041222104855e1870c@mail.gmail.com>
	<6.0.1.1.2.20041222130900.03309740@www.oddsock.org>
Message-ID: <41C9CCBA.1000500@linuxlink.com>

audio is working fine on this 300 mgz box.  It might get weird when I 
try to stream vid from it though.

I usually just do ices on the old boxes and send to a large server with 
icecast but i am just trying to wring what i can outa this box.



oddsock wrote:
> At 12:48 PM 12/22/2004, you wrote:
> 
>> Can't find any recommended system specs on the website.
>>
>> What are they? Will it run well on a Celeron 1GHz? How about a 700Mhz?
> 
> 
> we don't have any specific specs, but icecast will run on some very 
> low-end systems.    As far as CPU goes, icecast takes very little CPU, 
> it's all I/O, and mostly network read and writes.  So either of those 
> class servers should run fine.  Most always, the limiting factor is the 
> network interface.
> 
> oddsock
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 
> 


-- 
Michael H. Collins  Admiral, Penguinista Navy

http://linuxlink.com

/"\    	ASCII Ribbon Campaign
\ /    	No HTML/RTF in email
  x     	No Word docs in email
/ \    	Respect for open standards

Take your laptop and yell out:
"Can a brother get a ip address?"



From wb0gaz at hotmail.com  Wed Dec 22 21:28:18 2004
From: wb0gaz at hotmail.com (david feldman)
Date: Wed, 22 Dec 2004 14:28:18 -0700
Subject: [Icecast] Low-bitrate audio encode/stream application
In-Reply-To: <20041222200003.2C49B1CB3E@westfish.xiph.org>
Message-ID: <BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>

I am totally new to icecast, and would appreciate a pointer in the right 
direction. My application is to encode audio (at the linux server) at a low 
bit rate, say ~16 kbps, for transmission to a decoder at another location. 
The audio source will be bandlimited (basically voice grade circuit such as 
you'd find in a telephone application.) The decoder end (connected via a 
TCP/IP session) would be a Windows CE 3.0 machine which may be limited to 
MP3 decode format. I've looked through what documentation I could find on 
icecast and haven't seen anything that tells me how to characterize the 
audio encoding rules (how do you pick 16 kbps, 32 kbps, etc., stereo, mono, 
etc.?) Anyway, a pointer to the correct documentation resource would be 
greatly appreciated.

Tks,

Dave
wb0gaz at hotmail.com




From giles at xiph.org  Wed Dec 22 21:51:28 2004
From: giles at xiph.org (Ralph Giles)
Date: Wed, 22 Dec 2004 13:51:28 -0800
Subject: [Icecast] Low-bitrate audio encode/stream application
In-Reply-To: <BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>
References: <20041222200003.2C49B1CB3E@westfish.xiph.org>
	<BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>
Message-ID: <20041222215127.GA30153@ghostscript.com>

On Wed, Dec 22, 2004 at 02:28:18PM -0700, david feldman wrote:

> I am totally new to icecast, and would appreciate a pointer in the right 
> direction. My application is to encode audio (at the linux server) at a low 
> bit rate, say ~16 kbps, for transmission to a decoder at another location. 
> The audio source will be bandlimited (basically voice grade circuit such as 
> you'd find in a telephone application.) The decoder end (connected via a 
> TCP/IP session) would be a Windows CE 3.0 machine which may be limited to 
> MP3 decode format.

> I've looked through what documentation I could find on 
> icecast and haven't seen anything that tells me how to characterize the 
> audio encoding rules (how do you pick 16 kbps, 32 kbps, etc., stereo, mono, 
> etc.?) Anyway, a pointer to the correct documentation resource would be 
> greatly appreciated.

There are actually two pieces to this. Icecast itself is a server. It 
reflects streams from so-called 'source clients' to listening clients. 
It's in the source client that you set the encoding parameters. Ices is 
probably the best thing to use on linux, but there are others. See 
http://icecast.org/ices.php and http://icecast.org/3rdparty.php for 
links and associated howtos.

BTW, if you're actually doing voice over your very-low-bandwidth 
connection, you might consider our speex codec. It's designed 
specifically for speech and will in general do a much better job than 
vorbis or mp3 below 32 kbps. http://speex.org/

HTH,
 -r


From brendan at xiph.org  Wed Dec 22 22:51:20 2004
From: brendan at xiph.org (Brendan Cully)
Date: Wed, 22 Dec 2004 14:51:20 -0800
Subject: [Icecast] ices-0.4 Reencode problems
In-Reply-To: <6.0.0.22.2.20041222095402.0241f880@mxa.windwireless.net>
References: <6.0.0.22.2.20041222095402.0241f880@mxa.windwireless.net>
Message-ID: <20041222225119.GA24910@watanabe.local>

On Wednesday, 22 December 2004 at 10:01, Brian W. Antoine wrote:
>   Since the mailing list archives are a bit difficult to go through at the
> moment, I'll go ahead and simply ask.  If I fire up ices-0.4 with reencode
> enabled, at pretty much the end of every song I get an error:
> 
> bitstream problem: resyncing...
> 
>   Occasionally it will also throw in a:
> 
> mpg123: Can't rewind stream by NNN bits!
> 
>   And eventually after a dozen songs or so I'll get a rash of:

these are probably harmless warnings LAME will emit if there's
something odd in the source MP3 stream. I doubt they are directly
connected to the send error.

> Error during send: Libshout reported send error, disconnecting: Socket error

>   and it will close the connection and try to re-open it, only to get the
> same error again.  I'm running lame-3.96.1, libshout-2.0 and icecast-2.2.0,
> though it did it with icecast-2.1.0 also.  It will run without a hitch if
> I don't turn reencoding on.

Is it possible that you don't have enough CPU? The icecast logs would
probably have more useful information.


From jbebel at ncsu.edu  Wed Dec 22 23:15:53 2004
From: jbebel at ncsu.edu (Joel Ebel)
Date: Wed, 22 Dec 2004 18:15:53 -0500
Subject: [Icecast] fallback override failing for 128 mbps mp3 stream
Message-ID: <41CA0029.9070806@ncsu.edu>

I'm still having an issue with the fallback override from a 128 kbps mp3 
stream.  I have 6 streams all with fallbacks and overrides.  All are 
working except the 128 mp3.  All of the fallback streams are from 
ezstream which just plays a file matching the original source format. 
my 3 ogg streams and 2 of my mp3 streams work just fine with fallbacks 
and come back when the original stream returns.  I don't understand why 
the 128 mp3 doesn't.  It's set up just the same.

Here's the weird thing... if I go into the web interface and move my 
client from the 128 stream to it's fallback and then move it back to the 
original source it works fine.  Just not when the fallback override is 
supposed to take effect.

When the source disappears, the fallback stream begins playing just 
fine.  When the original stream returns, winamp stops playing audio, but 
the time keeps going up.  The kbps keeps going up too until I stop it. 
stopping and restarting connects to the original source stream just fine.

So what's the matter with the 128 mp3 stream?  Why is it behaving 
differently than all the other streams I have?

Thanks,
Joel


From wb0gaz at hotmail.com  Wed Dec 22 23:24:22 2004
From: wb0gaz at hotmail.com (david feldman)
Date: Wed, 22 Dec 2004 16:24:22 -0700
Subject: [Icecast] Low-bitrate audio encode/stream application
In-Reply-To: <20041222215127.GA30153@ghostscript.com>
Message-ID: <BAY101-F2349C2C4743D2A136908A496A40@phx.gbl>

Thanks Ralph,

speex is also interesting, and it will be for speech content, however, the 
listener side will be limited to generic CODEC (I don't want to port 
software to the CE machine, but rather use the existing older audio 
decoder(s) present there).

Anyway, this is good info, and I'll do some further reading.

Dave

>From: Ralph Giles <giles at xiph.org>
>To: david feldman <wb0gaz at hotmail.com>
>CC: icecast at xiph.org
>Subject: Re: [Icecast] Low-bitrate audio encode/stream application
>Date: Wed, 22 Dec 2004 13:51:28 -0800
>
>On Wed, Dec 22, 2004 at 02:28:18PM -0700, david feldman wrote:
>
> > I am totally new to icecast, and would appreciate a pointer in the right
> > direction. My application is to encode audio (at the linux server) at a 
>low
> > bit rate, say ~16 kbps, for transmission to a decoder at another 
>location.
> > The audio source will be bandlimited (basically voice grade circuit such 
>as
> > you'd find in a telephone application.) The decoder end (connected via a
> > TCP/IP session) would be a Windows CE 3.0 machine which may be limited 
>to
> > MP3 decode format.
>
> > I've looked through what documentation I could find on
> > icecast and haven't seen anything that tells me how to characterize the
> > audio encoding rules (how do you pick 16 kbps, 32 kbps, etc., stereo, 
>mono,
> > etc.?) Anyway, a pointer to the correct documentation resource would be
> > greatly appreciated.
>
>There are actually two pieces to this. Icecast itself is a server. It
>reflects streams from so-called 'source clients' to listening clients.
>It's in the source client that you set the encoding parameters. Ices is
>probably the best thing to use on linux, but there are others. See
>http://icecast.org/ices.php and http://icecast.org/3rdparty.php for
>links and associated howtos.
>
>BTW, if you're actually doing voice over your very-low-bandwidth
>connection, you might consider our speex codec. It's designed
>specifically for speech and will in general do a much better job than
>vorbis or mp3 below 32 kbps. http://speex.org/
>
>HTH,
>  -r




From msmith at xiph.org  Wed Dec 22 23:27:08 2004
From: msmith at xiph.org (Michael Smith)
Date: Thu, 23 Dec 2004 10:27:08 +1100
Subject: [Icecast] Recommnded system
In-Reply-To: <df1af8c9041222104855e1870c@mail.gmail.com>
References: <df1af8c9041222104855e1870c@mail.gmail.com>
Message-ID: <200412231027.08232.msmith@xiph.org>

On Thursday 23 December 2004 05:48, Aaron Paulley wrote:
> Can't find any recommended system specs on the website.
>
> What are they? Will it run well on a Celeron 1GHz? How about a 700Mhz?
>
> I'm asking because the company I'm hosting through is running a
> special on 700Mhz and 1Ghz servers, and if Icecast will run on these,
> I may just go ahead and lease 4-5 more to move my icecast stuff onto
> dedicated servers.

Icecast itself has very low cpu requirements. If your system can handle the 
network traffic, it can scale to several thousand concurrent listeners on 
(for example; a system I tested it on a while ago) a 400 MHz system.

However, if you're also trying to do _encoding_ on the system, you'll run into 
cpu limitations reasonably quickly if you have many simultaneous streams. 
Most people don't do their encoding on the server, though, so this may well 
be ok.

Mike



From Dennis at Heerema.net  Wed Dec 22 23:39:35 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Thu, 23 Dec 2004 00:39:35 +0100
Subject: [Icecast] Encoders
Message-ID: <004401c4e87f$8fb28af0$0202a8c0@heerema.local>

Hi There,

The discussion about speex triggered the following question:

Is there a way to use other encoders, to stream with icecast / oddcast.

Is there an format of witch the encoder shoul be standarized to (ACM or
something like that), if so would it be possible to use open license
encoders and commercail encoders with this. like FHG mp3, mp3pro, speex and
so on.

regards,

Dennis Heerema




From karl at xiph.org  Wed Dec 22 23:37:02 2004
From: karl at xiph.org (Karl Heyes)
Date: 22 Dec 2004 23:37:02 +0000
Subject: [Icecast] fallback override failing for 128 mbps mp3 stream
In-Reply-To: <41CA0029.9070806@ncsu.edu>
References: <41CA0029.9070806@ncsu.edu>
Message-ID: <1103758622.9035.3885.camel@bogus.hackers.club>

On Wed, 2004-12-22 at 23:15, Joel Ebel wrote:
...

> When the source disappears, the fallback stream begins playing just 
> fine.  When the original stream returns, winamp stops playing audio, but 
> the time keeps going up.  The kbps keeps going up too until I stop it. 
> stopping and restarting connects to the original source stream just fine.
> 
> So what's the matter with the 128 mp3 stream?  Why is it behaving 
> differently than all the other streams I have?

There's nothing specific to bitrates with regard to fallback and
override, so the fact that it's 128 is not directly related.

Does the fallback stream have the same audio format and settings eg same
samplerate, channels, and of course mp3. 

Does this problem always occur, or is it intermittent ?

karl.




From karl at xiph.org  Wed Dec 22 23:43:03 2004
From: karl at xiph.org (Karl Heyes)
Date: 22 Dec 2004 23:43:03 +0000
Subject: [Icecast] Encoders
In-Reply-To: <004401c4e87f$8fb28af0$0202a8c0@heerema.local>
References: <004401c4e87f$8fb28af0$0202a8c0@heerema.local>
Message-ID: <1103758982.9035.3897.camel@bogus.hackers.club>

On Wed, 2004-12-22 at 23:39, Dennis Heerema wrote:
> Hi There,
> 
> The discussion about speex triggered the following question:
> 
> Is there a way to use other encoders, to stream with icecast / oddcast.
> 
> Is there an format of witch the encoder shoul be standarized to (ACM or
> something like that), if so would it be possible to use open license
> encoders and commercail encoders with this. like FHG mp3, mp3pro, speex and
> so on.

If the stream format allows for passing the data straight through then
icecast will send it through to connected clients. The likes of mp3, aac
and nsv do exactly that.

The main thing you want to do for streaming to icecast is sending the
HTTP headers (like mountpoint and auth) to connect with beforehand,
libshout can handle that.

karl.




From mike at altrion.org  Wed Dec 22 23:47:19 2004
From: mike at altrion.org (Mike Whitaker)
Date: Wed, 22 Dec 2004 23:47:19 +0000
Subject: [Icecast] fallback override failing for 128 mbps mp3 stream
In-Reply-To: <1103758622.9035.3885.camel@bogus.hackers.club>
References: <41CA0029.9070806@ncsu.edu>
	<1103758622.9035.3885.camel@bogus.hackers.club>
Message-ID: <D159C3DE-5473-11D9-AAA6-0030658F78FC@altrion.org>

On 22 Dec 2004, at 23:37, Karl Heyes wrote:

> On Wed, 2004-12-22 at 23:15, Joel Ebel wrote:
>
>> When the source disappears, the fallback stream begins playing just
>> fine.
> There's nothing specific to bitrates with regard to fallback and
> override, so the fact that it's 128 is not directly related.

I have just had a Road to Damascus moment.

Or rather, a 'you pillock, Mike, why didn't you R all TFM and notice 
that WEEKS ago?' moment.

Fallback streams rock utterly. That is all.

:)



From geoff at hitsandpieces.net  Thu Dec 23 00:15:21 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Thu, 23 Dec 2004 10:15:21 +1000
Subject: [Icecast] Low-bitrate audio encode/stream application
In-Reply-To: <BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>
References: <BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>
Message-ID: <Pine.LNX.4.61.0412231014370.25093@data.home>

Hi:

Just curious, do we have any/many speex-enabled source clients and players?

Geoff.


-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From mike at altrion.org  Thu Dec 23 14:06:35 2004
From: mike at altrion.org (Mike Whitaker)
Date: Thu, 23 Dec 2004 14:06:35 +0000
Subject: [Icecast] Password protecting relay'ed mountpoints
Message-ID: <DB163DC3-54EB-11D9-AAA6-0030658F78FC@altrion.org>

Is it possible to have a <relay> section relaying from another 
(private) server, and then a <mount> section for the relay mountpoint 
that causes it to be password protected?



From karl at xiph.org  Thu Dec 23 15:30:28 2004
From: karl at xiph.org (Karl Heyes)
Date: 23 Dec 2004 15:30:28 +0000
Subject: [Icecast] Password protecting relay'ed mountpoints
In-Reply-To: <DB163DC3-54EB-11D9-AAA6-0030658F78FC@altrion.org>
References: <DB163DC3-54EB-11D9-AAA6-0030658F78FC@altrion.org>
Message-ID: <1103815827.9035.4899.camel@bogus.hackers.club>

On Thu, 2004-12-23 at 14:06, Mike Whitaker wrote:
> Is it possible to have a <relay> section relaying from another 
> (private) server, and then a <mount> section for the relay mountpoint 
> that causes it to be password protected?

yes, the <mount> options apply to source clients or relays and it is the
<mount> that states any authentication mechanism.

karl.




From guym at arizona.edu  Thu Dec 23 18:22:44 2004
From: guym at arizona.edu (Guy McArthur)
Date: Thu, 23 Dec 2004 11:22:44 -0700
Subject: [Icecast] mp3 checking
Message-ID: <41CB0CF4.4040600@arizona.edu>

Apologies if this is off topic, but could anyone recommend a utility for 
checking/repairing mp3's?

I'd like to be able to
* convert id3v1 tags to v2 (or vice versa)
* make sure the filename fits in fat32 restrictions
* be automatable (plugged into ices.p[m|y] for dynamic playlists)

Mp3check is pretty good, but doesn't do those first two items (perhaps 
it could in conjunction with other scripts).


From umar at natrix.wcrb.com  Thu Dec 23 18:11:22 2004
From: umar at natrix.wcrb.com (Rob Landry)
Date: Thu, 23 Dec 2004 13:11:22 -0500 (EST)
Subject: [Icecast] Icecast 2.2.0 and Ices2: no audio
Message-ID: <20041223125202.C32217@natrix.wcrb.com>

Folks:

I'm trying to set up a streaming server under Fedora Core 2 using Icecast
2.2.0. Everything compiles; everything runs. There are no indications of a
problem in any of the log files.

When I look at http://192.168.0.128:8000/status.xsl, everything looks ok.
But when I click on "Click to listen", it brings up xmms, but there's no
indication of audio, and xmms shows a bit rate of 1 kbps.

This is a machine that formerly ran icecast 1.3 and liveice under OpenBSD
2.8, so I know the hardware is OK.

What gives?


Rob Landry
umar at wcrb.com


Here's my ices.xml:

<?xml version="1.0"?>
<ices>
    <background>0</background>
    <logpath>/var/log/ices</logpath>
    <logfile>ices.log</logfile>
    <loglevel>4</loglevel>
    <consolelog>0</consolelog>
    <pidfile>/var/run/ices.pid</pidfile>

    <stream>
        <metadata>
            <name>Test Stream</name>
            <genre>music</genre>
            <description>A test stream</description>
            <url>http://www.mydomain.com</url>
        </metadata>

        <input>
            <module>oss</module>
            <param name="rate">44100</param>
            <param name="channels">2</param>
            <param name="device">/dev/dsp</param>
            <param name="metadata">0</param>
            <param name="metadatafilename">live</param>
        </input>

        <instance>
            <hostname>192.168.0.128</hostname>
            <port>8000</port>
            <password>12345678</password>
            <mount>/highband.ogg</mount>
            <yp>0</yp>
            <reconnectdelay>2</reconnectdelay>
            <reconnectattempts>5</reconnectattempts>
            <maxqueuelength>80</maxqueuelength>

            <encode>
                <quality>2</quality>
                <nominal-bitrate>96000</nominal-bitrate>
                <samplerate>44100</samplerate>
                <channels>2</channels>
            </encode>
        </instance>

        <instance>
            <hostname>192.168.0.128</hostname>
            <port>8000</port>
            <password>12345678</password>
            <mount>/midband.ogg</mount>
            <yp>0</yp>
            <reconnectdelay>2</reconnectdelay>
            <reconnectattempts>5</reconnectattempts>
            <maxqueuelength>80</maxqueuelength>

            <downmix>1</downmix>

            <resample>
                <in-rate>44100</in-rate>
                <out-rate>22050</out-rate>
            </resample>

            <encode>
                <nominal-bitrate>32000</nominal-bitrate>
                <samplerate>22050</samplerate>
                <channels>2</channels>
                <quality>1</quality>
            </encode>
        </instance>

        <instance>
            <hostname>192.168.0.128</hostname>
            <port>8000</port>
            <password>12345678</password>
            <mount>/lowband.ogg</mount>
            <yp>0</yp>
            <reconnectdelay>2</reconnectdelay>
            <reconnectattempts>5</reconnectattempts>
            <maxqueuelength>80</maxqueuelength>

            <downmix>1</downmix>

            <resample>
                <in-rate>44100</in-rate>
                <out-rate>11000</out-rate>
            </resample>

            <encode>
                <nominal-bitrate>16000</nominal-bitrate>
                <samplerate>11000</samplerate>
                <channels>1</channels>
                <quality>-1</quality>
            </encode>
        </instance>

    </stream>
</ices>


Here's my icecast.xml:


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

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

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

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

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

    <!-- You can use these two if you only want a single listener -->
    <!--<port>8000</port> -->
    <!--<bind-address>127.0.0.1</bind-address>-->

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

    <!--<master-server>127.0.0.1</master-server>-->
    <!--<master-server-port>8001</master-server-port>-->
    <!--<master-update-interval>120</master-update-interval>-->
    <!--<master-password>12345678</master-password>-->
    <!--
    <relay>
        <server>127.0.0.1</server>
        <port>8001</port>
        <mount>/example.ogg</mount>
        <local-mount>/different.ogg</local-mount>

        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>
    -->

    <!-- Only define a <mount> section if you want to use advanced options,
         like alternative usernames or passwords
    <mount>
        <mount-name>/example-complex.ogg</mount-name>

        <username>othersource</username>
        <password>12345678</password>

        <max-listeners>1</max-listeners>
        <dump-file>/tmp/dump-example1.ogg</dump-file>
        <burst-size>65536</burst-size>
        <fallback-mount>/example2.ogg</fallback-mount>
        <fallback-override>1</fallback-override>
        <hidden>1</hidden>
        <no-yp>1</no-yp>
        <authentication type="htpasswd">
                <option name="filename" value="myauth"/>
                <option name="allow_duplicate_users" value="0"/>
        </authentication>
    </mount>
    -->

    <fileserve>1</fileserve>

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

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

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

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

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <!-- <playlistlog>playlist.log</playlistlog> -->
      	<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
    </logging>

    <security>
        <chroot>0</chroot>
        <changeowner>
            <user>wcrb</user>
            <group>wcrb</group>
        </changeowner>
    </security>
</icecast>


From dm8tbr at afthd.tu-darmstadt.de  Thu Dec 23 22:59:31 2004
From: dm8tbr at afthd.tu-darmstadt.de (=?ISO-8859-15?Q?=22Thomas_B=2E_R=FCcker=22?=)
Date: Thu, 23 Dec 2004 23:59:31 +0100
Subject: [Icecast] Low-bitrate audio encode/stream application
In-Reply-To: <BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>
References: <BAY101-F3070BD977DD912461D1F1796A40@phx.gbl>
Message-ID: <41CB4DD3.6020602@afthd.tu-darmstadt.de>

Hi David,

trying to put pieces together...
judging by your email-adress you must be an radio amateur.
lets try an "educated guess" ;)

hope you're not going to try running digimodes through that... ;)

Short wave audio should be fine. I use darkice myself for exactly that 
purpose: remote RX at dl0td while travelling around europe.

One thing you should remember is: there is a considerable delay you wont 
be able to reduce below a minimum (depending on network and client 
software). This makes tuning bit harder on ssb.

Oh before i forget: there is a mediaplayer capable of streaming mp3 and 
ogg/vorbis for WinCE (HPC/PPC). I've been using it for quite some time 
before i switched towards embedded linux. It is a bit tricky to get it 
running (you have to prepare a special playlist file containing the 
stream adress in a weird char encoding)
Hopefully this is fixed by now. would make it more useable. ;)
you should be able to find it either at corecodec.com or while looking 
for pocket-divx (its an descendant of the abandoned pocket-divx 
sourcecode).

bitrates can be pushed quite low while using ogg/vorbis. quality -1 at 
22kHz mono should already give you around 20kbit or so with drops to 
nearly zero when there is very low noise-level and no signal. A downside 
could be increased time-shift due to buffers filling up slowly.

vy 73 es merry x-mas es happy nw yr de Thomas, dm8tbr



From karl at xiph.org  Fri Dec 24 01:57:42 2004
From: karl at xiph.org (Karl Heyes)
Date: 24 Dec 2004 01:57:42 +0000
Subject: [Icecast] Icecast 2.2.0 and Ices2: no audio
In-Reply-To: <20041223125202.C32217@natrix.wcrb.com>
References: <20041223125202.C32217@natrix.wcrb.com>
Message-ID: <1103853461.9035.5568.camel@bogus.hackers.club>

On Thu, 2004-12-23 at 18:11, Rob Landry wrote:
...
> When I look at http://192.168.0.128:8000/status.xsl, everything looks ok.
> But when I click on "Click to listen", it brings up xmms, but there's no
> indication of audio, and xmms shows a bit rate of 1 kbps.
> 
> This is a machine that formerly ran icecast 1.3 and liveice under OpenBSD
> 2.8, so I know the hardware is OK.

what are you capturing, probably silence based on those figures. check
your mixer settings

> Here's my ices.xml:
...

>         <instance>
...
>             <downmix>1</downmix>
> 
>             <resample>
>                 <in-rate>44100</in-rate>
>                 <out-rate>22050</out-rate>
>             </resample>
> 
>             <encode>
>                 <nominal-bitrate>32000</nominal-bitrate>
>                 <samplerate>22050</samplerate>
>                 <channels>2</channels>
>                 <quality>1</quality>
>             </encode>
>         </instance>

If you enable downmix then encode channels has to be 1

karl.




From mike at altrion.org  Fri Dec 24 11:54:56 2004
From: mike at altrion.org (Mike Whitaker)
Date: Fri, 24 Dec 2004 11:54:56 +0000
Subject: [Icecast] Fallback streams
Message-ID: <A1266476-55A2-11D9-AAA6-0030658F78FC@altrion.org>

Is there any way from the web interface of seeing how fallback streams 
are set up? (I need to be able to get my idiot audio producers to check 
that a config change has 'taken').



From karl at xiph.org  Fri Dec 24 12:10:26 2004
From: karl at xiph.org (Karl Heyes)
Date: 24 Dec 2004 12:10:26 +0000
Subject: [Icecast] Fallback streams
In-Reply-To: <A1266476-55A2-11D9-AAA6-0030658F78FC@altrion.org>
References: <A1266476-55A2-11D9-AAA6-0030658F78FC@altrion.org>
Message-ID: <1103890225.25463.7.camel@bogus.hackers.club>

On Fri, 2004-12-24 at 11:54, Mike Whitaker wrote:
> Is there any way from the web interface of seeing how fallback streams 
> are set up? (I need to be able to get my idiot audio producers to check 
> that a config change has 'taken').

The fallback mount is not currently put onto the stats so you won't be
able to see then. I don't see any reason why it cannot be, but if you
can report it on trac.xiph.org then it shouldn't get missed.

karl.




From altufaltu at mail.com  Sat Dec 25 09:12:44 2004
From: altufaltu at mail.com (Altu Faltu)
Date: Sat, 25 Dec 2004 04:12:44 -0500
Subject: [Icecast] Win32 project files for libshout
Message-ID: <20041225091244.E80E11CE302@ws1-6.us4.outblaze.com>

Hi,

The VC++ project workspace for ezstream refers to libshout project, which is not supplied with ezstream or libshout source distribution.

  Project: "libshout"="..\..\libshout-2.0\win32\libshout.dsp" - Package Owner=<4>

Where do I get those files? Please help!

- Altu Faltu
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From wb0gaz at hotmail.com  Sat Dec 25 17:22:17 2004
From: wb0gaz at hotmail.com (david feldman)
Date: Sat, 25 Dec 2004 10:22:17 -0700
Subject: [Icecast] Low-bitrate audio encode/stream application
In-Reply-To: <20041224200003.80C211CA97@westfish.xiph.org>
Message-ID: <BAY101-F245CE99C53935B94628CBD96A70@phx.gbl>

Hello Thomas,

You are correct - the application is basically for secure remote access to 
ham CW (morse code) station. I believe the solution will be based on low bit 
rate MP3 streaming for receiver side (MP3 allows use with existing CODEC in 
client side, which could include Win CE or Linux palmtop type form factor, 
and the audio source would just be "voice grade" material on a mono, not 
stereo, connection). I am investigating options to build small 
morse-to-IRDA/Serial encoder that would accept key/paddle input, encode and 
timestamp into serial message format, and be transmitted back to server 
using the client machine's serial/IRDA port and then through telnet or 
similar text-oriented session to the server. This seems to hold promise in 
that it would require very little or no client side software development 
(I'm hoping to do this with a HP Jornada 720 windows CE client, which is 
about 5 years old, out of production, so other CODEC development seems very 
unlikely.)

Do you know if any books have been published that address icecast? It 
appears from reading traffic on this reflector that a single (mono) 22000 
bps encoding rate carried over a 32000 bps is feasible, and while this would 
be a bit much for dial-up serial access, it would be adequate for any 
broadband client connection.

73 Dave WB0GAZ wb0gaz at hotmail.com

>From: "Thomas B. R?cker" 	<dm8tbr at afthd.tu-darmstadt.de>
>Subject: Re: [Icecast] Low-bitrate audio encode/stream application
>To: david feldman <wb0gaz at hotmail.com>, icecast at xiph.org
>Message-ID: <41CB4DD3.6020602 at afthd.tu-darmstadt.de>
>Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>
>Hi David,
>
>trying to put pieces together...
>judging by your email-adress you must be an radio amateur.
>lets try an "educated guess" ;)
>
>hope you're not going to try running digimodes through that... ;)
>
>Short wave audio should be fine. I use darkice myself for exactly that
>purpose: remote RX at dl0td while travelling around europe.
>
>One thing you should remember is: there is a considerable delay you wont
>be able to reduce below a minimum (depending on network and client
>software). This makes tuning bit harder on ssb.
>
>Oh before i forget: there is a mediaplayer capable of streaming mp3 and
>ogg/vorbis for WinCE (HPC/PPC). I've been using it for quite some time
>before i switched towards embedded linux. It is a bit tricky to get it
>running (you have to prepare a special playlist file containing the
>stream adress in a weird char encoding)
>Hopefully this is fixed by now. would make it more useable. ;)
>you should be able to find it either at corecodec.com or while looking
>for pocket-divx (its an descendant of the abandoned pocket-divx
>sourcecode).
>
>bitrates can be pushed quite low while using ogg/vorbis. quality -1 at
>22kHz mono should already give you around 20kbit or so with drops to
>nearly zero when there is very low noise-level and no signal. A downside
>could be increased time-shift due to buffers filling up slowly.
>
>vy 73 es merry x-mas es happy nw yr de Thomas, dm8tbr




From altufaltu at mail.com  Sun Dec 26 11:50:03 2004
From: altufaltu at mail.com (Altu Faltu)
Date: Sun, 26 Dec 2004 17:20:03 +0530
Subject: [Icecast] ezstream without repeating playlist / file for Win32
Message-ID: <200412261150.iBQBo2QQ013197@dbdp30.itg.ti.com>

Hi,

Can somebody do me a favour?

I need a version of ezstream (for Win32) that does not repeat playlist / song. It can be done by removing following two lines from ezstream.c:

    printf("Connecting to %s...", pezConfig->URL);
    if (shout_open(shout) == SHOUTERR_SUCCESS) {
        printf("SUCCESS.\n");
-->     while (1) {
            if (!strrcmp(pezConfig->fileName, ".m3u")) {
                streamPlaylist(shout, pezConfig->fileName);
            }
            else {
                streamFile(shout, pezConfig->fileName);
            }
-->     }
    } else {
        printf("FAILED: %s\n", shout_get_error(shout));
    }

Please help! I can't compile ezstream since the source distribution doesn't include all required files!

Thanks.

- Altu Faltu




From oddsock at oddsock.org  Sun Dec 26 19:12:41 2004
From: oddsock at oddsock.org (oddsock at oddsock.org)
Date: Sun, 26 Dec 2004 14:12:41 -0500 (EST)
Subject: [Icecast] Win32 project files for libshout
Message-ID: <1105.65.118.118.130.1104088361.squirrel@65.118.118.130>

You need to get the SVN version of libshout to pick up the VC project
files.  We should really release a new version of libshout...but in the
meantime, I've added libshout to my snapshot script which produces nightly
snapshots of certain xiph modules, you can download them here :


From oddsock at oddsock.org  Sun Dec 26 19:18:05 2004
From: oddsock at oddsock.org (oddsock at oddsock.org)
Date: Sun, 26 Dec 2004 14:18:05 -0500 (EST)
Subject: [Icecast] Win32 project files for libshout
In-Reply-To: <1105.65.118.118.130.1104088361.squirrel@65.118.118.130>
References: <1105.65.118.118.130.1104088361.squirrel@65.118.118.130>
Message-ID: <1127.65.118.118.130.1104088685.squirrel@65.118.118.130>

> You need to get the SVN version of libshout to pick up the VC project
> files.  We should really release a new version of libshout...but in the
> meantime, I've added libshout to my snapshot script which produces nightly
> snapshots of certain xiph modules, you can download them here :
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
http://www.oddsock.org/xiph_snapshots/

sorry, forgot the actual link :)

oddsock


From altufaltu at mail.com  Mon Dec 27 06:55:35 2004
From: altufaltu at mail.com (Altu Faltu)
Date: Mon, 27 Dec 2004 01:55:35 -0500
Subject: [Icecast] Re: Win32 project files for libshout
Message-ID: <20041227065535.E92281F50B1@ws1-2.us4.outblaze.com>

Hi,

Thanks for provoding the snapshot.

Now it refers to following folders which are not included in the package!
  ../../pthreads
  ../../oggvorbis-win32sdk-1.0.1/include

1) Can I use http://svn.xiph.org/trunk/ogg insted of oggvorbis-win32sdk-1.0.1?
2) Where do I get pthreads?
3) Is svn for libshout available for public read access? Where?

- Altu Faltu

----- Original Message -----
> > You need to get the SVN version of libshout to pick up the VC project
> > files.  We should really release a new version of libshout...but in the
> > meantime, I've added libshout to my snapshot script which produces nightly
> > snapshots of certain xiph modules, you can download them here :
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> >
> http://www.oddsock.org/xiph_snapshots/
> 
> sorry, forgot the actual link :)
> 
> oddsock

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From geoff at hitsandpieces.net  Mon Dec 27 07:02:30 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Mon, 27 Dec 2004 17:02:30 +1000
Subject: [Icecast] Re: Win32 project files for libshout
In-Reply-To: <20041227065535.E92281F50B1@ws1-2.us4.outblaze.com>
References: <20041227065535.E92281F50B1@ws1-2.us4.outblaze.com>
Message-ID: <Pine.LNX.4.61.0412271700030.6895@data.home>

Altu Faltu wrote:

> 3) Is svn for libshout available for public read access? Where?

svn.xiph.org/icecast/trunk/libshout/

You can browse the tree using a web browser, there's a lot in the xiph 
tree.

Geoff.



-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From m.musnikas at lrtc.lt  Mon Dec 27 14:51:49 2004
From: m.musnikas at lrtc.lt (Mindaugas Musnikas)
Date: Mon, 27 Dec 2004 16:51:49 +0200
Subject: [Icecast] AAC
Message-ID: <00f201c4ec23$98691310$d590a8c0@techmindaugas>


Hello all,

I would like to know what kind of AAC can stream icecast 2.2.0. Is it MPEG-2 AAC or MPEG-4 AAC? How much efficiency can be gained by using this kind of AAC compared to MP3?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041227/c7c14910/attachment.htm>

From karl at xiph.org  Mon Dec 27 15:07:26 2004
From: karl at xiph.org (Karl Heyes)
Date: 27 Dec 2004 15:07:26 +0000
Subject: [Icecast] AAC
In-Reply-To: <00f201c4ec23$98691310$d590a8c0@techmindaugas>
References: <00f201c4ec23$98691310$d590a8c0@techmindaugas>
Message-ID: <1104160046.26896.57.camel@bogus.hackers.club>

On Mon, 2004-12-27 at 14:51, Mindaugas Musnikas wrote:
>  
> Hello all,
>  
> I would like to know what kind of AAC can stream icecast 2.2.0. Is it
> MPEG-2 AAC or MPEG-4 AAC? How much efficiency can be gained by using
> this kind of AAC compared to MP3?
> 
> ______________________________________________________________________
The AAC format is passed through as-is, so you'll find that all variants
of AAC go through.

As for efficiency, it's understood to be better compression than mp3,
whether it suits your needs is another matter.

karl.




From oddsock at oddsock.org  Mon Dec 27 16:34:53 2004
From: oddsock at oddsock.org (oddsock at oddsock.org)
Date: Mon, 27 Dec 2004 11:34:53 -0500 (EST)
Subject: [Icecast] Re: Win32 project files for libshout
In-Reply-To: <20041227065535.E92281F50B1@ws1-2.us4.outblaze.com>
References: <20041227065535.E92281F50B1@ws1-2.us4.outblaze.com>
Message-ID: <1133.69.95.98.41.1104165293.squirrel@69.95.98.41>

> Hi,
>
> Thanks for provoding the snapshot.
>
> Now it refers to following folders which are not included in the package!
>   ../../pthreads
>   ../../oggvorbis-win32sdk-1.0.1/include
>
of course they are not included...They are 3rd party libraries.

> 1) Can I use http://svn.xiph.org/trunk/ogg insted of
> oggvorbis-win32sdk-1.0.1?
sure, if you want you can.  You will need vorbis as well too.

> 2) Where do I get pthreads?
http://sources.redhat.com/pthreads-win32/
although you really could have found it with a simple google search.

p.s. No need to CC me as well as email it to the list....emailing to the
list will suffice.


From oddsock at oddsock.org  Mon Dec 27 16:46:07 2004
From: oddsock at oddsock.org (oddsock at oddsock.org)
Date: Mon, 27 Dec 2004 11:46:07 -0500 (EST)
Subject: [Icecast] AAC
In-Reply-To: <00f201c4ec23$98691310$d590a8c0@techmindaugas>
References: <00f201c4ec23$98691310$d590a8c0@techmindaugas>
Message-ID: <1192.69.95.98.41.1104165967.squirrel@69.95.98.41>

>
> Hello all,
>
> I would like to know what kind of AAC can stream icecast 2.2.0. Is it
> MPEG-2 AAC or MPEG-4 AAC? How much efficiency can be gained by using this
> kind of AAC compared to
> MP3?_______________________________________________
you might want to direct your efficiency questions to
http://www.audiocoding.com.  We are not really AAC experts here.  As far
as icecast goes, it should stream whatever type of AAC you throw at it. 
Oddcast uses MPEG2 AAC (via libfaac), I'm not sure what the other source
clients that work with Icecast use.  There is no real limitation of the
formats you can stream with icecast now.  Most of the MPEG-type formats
are supportable now, you just need to get a source client and listening
client that supports it.  Any new formats encapsulated with ogg need a bit
of work (i.e. speex) but, nothing too difficult.


oddsock


From altufaltu at mail.com  Mon Dec 27 17:14:37 2004
From: altufaltu at mail.com (Altu Faltu)
Date: Mon, 27 Dec 2004 12:14:37 -0500
Subject: [Icecast] Re: Win32 project files for libshout
Message-ID: <20041227171438.077471F50B2@ws1-2.us4.outblaze.com>

Hi,

Thanks for the links. I downloaded oggvorbis-win32sdk, phreads, libxml2 and iconv.

Now I get following errors while linking ezstream:

 libshout.lib(shout.obj) : error LNK2001: unresolved external symbol _vsnprintf
 libshout.lib(shout.obj) : error LNK2001: unresolved external symbol _va_copy
 libshout.lib(ogg.obj) : error LNK2001: unresolved external symbol __shout_open_vorbis

Any pointers?

- Altu Faltu


----- Original Message -----
> > 1) Can I use http://svn.xiph.org/trunk/ogg insted of
> > oggvorbis-win32sdk-1.0.1?
> sure, if you want you can.  You will need vorbis as well too.
> 
> > 2) Where do I get pthreads?
> http://sources.redhat.com/pthreads-win32/
> although you really could have found it with a simple google search.

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From Dennis at Heerema.net  Mon Dec 27 22:02:18 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Mon, 27 Dec 2004 23:02:18 +0100
Subject: [Icecast] How do I group icecast servers
Message-ID: <41D0866A.6040800@Heerema.net>

Hi There,

Is there a way to group icecast servers, so they are found as one 
announcement on the YP directory lists and al servers will give all 
servers in there m3u.

regards,

Dennis Heerema



From karl at xiph.org  Mon Dec 27 22:07:16 2004
From: karl at xiph.org (Karl Heyes)
Date: 27 Dec 2004 22:07:16 +0000
Subject: [Icecast] How do I group icecast servers
In-Reply-To: <41D0866A.6040800@Heerema.net>
References: <41D0866A.6040800@Heerema.net>
Message-ID: <1104185235.26896.66.camel@bogus.hackers.club>

On Mon, 2004-12-27 at 22:02, Dennis Heerema wrote:
> Hi There,
> 
> Is there a way to group icecast servers, so they are found as one 
> announcement on the YP directory lists and al servers will give all 
> servers in there m3u.

Look at the use of cluster password in 2.2

karl.




From Dennis at Heerema.net  Tue Dec 28 00:02:55 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Tue, 28 Dec 2004 01:02:55 +0100
Subject: [Icecast] master-slave  metadata missing
Message-ID: <001e01c4ec70$a1ede030$0202a8c0@heerema.local>

Hi there,

Don't know if it's already noticed.

But when defining an master - slave configuration, not all mata data is relayed to the slave server.

I'm missing the stream discription, sampling frequentie and stereo /  mono information at the salve server side in the YP directory listing.

See copy op yp directory below.

Regards,

Dennis Heerma

      Listen Streams Genre Audio Info 
     
     
     
     
     DOOSFM  
      Cluster 
      Ogg Vorbis Test stream OGG Vorbis -2 quality
      Now playing on /live.ogg :  XTM present ANNIA - Fly on the Wings of Love various Quality -2.0
      32000Hz Stereo 
     
     DOOSFM  
      Cluster 
      Ogg Vorbis 
      Now playing on /live.ogg :  XTM present ANNIA - Fly on the Wings of Love various Quality -2.0
     
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041228/fad74b42/attachment.htm>

From geoff at hitsandpieces.net  Tue Dec 28 04:42:57 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Tue, 28 Dec 2004 14:42:57 +1000
Subject: [Icecast] How do I group icecast servers
In-Reply-To: <41D0866A.6040800@Heerema.net>
References: <41D0866A.6040800@Heerema.net>
Message-ID: <Pine.LNX.4.61.0412281441411.6895@data.home>

Dennis Heerema wrote:

> Is there a way to group icecast servers, so they are found as one 
> announcement on the YP directory lists and al servers will give all servers 
> in there m3u.

As far as the M3U is concerned, you can always role your own rather than 
use the one supplied by the server.

Geoff.



From oddsock at oddsock.org  Tue Dec 28 05:24:20 2004
From: oddsock at oddsock.org (oddsock at oddsock.org)
Date: Tue, 28 Dec 2004 00:24:20 -0500 (EST)
Subject: [Icecast] How do I group icecast servers
In-Reply-To: <41D0866A.6040800@Heerema.net>
References: <41D0866A.6040800@Heerema.net>
Message-ID: <1648.69.95.98.9.1104211460.squirrel@69.95.98.9>

> Hi There,
>
> Is there a way to group icecast servers, so they are found as one
> announcement on the YP directory lists and al servers will give all
> servers in there m3u.
>
> regards,
>
> Dennis Heerema
>
There are two different ways to group servers together on the YP.

The first is referred to as "server grouping".  Streams that have the same
Server Name and are listed from the same IP are "grouped" together into
one logical directory listing.  An example of this can be seen here :
http://dir.xiph.org/index.php?sgenre=&stype=&search=Wicked

In this grouping, there are many streams listed, but all are grouped into
a single logical listing.  Note that each stream can have a separate
Server description (Server description is separate from Server name).

The second type of grouping is what's called "clustering".  Clusters are
grouped together in a single actual listing and are meant mostly for
listing streams and their relays together in a single physical listing. 
>From your question, it seems that this is the type you are interested in. 
An example of this can be seen here :
http://dir.xiph.org/index.php?sgenre=&stype=&search=Ropin

In this case, there is only a single listing, but when a listener clicks
on the listen link, they are served an m3u containing all clustered
servers.

In order to "cluster" servers together, you MUST use the cluster password
feature of Icecast 2.2.  This is a mount specific setting and the docs
should help you out in figuring out where it goes.  All streams with the
same cluster password and server name will be clustered together into a
single listing.  Note that clusters can span across multiple listing IPs
(as most relays do).

hopefully that clears it up a bit...

oddsock


From Dennis at Heerema.net  Tue Dec 28 09:29:30 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Tue, 28 Dec 2004 10:29:30 +0100
Subject: [Icecast] How do I group icecast servers
References: <41D0866A.6040800@Heerema.net>
	<1648.69.95.98.9.1104211460.squirrel@69.95.98.9>
Message-ID: <001401c4ecbf$c8847890$0202a8c0@heerema.local>

Hi oddsock and others,

Everything is clear about that, but where and how do i specify the
servername, cannot find it in the docs and a threath about it on the archive
(found via google) is not there anymore.

Thanks,

Dennis


----- Original Message ----- 
From: <oddsock at oddsock.org>
To: <icecast at xiph.org>
Sent: Tuesday, December 28, 2004 6:24 AM
Subject: Re: [Icecast] How do I group icecast servers


> > Hi There,
> >
> > Is there a way to group icecast servers, so they are found as one
> > announcement on the YP directory lists and al servers will give all
> > servers in there m3u.
> >
> > regards,
> >
> > Dennis Heerema
> >
> There are two different ways to group servers together on the YP.
>
> The first is referred to as "server grouping".  Streams that have the same
> Server Name and are listed from the same IP are "grouped" together into
> one logical directory listing.  An example of this can be seen here :
> http://dir.xiph.org/index.php?sgenre=&stype=&search=Wicked
>
> In this grouping, there are many streams listed, but all are grouped into
> a single logical listing.  Note that each stream can have a separate
> Server description (Server description is separate from Server name).
>
> The second type of grouping is what's called "clustering".  Clusters are
> grouped together in a single actual listing and are meant mostly for
> listing streams and their relays together in a single physical listing.
> >From your question, it seems that this is the type you are interested in.
> An example of this can be seen here :
> http://dir.xiph.org/index.php?sgenre=&stype=&search=Ropin
>
> In this case, there is only a single listing, but when a listener clicks
> on the listen link, they are served an m3u containing all clustered
> servers.
>
> In order to "cluster" servers together, you MUST use the cluster password
> feature of Icecast 2.2.  This is a mount specific setting and the docs
> should help you out in figuring out where it goes.  All streams with the
> same cluster password and server name will be clustered together into a
> single listing.  Note that clusters can span across multiple listing IPs
> (as most relays do).
>
> hopefully that clears it up a bit...
>
> oddsock
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>




From Dennis at Heerema.net  Tue Dec 28 09:33:44 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Tue, 28 Dec 2004 10:33:44 +0100
Subject: [Icecast] How do I group icecast servers
References: <41D0866A.6040800@Heerema.net><1648.69.95.98.9.1104211460.squirrel@69.95.98.9>
	<001401c4ecbf$c8847890$0202a8c0@heerema.local>
Message-ID: <000901c4ecc0$5f88e6e0$0202a8c0@heerema.local>

I'm getting as far as this now

http://www.oddsock.org/icecast2yp/index.php?sgenre=&search=doosfm

Both servers are clustered, got in the m3u on both servers, both listen
urls. But they are still listed as two seperate streams in the yp dir

Regards,

Dennis


----- Original Message ----- 
From: "Dennis Heerema" <Dennis at Heerema.net>
To: <icecast at xiph.org>
Sent: Tuesday, December 28, 2004 10:29 AM
Subject: Re: [Icecast] How do I group icecast servers


> Hi oddsock and others,
>
> Everything is clear about that, but where and how do i specify the
> servername, cannot find it in the docs and a threath about it on the
archive
> (found via google) is not there anymore.
>
> Thanks,
>
> Dennis
>
>
> ----- Original Message ----- 
> From: <oddsock at oddsock.org>
> To: <icecast at xiph.org>
> Sent: Tuesday, December 28, 2004 6:24 AM
> Subject: Re: [Icecast] How do I group icecast servers
>
>
> > > Hi There,
> > >
> > > Is there a way to group icecast servers, so they are found as one
> > > announcement on the YP directory lists and al servers will give all
> > > servers in there m3u.
> > >
> > > regards,
> > >
> > > Dennis Heerema
> > >
> > There are two different ways to group servers together on the YP.
> >
> > The first is referred to as "server grouping".  Streams that have the
same
> > Server Name and are listed from the same IP are "grouped" together into
> > one logical directory listing.  An example of this can be seen here :
> > http://dir.xiph.org/index.php?sgenre=&stype=&search=Wicked
> >
> > In this grouping, there are many streams listed, but all are grouped
into
> > a single logical listing.  Note that each stream can have a separate
> > Server description (Server description is separate from Server name).
> >
> > The second type of grouping is what's called "clustering".  Clusters are
> > grouped together in a single actual listing and are meant mostly for
> > listing streams and their relays together in a single physical listing.
> > >From your question, it seems that this is the type you are interested
in.
> > An example of this can be seen here :
> > http://dir.xiph.org/index.php?sgenre=&stype=&search=Ropin
> >
> > In this case, there is only a single listing, but when a listener clicks
> > on the listen link, they are served an m3u containing all clustered
> > servers.
> >
> > In order to "cluster" servers together, you MUST use the cluster
password
> > feature of Icecast 2.2.  This is a mount specific setting and the docs
> > should help you out in figuring out where it goes.  All streams with the
> > same cluster password and server name will be clustered together into a
> > single listing.  Note that clusters can span across multiple listing IPs
> > (as most relays do).
> >
> > hopefully that clears it up a bit...
> >
> > oddsock
> > _______________________________________________
> > 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 altufaltu at mail.com  Tue Dec 28 13:24:46 2004
From: altufaltu at mail.com (Altu Faltu)
Date: Tue, 28 Dec 2004 08:24:46 -0500
Subject: [Icecast] Bug: ezstream doesn't recover from socket error
Message-ID: <20041228132446.277B11F50B1@ws1-2.us4.outblaze.com>

Hi,

If icecast is turned off or if admin kills source from web interface, ezstream keeps showing following error message and never recovers or terminates:

  DEBUG: Send error: Socket error

* Seen on Win32.

- Altu Faltu
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From altufaltu at mail.com  Tue Dec 28 13:53:02 2004
From: altufaltu at mail.com (Altu Faltu)
Date: Tue, 28 Dec 2004 08:53:02 -0500
Subject: [Icecast] svn.xiph.org is down?
Message-ID: <20041228135302.8F9D41F50B1@ws1-2.us4.outblaze.com>

I'm unable to access svn.xiph.org!

  svn: PROPFIND of '/icecast/trunk/libshout': 500 Server Error (http://svn.xiph.org)

Something fishey?

- Altu Faltu
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



From giles at xiph.org  Tue Dec 28 14:22:04 2004
From: giles at xiph.org (Ralph Giles)
Date: Tue, 28 Dec 2004 06:22:04 -0800
Subject: [Icecast] svn.xiph.org is down?
In-Reply-To: <20041228135302.8F9D41F50B1@ws1-2.us4.outblaze.com>
References: <20041228135302.8F9D41F50B1@ws1-2.us4.outblaze.com>
Message-ID: <20041228142204.GB17346@ghostscript.com>

On Tue, Dec 28, 2004 at 08:53:02AM -0500, Altu Faltu wrote:

> I'm unable to access svn.xiph.org!
> Something fishey?

Rather unfishy, I'd say. :)

Fixed now,
 -r


From hello at ianbell.com  Tue Dec 28 18:47:52 2004
From: hello at ianbell.com (Ian Andrew Bell)
Date: Tue, 28 Dec 2004 10:47:52 -0800
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <Pine.LNX.4.61.0412182220570.20900@data.home>
References: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>
	<20041218010019.63338.qmail@web54509.mail.yahoo.com>
	<20041218011135.GD32378@ghostscript.com>
	<Pine.LNX.4.61.0412182220570.20900@data.home>
Message-ID: <FAFCC7DC-5900-11D9-9E22-000A95B3B8D6@ianbell.com>

If propagation of Ogg Vorbis is the (or a)  goal of Icecast then 
probably the best strategy is to build an embedded Ogg Flash Player of 
some sort, so that people unwittingly become Ogg users without lifting 
a finger, and broadcasters can start using it without fear that they'll 
lose listeners due to their protocol choice.  I've been streaming for 
more than 7 years now with Quicktime, Shoutcast, and most recently 
Icecast and it's been interesting to see how the technologies in the 
space have vied for dominance, ultimately ceding to MP3.

In 2000, Shoutcasting was difficult because nobody had MP3 players 
installed and it was a pain to download.  Microsoft changed this by 
including Windows Media Player and suddenly there was an embedded base 
of MP3 listeners out there looking for something to tune into.  Cue the 
demise of proprietary streaming protocols like RealPlayer (which 
previously was the norm) and Quicktime streaming (which still required 
users to get Quicktime, though it was pretty easy).  These two had 
previously been prominent because RealAudio had been prolific in 
embedding their player with browser downloads and OS installs, and 
because Apple/Quicktime had come up with millions of different reasons 
why you needed to install their plugin and so a large base had been 
grown over half a decade.  MP3 streaming broke out and away from the 
pack because A) it was free, B) MP3 as a standard was getting huge 
attention thanks to file sharing, and C) it was well supported by 
NullSoft from encoder to server to player.

Sure there are lots of Ogg players out there for you and me to install, 
but without some kind of stealth strategy Ogg is stuck with a 
chicken-and-egg problem.  Can't get the streamers if there are no 
listeners, can't get the listeners if there are no streamers.  The 
difference between now and 2000, when MP3 broke thru this wall, is that 
there are a lot more choices out there and streaming over IP is no 
longer quite as new and cool.  Being cooler, being technically better, 
is not enough.  Being free and open-source in itself doesn't cut it in 
the mass market.  MP3, these days, is "free enough" and easily 
available for use by the unwashed masses.

So... what would make me as a professional broadcaster seriously 
consider Ogg?  Two things:

ONE:

We use an embedded player at Pulverradio.com that's done in Flash.  For 
our part we just modified an off-the-shelf player for our station and 
the result is we receive very little email from folks having trouble 
connecting.  So ostensibly we could choose any protocol we liked, so 
long as there was a Flash Library to support it, since the listeners 
don't NEED to know the difference.

TWO:

I need to encode Ogg professionally.  We use hardware encoders from 
TELOS. I picked these because it was the most rock-solid solution that 
had AES inputs, and our production studios are all-digital.  
(http://www.audioactive.com/products/webcasting.html)  These use 
licensed Fraunhofer encoders and also have some nice de-essing and 
grunge reduction features that I am a fan of.  Convince guys like this 
to use Ogg, or develop a similar device which does both Ogg and MP3, 
and you've got a winner.

Like any effective salesman, when facing chicken-and-egg problems dead 
on (which I've had to do a number of times in my career) it's important 
to grease the skids so that there are no reasons for the listener, the 
producer, or the broadcaster to say No.  In the case of Ogg Vorbis it's 
simply not good enough to push the tools out there and wait for people 
to use them.

In any case I share your pain because I'm frustrated with MP3 streaming 
and would like to see Ogg Vorbis more widely used.

-Ian.


On 18-Dec-04, at 4:24 AM, Geoff Shang wrote:

> Ralph Giles wrote:
>
>> Of course. But that's not the whole story. Microsoft only
>> supports MP3 because so many people listen to mp3 radio
>> stations and files. And before Window Media Player played
>> MP3, everyone had winamp installed because the nearest
>> teenager (if I may) had installed it as a way to listen to
>> cool--or at least free--music.
>
> Very true.  And WMP had support for MP3 files before it properly 
> supported MP3 streaming.  Same with RealPLayer.  They added it because 
> there was overwhelming user demand for it.



From mike at altrion.org  Tue Dec 28 19:06:26 2004
From: mike at altrion.org (Mike Whitaker)
Date: Tue, 28 Dec 2004 19:06:26 +0000
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <FAFCC7DC-5900-11D9-9E22-000A95B3B8D6@ianbell.com>
References: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>
	<20041218010019.63338.qmail@web54509.mail.yahoo.com>
	<20041218011135.GD32378@ghostscript.com>
	<Pine.LNX.4.61.0412182220570.20900@data.home>
	<FAFCC7DC-5900-11D9-9E22-000A95B3B8D6@ianbell.com>
Message-ID: <92A61C39-5903-11D9-AAA6-0030658F78FC@altrion.org>

> So... what would make me as a professional broadcaster seriously 
> consider Ogg?  Two things:
>
> ONE:
>
> We use an embedded player at Pulverradio.com that's done in Flash.  
> For our part we just modified an off-the-shelf player for our station 
> and the result is we receive very little email from folks having 
> trouble connecting.  So ostensibly we could choose any protocol we 
> liked, so long as there was a Flash Library to support it, since the 
> listeners don't NEED to know the difference.

That, right there, would make us (The Cricket Site - 
http://www.the-cricket-site.com/) seriously consider switching away 
from MP3. At present, we really have no choice: we can't handle the 
support overhead for getting folks to work with new codecs. We'd really 
like to switch to OGG for quality issues (better encoding of speech) 
and because we could then hang ices2 off the back end of an Asterisk 
PBX for our commentators to dial into, and enable them to chat to each 
other and manage handovers cleaner than we do at present.

On which subject: what software is there other than MuSE out there that 
allows mixing of live audio with an Icecast stream? we're trying to 
figure out the best way of managing handovers from one studio+encoder 
to another.



From henk.vande.ridder at solcon.nl  Tue Dec 28 19:46:41 2004
From: henk.vande.ridder at solcon.nl (Henk van de Ridder)
Date: Tue, 28 Dec 2004 20:46:41 +0100
Subject: [Icecast] Aliassing Icecast 2.1 Admin console
Message-ID: <000b01c4ed15$f43f1ed0$ca29a8c0@hvdr>

Hello,

We are searching for a possibility of "aliassing without wasting bandwidth".
It is described in the following section which we found at
http://open4all.info/ossa/_Icecast_Streaming_Server.

# What happens is that when a listeners connects to your server and
# requests the /laika stream, then your icecast server will connect
# as a client to my machine, and then feed my stream to the listener.
# All subsequent requests for /laika will use the same feed (i.e only
# one connect will be made to my machine). Icecast will automagically
# shut the link from my machine down when no one is listening. I.e
# no bandwidth will be wasted.

In our situation we have al local icecast server and a remote one. The
remote one is hosted by an ISP with limited download amount. If I make a
relay connection fro the remote icecast server then it allways transports
the continuing stream. But I only want to have transport if someone is
listening and when nobody listens we don't want to waste the download
amount.

In an old manual of icecast (versie 1.3 ??) (at
www.skywayradio.com/tech/icecast) I 've read something about "relaying using
aliases". The settings are described via de admin-console.

First quesiton: It seems icecast2.1 does not have a admin-console. Is it
still there ? How can I reach it ?

Second question: Is there a way of setting the relay- or alias-configuration
is the way we want to have to limited the 'waste' of download amount.

With kind regards,
Henk vd Ridder






From giles at xiph.org  Tue Dec 28 20:36:29 2004
From: giles at xiph.org (Ralph Giles)
Date: Tue, 28 Dec 2004 12:36:29 -0800
Subject: [Icecast] Still the big Icecast problem!
In-Reply-To: <FAFCC7DC-5900-11D9-9E22-000A95B3B8D6@ianbell.com>
References: <000a01c4e498$c2d9ebc0$1401a8c0@workstation>
	<20041218010019.63338.qmail@web54509.mail.yahoo.com>
	<20041218011135.GD32378@ghostscript.com>
	<Pine.LNX.4.61.0412182220570.20900@data.home>
	<FAFCC7DC-5900-11D9-9E22-000A95B3B8D6@ianbell.com>
Message-ID: <20041228203629.GA14654@ghostscript.com>

On Tue, Dec 28, 2004 at 10:47:52AM -0800, Ian Andrew Bell wrote:

> If propagation of Ogg Vorbis is the (or a)  goal of Icecast then 
> probably the best strategy is to build an embedded Ogg Flash Player of 
> some sort, so that people unwittingly become Ogg users without lifting 
> a finger, and broadcasters can start using it without fear that they'll 
> lose listeners due to their protocol choice.  I've been streaming for 
> more than 7 years now with Quicktime, Shoutcast, and most recently 
> Icecast and it's been interesting to see how the technologies in the 
> space have vied for dominance, ultimately ceding to MP3.

Yes, of course. This is up to Macromedia; they're the ones distributing 
the flash plugins. Please tell them you want Ogg Vorbis support and why.
You might have better luck getting it is as part of Ogg Theora (video) 
support since they can use the quality lift rather more on that side.

There are java player applets, as has been mentioned.

> So... what would make me as a professional broadcaster seriously 
> consider Ogg?  Two things:

You've only mentioned quality. Are license fees not an issue for you?
 
When Vorbis was first released 4 years ago, we expected this to be the 
major thing driving adoption. The business case for internet webcast 
had such a fine margin that the MP3 royalties nearly killed it. Of 
course, in the US as least, the recording industry's punitive copyright 
royalties pretty much made up for the savings Vorbis offerred, so things
still went nowhere. I don't know what happened in other countries; maybe 
the whole idea was just a .com-era experiment no one else tried.

> In any case I share your pain because I'm frustrated with MP3 streaming 
> and would like to see Ogg Vorbis more widely used.

Well, do what you can. It takes a village to build Rome. :-)

 -r


From postfix at webgate.ro  Tue Dec 28 21:13:16 2004
From: postfix at webgate.ro (Alex)
Date: Tue, 28 Dec 2004 23:13:16 +0200
Subject: [Icecast] startup problem: how to start ices under regular user
	account
Message-ID: <41D1CC6C.8030402@webgate.ro>

Hello ices experts,

I am running icecast2 and ices2 which are working fine for me. What i 
can't find in docs is how to startup ices tu run under certain user 
account, not as root.

I tried to setuid /usr/bin/ices and change owner without luck... ices 
can't be started!

Also, i tried as root, to see if next command will work:

su -l alex -s /bin/bash -c "/usr/bin/ices /etc/ices-live.xm &"

or i added the above line in my startup scripts...but no ices process is 
running!

I need this feature for my startup script, because i don't want to allow 
ices to be started as root!

Any help will be appreciated!

Regards,
Alex




From karl at xiph.org  Tue Dec 28 21:40:35 2004
From: karl at xiph.org (Karl Heyes)
Date: 28 Dec 2004 21:40:35 +0000
Subject: [Icecast] Aliassing Icecast 2.1 Admin console
In-Reply-To: <000b01c4ed15$f43f1ed0$ca29a8c0@hvdr>
References: <000b01c4ed15$f43f1ed0$ca29a8c0@hvdr>
Message-ID: <1104270035.30220.7.camel@bogus.hackers.club>

On Tue, 2004-12-28 at 19:46, Henk van de Ridder wrote:
> Hello,
> 
> We are searching for a possibility of "aliassing without wasting bandwidth".
> It is described in the following section which we found at
> http://open4all.info/ossa/_Icecast_Streaming_Server.
> 
> # What happens is that when a listeners connects to your server and
> # requests the /laika stream, then your icecast server will connect
> # as a client to my machine, and then feed my stream to the listener.
> # All subsequent requests for /laika will use the same feed (i.e only
> # one connect will be made to my machine). Icecast will automagically
> # shut the link from my machine down when no one is listening. I.e
> # no bandwidth will be wasted.
...

This has been known as the on-demand relay, it has been used very
successfully in the kh branch for some time now, and will probably be
merged into the next release.

> First quesiton: It seems icecast2.1 does not have a admin-console. Is it
> still there ? How can I reach it ?

The web interface is the way to interact with a running icecast. If
there is something specifically missing then by all means raise a query.

> Second question: Is there a way of setting the relay- or alias-configuration
> is the way we want to have to limited the 'waste' of download amount.

At the current time, you'll have to use the kh branch for such a feature
(mediacast1.com/~karl).

Note that the term alias in icecast2 refers to something else.

karl.




From pnm at zephyr.to  Tue Dec 28 22:57:34 2004
From: pnm at zephyr.to (Paul Melnikow)
Date: Tue, 28 Dec 2004 17:57:34 -0500
Subject: [Icecast] startup problem: how to start ices under regular user
	account
In-Reply-To: <41D1CC6C.8030402@webgate.ro>
References: <41D1CC6C.8030402@webgate.ro>
Message-ID: <20041228225734.GA15277@netspace.org>

On Tue, Dec 28, 2004 at 11:13:16PM +0200, Alex wrote:
> I am running icecast2 and ices2 which are working fine for me. What i 
> can't find in docs is how to startup ices tu run under certain user 
> account, not as root.

here's an init script i've been using -- kind of rough, but should
probably do the trick.

http://www.zephyr.to/icecast/myices

you can put it in /etc/init.d/icecast, and probably change DUMP=false,
and USER=alex or whatever :)

hth
p.

-- 
every day is a good day


From wb8erj at hotmail.com  Wed Dec 29 03:37:51 2004
From: wb8erj at hotmail.com (M T)
Date: Tue, 28 Dec 2004 22:37:51 -0500
Subject: [Icecast] Liveice startup error message..
Message-ID: <BAY101-F5925AF9FB8021715B97079F9B0@phx.gbl>

Hello,

I have been trying to use liveice with icecast to stream live audio. I am 
getting an error message that I can't seem to find an answer to. FIrst of 
all, I start Icecast (Version 2.2.0) and it seems to come up fine.Then I 
start liveice, and I get the following error message:

liveice -c /usr/local/bin/liveice.conf
0
Initialising Soundcard
16Bit 22050Hz
opening connection to localhost 8000
Attempting to Contact Server
connection successful: forking process
server didn't send OK response


I am running Fedore core 3. My config files are below:

icecast.xml
+++++++++++++++

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

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

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

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

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

    <!-- You can use these two if you only want a single listener -->
    <!--<port>8000</port> -->
    <!--<bind-address>127.0.0.1</bind-address>-->

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

    <!--<master-server>127.0.0.1</master-server>-->
    <!--<master-server-port>8001</master-server-port>-->
    <!--<master-update-interval>120</master-update-interval>-->
    <!--<master-password>hackme</master-password>-->
    <!--
    <relay>
        <server>127.0.0.1</server>
        <port>8001</port>
        <mount>/example.ogg</mount>
        <local-mount>/different.ogg</local-mount>

        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>
    -->

    <!-- Only define a <mount> section if you want to use advanced options,
         like alternative usernames or passwords
    <mount>
        <mount-name>/example-complex.ogg</mount-name>

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

        <max-listeners>1</max-listeners>
        <dump-file>/tmp/dump-example1.ogg</dump-file>
        <burst-size>65536</burst-size>
        <fallback-mount>/example2.ogg</fallback-mount>
        <fallback-override>1</fallback-override>
        <hidden>1</hidden>
        <no-yp>1</no-yp>
        <authentication type="htpasswd">
                <option name="filename" value="myauth"/>
                <option name="allow_duplicate_users" value="0"/>
        </authentication>
    </mount>
    -->

    <fileserve>1</fileserve>

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

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

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

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

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <!-- <playlistlog>playlist.log</playlistlog> -->
      	<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
    </logging>

    <security>
        <chroot>0</chroot>
        <!--
        <changeowner>
            <user>nobody</user>
            <group>nogroup</group>
        </changeowner>
        -->
    </security>
</icecast>

+++++++++++++++


  >>> liveice configuration file:

+++++++++++++++++++++++


SERVER 192.168.2.3
SERVER streamingserver
PORT 8000
NAME WVMC 90.7 Webcast
GENRE Live
URL http://www.wvmcfm.com
PUBLIC 1
X_AUDIOCAST_LOGIN
# ICY_LOGIN
PASSWORD wvmc907
SAMPLE_RATE 22050
stereo
# uncomment the next line if you want to listen to a playlist
# NO_SOUNDCARD
# uncomment the next line is you want to listen to a stream
SOUNDCARD
HALF_DUPLEX
USE_LAME3 /usr/local/bin/lame
SOUND_DEVICE /dev/dsp
MOUNTPOINT live
BITRATE 64000
VBR_QUALITY 1
# uncomment the next line if you want to listen to a playlist
# MIXER
# uncomment the next line if you want to listen to a stream
NO_MIXER
# PLAYLIST playlist
DECODER_COMMAND mpg123
# MIX_CONTROL_MANUAL
# CONTROL_FILE mix_command
# TRACK_LOGFILE track.log
# VERBOSE 10

++++++++++++++

Any help would be greatly appreciated!

      -- Mike

     WVMC FM
Mansfield, Ashland, Willard, Ohio
  http://www.wvmcfm.com




From brendan at xiph.org  Wed Dec 29 03:45:55 2004
From: brendan at xiph.org (Brendan Cully)
Date: Tue, 28 Dec 2004 19:45:55 -0800
Subject: [Icecast] Liveice startup error message..
In-Reply-To: <BAY101-F5925AF9FB8021715B97079F9B0@phx.gbl>
References: <BAY101-F5925AF9FB8021715B97079F9B0@phx.gbl>
Message-ID: <20041229034554.GA2194@watanabe.local>

On Tuesday, 28 December 2004 at 22:37, M T wrote:
> Hello,
> 
> I have been trying to use liveice with icecast to stream live audio. I am 
> getting an error message that I can't seem to find an answer to. FIrst of 
> all, I start Icecast (Version 2.2.0) and it seems to come up fine.Then I 
> start liveice, and I get the following error message:
> 
> liveice -c /usr/local/bin/liveice.conf
> 0
> Initialising Soundcard
> 16Bit 22050Hz
> opening connection to localhost 8000
> Attempting to Contact Server
> connection successful: forking process
> server didn't send OK response
...
>  >>> liveice configuration file:
...
> X_AUDIOCAST_LOGIN
> # ICY_LOGIN
...

This is most likely your problem. X_AUDIOCAST is the icecast 1
protocol, and it's not supported in v2. I don't use liveice, so I
don't know what you should replace it with - see the docs. My guess
is something like HTTP_LOGIN.


From bobr2 at telcen.com  Wed Dec 29 06:04:39 2004
From: bobr2 at telcen.com (Bob Reite)
Date: Wed, 29 Dec 2004 01:04:39 -0500
Subject: [Icecast] Help needed with port 80 on Fedora
Message-ID: <41D248F7.5020006@telcen.com>

I'm running Icecast 2.2.0 on RedHat Fedora core 2.  It's working fine if
I use the default port of 8000.   I need to use port 80 because of 
client firewall issues.   However when I try to reconfigure icecast.xml
to port 80, I get "cannot create listener socket on port 80".

I'm guessing it's some permissions issue in Fedora, but I'll be darned 
if I can find it!  Any suggestions?  I tried looking in both the Icecast 
and RedHat documentation, but no luck.

Bob Reite
Telecentral Electronics, Inc.



From geoff at hitsandpieces.net  Wed Dec 29 06:14:53 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Wed, 29 Dec 2004 16:14:53 +1000
Subject: [Icecast] Help needed with port 80 on Fedora
In-Reply-To: <41D248F7.5020006@telcen.com>
References: <41D248F7.5020006@telcen.com>
Message-ID: <Pine.LNX.4.61.0412291613240.1178@data.home>

Hi:

Two thoughts.

1.  You need to run as root to be able to use ports < 1024.  This could
    well be your problem.

2.  Make sure there's nothing else (like a webserver) runing on port 80.

Geoff.


-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From geoff at hitsandpieces.net  Wed Dec 29 06:32:32 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Wed, 29 Dec 2004 16:32:32 +1000
Subject: [Icecast] Shoutcast compatibility suggestions
Message-ID: <Pine.LNX.4.61.0412291615050.1178@data.home>

Hi:

Ok, I've not managed to find any documentation on the shoutcast 
compatibility introduced in icecast 2.2.0, so please humour me if I 
missunderstand how it's meant to work.

This is my understanding of it currently:

1.  You configure Icecast (as shown in the shoutcast example) so that 
shoutcast connections get mapped to the mountpoint you define.

2.  You configure a listen socket specifically for use as a shoutcast 
source port.  People connecting on this port wil have their stream appear 
on regular Icecast ports under the mountpoint defined for Shoutcast 
streams.

Note that it's not clear whether you can only have one port defined, or 
just that you can only have one of such ports active at any one time.

3.  So, you end up with a situation where you have a regular Icecast setup
    running on your regular Icecast port(s), plus one (or possibly more)
    ports set up specifically to receive shoutcast-style connections which
    will appear on the regular Icecast port(s) under the mountpoint
    specified for such streams.

Assuming I'm correct so far, my observations follow.

The one downside to this setup is that you can only accept one shoutcast 
style connection at a time.  This means that if you have people who want or 
need to use this type of connection, you need to run multiple servers. 
This seems kinda silly to me as Icecast is otherwise designed to handle as 
many streams as you can manage.

My proposal is this.  Move the mountpoint specifier from where it is now 
into the section where you configure the shoutcast source port.  This way, 
you could configure several shoutcast source ports, each with their own 
mountpoint and hence served by the one server.  Ideally, it would also be 
good if you could define separate source passwords for such ports too, but 
I don't know how much work that would be.

I do realise that we aren't really in the business of encouraging the use 
of shoutcast sources, but at least such a change would encourage the use of 
the Icecast server as it would negate the need to run multiple servers. 
Currently I work with a project that runs 6 shoutcast-compatible servers as 
well as an Icecast server.  I'd dearly love to be able to get rid of most 
of these.  If I can do it without having to bug any of the broadcasters 
into changing their software, then it'll go a lot more smoothly.

Geoff.


-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From mlrsmith at gmail.com  Wed Dec 29 06:52:42 2004
From: mlrsmith at gmail.com (Michael Smith)
Date: Wed, 29 Dec 2004 17:52:42 +1100
Subject: [Icecast] Help needed with port 80 on Fedora
In-Reply-To: <41D248F7.5020006@telcen.com>
References: <41D248F7.5020006@telcen.com>
Message-ID: <3c17372104122822525511442a@mail.gmail.com>

On Wed, 29 Dec 2004 01:04:39 -0500, Bob Reite <bobr2 at telcen.com> wrote:
> I'm running Icecast 2.2.0 on RedHat Fedora core 2.  It's working fine if
> I use the default port of 8000.   I need to use port 80 because of
> client firewall issues.   However when I try to reconfigure icecast.xml
> to port 80, I get "cannot create listener socket on port 80".

Unix systems don't allow non-root users to bind to ports less than
1024. So, you need to be root to do this.

When you try this, you'll then find that icecast refuses to run as
root (in an attempt to prevent any possible icecast security holes
from being _too_ serious).

So, you'll have to configure the <changeowner> section (inside
<security>) in your icecast configuration file.

This tells icecast to change to a different user (whichever one you
choose) after it binds listening sockets, but before it starts
accepting connections from the network.

Mike


From jakobao at yahoo.com  Wed Dec 29 08:21:27 2004
From: jakobao at yahoo.com (qiang Bao)
Date: Wed, 29 Dec 2004 00:21:27 -0800 (PST)
Subject: [Icecast] icecast2.2 and aac?
Message-ID: <20041229082127.79377.qmail@web60209.mail.yahoo.com>

it seems that icecast 2.2 can only stream aac at 128kbps!
 
mp3 and ogg are ok at all bitrates.
 
is it a bug or my config wrong?

		
---------------------------------
Do you Yahoo!?
 Jazz up your holiday email with celebrity designs. Learn more.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041229/9edf982b/attachment.htm>

From pem at levillage.org  Wed Dec 29 09:04:31 2004
From: pem at levillage.org (Pierre-Emmanuel Muller)
Date: Wed, 29 Dec 2004 10:04:31 +0100
Subject: [Icecast] Some ideas
Message-ID: <41D2731F.7080000@levillage.org>

Hi all,

I'll try to explain my suggestion with my poor english.

I've got the feeling that icecast is full of potential but not growing 
as fast as it can or simply not having the support it could have.

The greatest lack are the "open doors" for new coders, webdesigners, 
translators, etc. Icecast is open: the sourcecode is open, the mailing 
list is open, etc. But a skill is not enough. You need some kind of 
structure, some kind of simple tasks to do.

Look at KDE. You can find many "How to help" pages on many sites with 
such things :
- You're a coder? Welcome, go here and ask or look at this list of 
things to do and begin to code.
- You're a webdesigner/PHP wizard? Welcome, go here and do that.
- You're a PR/marketing/journalist pple? Welcome, we need to promote our 
work.
- You're a happy KDE user? Go here and fill our form, we're glad to ear 
from you.
Then, the guy who wants to help exactly knows where to go and what to do.
Just look at me. Unable to code something correct, not good enough to be 
a standalone PHP coder but I can read english and german and french is 
my native language. So what? A week after having the idea to help, I was 
rereading some docs and working with the translation team.
So my suggestion is: lets stop icecast. KDE is better.
Ah ah.

I know it is hard to have a clear roadmap, to communicate and explain 
all the things going around icecast. But that's also a way to open 
icecast. When I know what's going on, I know what I can do.
The lack of open doors can also be known and not that bad if you want 
icecast to remain the fact of few people and keep it more or less to 
your own and be sure to grab most of the fama/pride/money.

Here are my suggestions:
- building up a simple webpage with a "bounties" system. A user can fill 
a form and ask for some specific feature. When a feature request already 
exists, a new user can simply vote for it. At the moment, I have to 
subscribe to the list and ask it in english. Such a system is a closed 
door to many users. The icecast developpers could have a "froze" 
feature. When they know that it's dangerous to work on some feature 
because it's going to be implemented or that the code is moving too 
fast, they froze the feature. When a coder see a feature or a bug he can 
solve, he registers, subscribe to the feature, get the code, work on it, 
give the clue to an icecast core team and that's it. He's now and the 
Hall Of Fame Of Nice People. Having such small things to do is a good 
way to begin. Plug coders on the main trunk is too complicated.
Feature, bugs, etc., I'm sure that the main icecast coders are aware of 
some bugs but do not have the time to solve them. They could also fill 
some "bounties".
And, why not, some company could give some money for specific bounties. 
Again, that's an open door.
- have an internationalization team. First: translate the docs, second, 
translate the website, etc. That can be made without any specific tool. 
We just need a "start" and coordination.
- have a "happy user" page with a form : why are you using icecast? how 
many users are you serving? etc. Then, when a new user discovers icecast 
he can know how strong and powerful the server is. When I first 
discovered icecast I could not know if the server could handle 100, 200 
ou 500 users. How is icecast reacting when 200 streams @ 128kb/s are 
sended? Etc. That's easy to do.

So.
I'm ready to help :)

PeM




From pem at levillage.org  Wed Dec 29 12:01:17 2004
From: pem at levillage.org (Pierre-Emmanuel Muller)
Date: Wed, 29 Dec 2004 13:01:17 +0100
Subject: [Icecast] Some ideas
In-Reply-To: <41D2731F.7080000@levillage.org>
References: <41D2731F.7080000@levillage.org>
Message-ID: <41D29C8D.8030807@levillage.org>

Another idea.
What about asking someone like Dag (http://dag.wieers.com) to include 
icecast in his repo? Having the ability to install icecast with a simple 
"yum install icecast" would give icecast many users.
That's an exemple of what can be done by icecast zealots. You can help 
without coding the Theora core libs : you packages the softs.

PeM


Pierre-Emmanuel Muller wrote:

> Hi all,
>
> I'll try to explain my suggestion with my poor english.
>



From geoff at hitsandpieces.net  Wed Dec 29 12:19:55 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Wed, 29 Dec 2004 22:19:55 +1000
Subject: [Icecast] Some ideas
In-Reply-To: <41D2731F.7080000@levillage.org>
References: <41D2731F.7080000@levillage.org>
Message-ID: <Pine.LNX.4.61.0412292204470.1178@data.home>

Hi:

I'll start out by saying that I'm just a humble user, though a user who has 
kept an eye on Icecast and related development for about 5 years now.

To start with, Icecast is just one of the projects of the Xiph.org 
Foundation (http://www.xiph.org).  So while some of the things you mention 
are not in place for Icecast specifically, they are in place or at least on 
the drawing boardfor Xiph generally.

Some might disagree with me, but I find that Xiph is pretty open about what 
it's up to and what still needs to be done.  Apart from the various mailing 
lists, there is the xiph.org wiki (http://wiki.xiph.org), which includes 
details of and transcripts of their monthly meetings which are a good way 
to keep across the various projects.

For Icecast specifically, the icecast-dev list is a good place to look. 
There's also the ToDo file in the Icecast source tree, and the xiph 
bugtracker at trac.xiph.org (nice looking tracker BTW, much less 
intimidating than the one you guys had before).

The bounty thing has already been thought of, and an attempt to start one 
up has already begun.  See http://wiki.xiph.org/index.php/Bounties .  I 
note that there's no Icecast specific bounties in there yet, but some 
existing bounties would benefit Icecast (particularly bitrate peeling in 
Ogg Vorbis).

I agree that documentation for Icecast in multiple languages would be nice. 
But I was looking at the docs today and I personally think they need a bit 
of work in English first before we go translating them into other 
languages.  I didn't see anything regarding recent features of Icecast in 
the docs I read, and there's been a typo in the ReadMe for as long as I can 
remember.

As for the website, the Xiph websites in general have a team of people 
working on them following a call for help that went out a few months ago. 
Judging by the commits I see, they seem to be doing good work.  Not sure 
who to contact to offer help but I'm sure someone on here will know.

Not sure if any of this info is helpful, hopefully it is.

Geoff.


-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From pem at levillage.org  Wed Dec 29 13:03:17 2004
From: pem at levillage.org (Pierre-Emmanuel Muller)
Date: Wed, 29 Dec 2004 14:03:17 +0100
Subject: [Icecast] Some ideas
In-Reply-To: <Pine.LNX.4.61.0412292204470.1178@data.home>
References: <41D2731F.7080000@levillage.org>
	<Pine.LNX.4.61.0412292204470.1178@data.home>
Message-ID: <41D2AB15.8060609@levillage.org>

Hi Geoff,

Geoff Shang wrote:

> I'll start out by saying that I'm just a humble user

me too :)

> To start with, Icecast is just one of the projects of the Xiph.org 
> Foundation (http://www.xiph.org).  So while some of the things you 
> mention are not in place for Icecast specifically, they are in place 
> or at least on the drawing boardfor Xiph generally.

I know and agree. I would like to make myself clear. Icecast is open and 
is a great piece of software and many tools are already avalaible. I do 
not wanted to say that Icecast is a "closed" project. I said that, in my 
humble point of view, some "entry doors" are missing.

> Some might disagree with me, but I find that Xiph is pretty open about 
> what it's up to and what still needs to be done.  Apart from the 
> various mailing lists, there is the xiph.org wiki 
> (http://wiki.xiph.org), which includes details of and transcripts of 
> their monthly meetings which are a good way to keep across the various 
> projects.

You're right. But I must confess that I'm still a bit confused when I 
navigate between the icecast website, the xiph website, the vorbis 
website and so on. Although all the required informations are present, 
I, as an end-user, feel that all is a bit confusing. I'm not confused 
about what is icecast for xiph, but a bit confused on the user 
experience side.

> For Icecast specifically, the icecast-dev list is a good place to 
> look. There's also the ToDo file in the Icecast source tree, and the 
> xiph bugtracker at trac.xiph.org (nice looking tracker BTW, much less 
> intimidating than the one you guys had before).

Alles klar. The bugtracker is the perfect tool but for coders and tech 
aware guys. I was just wondering about the "d?cideur press?", the guy 
who needs a fast a clear view of where is icecast going.
Why is the icecast roadmap directly awalaible from the icecast website?
Why is not the icecast bugtracker on the icecast website with a clear 
"suggest a feature" link?

> The bounty thing has already been thought of, and an attempt to start 
> one up has already begun.  See http://wiki.xiph.org/index.php/Bounties 
> .  I note that there's no Icecast specific bounties in there yet, but 
> some existing bounties would benefit Icecast (particularly bitrate 
> peeling in Ogg Vorbis).

Yes. But :)
First of all: a wiki. Okay wikipedia is an enormous website but I'm not 
sure that a wiki is the most user friendly system for feature requests.
That's not on the icecast website. Why are this bounties not stated 
(linked) from the icecast website?
Bitrate peeling is for sure an important side of icecast but something 
like "automatic generation of relay config avalaible through HTTP" or 
"automatic config file generation from icecast.xml for darkice, ices, 
M3W, etc." are also some important points.

In fact, I think that the point is that you can help, for sure. But you 
have to make your own way into icecast/xiph. It is not clear that help 
is wanted.

> I agree that documentation for Icecast in multiple languages would be 
> nice. But I was looking at the docs today and I personally think they 
> need a bit of work in English first before we go translating them into 
> other languages.  I didn't see anything regarding recent features of 
> Icecast in the docs I read, and there's been a typo in the ReadMe for 
> as long as I can remember.

So :)
Why not make an icecast bounty, on the icecast website, about "review 
the doc, add the new feature, correct the typo, translate the FAQ in 
French, etc."
The icecast doc needs help but that's not said on the website.
Why having a section on the website called "Help wanted" and state here 
clearly all the requested help : code, docs, etc. When you visit the 
site you know that icecast is growing but you do not understand that any 
new help is welcome.

> Not sure if any of this info is helpful, hopefully it is.

It helped :)

PeM


From oddsock at oddsock.org  Wed Dec 29 14:49:54 2004
From: oddsock at oddsock.org (oddsock)
Date: Wed, 29 Dec 2004 08:49:54 -0600
Subject: [Icecast] Shoutcast compatibility suggestions
In-Reply-To: <Pine.LNX.4.61.0412291615050.1178@data.home>
References: <Pine.LNX.4.61.0412291615050.1178@data.home>
Message-ID: <6.0.1.1.2.20041229083213.03376cc0@www.oddsock.org>

At 12:32 AM 12/29/2004, you wrote:
>Hi:
>
>Ok, I've not managed to find any documentation on the shoutcast 
>compatibility introduced in icecast 2.2.0, so please humour me if I 
>missunderstand how it's meant to work.
>
>This is my understanding of it currently:
>
>1.  You configure Icecast (as shown in the shoutcast example) so that 
>shoutcast connections get mapped to the mountpoint you define.
>
>2.  You configure a listen socket specifically for use as a shoutcast 
>source port.  People connecting on this port wil have their stream appear 
>on regular Icecast ports under the mountpoint defined for Shoutcast streams.

The shoutcast-compat options in icecast were introduced so that we could 
properly handle the Shoutcast DSP style source client connection.  Here are 
the important bits we needed to implement :

* The shoutcast DSP connects on 2 different ports (lets call this "port" 
and "port + 1").  The authentication handshaking (as well as the actual 
stream data) comes over "port + 1", while "port" is used only for sending 
in metadata updates.
* The shoutcast DSP sends in metadata update requests over "port", but does 
not specify any kind of mountpoint (obviously since it knows nothing about 
them).
* The shoutcast DSP connection protocol is obscure enough that we were not 
able to easily flag that type of connection protocol (this caused us to 
require that all "port + 1" connections must be flagged as 
"shoutcast-compat" to enable shoutcast DSP style connection behavior on 
that port.

So to setup icecast in shoutcast-compat mode you pretty much just create 
another listen port (one larger than your original port) and mark that 
"port + 1" port as "shoutcast-compat".  This is what the example config 
does.  Also, since the shoutcast DSP doesn't allow you to specify any kind 
of mountpoint (or anything close to it), you are able to assign a "virtual 
mountpoint" via the <shoutcast-mount> option.  The default is to map all 
shoutcast DSP sources to /stream.  The main problem (and reason why you 
cannot attach multiple Shoutcast DSPs reliably to a single icecast 
instance) is the Shoutcast DSP's ignorance of mountpoints.  Metadata 
updates are sent in over the "port" port, and have no mountpoint 
designation.  So, while technically you could connect 2 (or more) Shoutcast 
DSPs to icecast, you would have no way to map the metadata updates from 
those 2 to the correct mountpoints.   It may be possible to do this based 
off the port the request came in on (that would then require you to setup a 
set of 'port' and 'port + 1' pairs for each possible shoutcast DSP you 
wanted to connect.  This is not a very elegant solution however, and is 
marginally better than starting up multiple icecast instances.  although we 
may consider implementing it if enough people ask for it.

The good news is, once you've connected a shoutcast DSP to icecast (and it 
is mapped to a mountpoint), then you can use all the normal 
"mountpoint-specific" settings that any normal mountpoint can.  this 
includes specifying a different source password, all the authentication 
stuff, and things like fallbacks.

Hope this explains it a bit better, and if you have any questions, feel 
free to followup...

oddsock




From karl at xiph.org  Wed Dec 29 15:30:25 2004
From: karl at xiph.org (Karl Heyes)
Date: 29 Dec 2004 15:30:25 +0000
Subject: [Icecast] icecast2.2 and aac?
In-Reply-To: <20041229082127.79377.qmail@web60209.mail.yahoo.com>
References: <20041229082127.79377.qmail@web60209.mail.yahoo.com>
Message-ID: <1104334224.30220.23.camel@bogus.hackers.club>

On Wed, 2004-12-29 at 08:21, qiang Bao wrote:
> it seems that icecast 2.2 can only stream aac at 128kbps!
>  
> mp3 and ogg are ok at all bitrates.
>  
> is it a bug or my config wrong?

AAC is not specifically handled. The stream data that is sent in, gets
sent out to listeners, icecast doesn't even know it's 128kbps.

Without knowing the details of the problem you're having it's hard to
say what the cause is.

karl.




From giles at xiph.org  Wed Dec 29 18:52:48 2004
From: giles at xiph.org (Ralph Giles)
Date: Wed, 29 Dec 2004 10:52:48 -0800
Subject: [Icecast] Shoutcast compatibility suggestions
In-Reply-To: <6.0.1.1.2.20041229083213.03376cc0@www.oddsock.org>
References: <Pine.LNX.4.61.0412291615050.1178@data.home>
	<6.0.1.1.2.20041229083213.03376cc0@www.oddsock.org>
Message-ID: <20041229185248.GA16363@ghostscript.com>

On Wed, Dec 29, 2004 at 08:49:54AM -0600, oddsock wrote:

>               So, while technically you could connect 2 (or more) Shoutcast 
> DSPs to icecast, you would have no way to map the metadata updates from 
> those 2 to the correct mountpoints.   It may be possible to do this based 
> off the port the request came in on (that would then require you to setup a 
> set of 'port' and 'port + 1' pairs for each possible shoutcast DSP you 
> wanted to connect.  This is not a very elegant solution however, and is 
> marginally better than starting up multiple icecast instances.  although we 
> may consider implementing it if enough people ask for it.

IMHO, it's much better than having to run multiple instances. Especially 
since you're already doing magic with the paired ports. 

 -r


From mark at indymedia.org  Wed Dec 29 19:02:52 2004
From: mark at indymedia.org (mark burdett)
Date: Wed, 29 Dec 2004 11:02:52 -0800
Subject: [Icecast] Shoutcast compatibility suggestions
In-Reply-To: <20041229185248.GA16363@ghostscript.com>
References: <Pine.LNX.4.61.0412291615050.1178@data.home>
	<6.0.1.1.2.20041229083213.03376cc0@www.oddsock.org>
	<20041229185248.GA16363@ghostscript.com>
Message-ID: <3D60B508-59CC-11D9-B913-0030654FD4CC@indymedia.org>

yup sounds pretty good (if you're already taking the shoutcast compat 
plunge).

--mark

On 29 Dec 2004, at 10:52, Ralph Giles wrote:

> On Wed, Dec 29, 2004 at 08:49:54AM -0600, oddsock wrote:
>
>>               So, while technically you could connect 2 (or more) 
>> Shoutcast
>> DSPs to icecast, you would have no way to map the metadata updates 
>> from
>> those 2 to the correct mountpoints.   It may be possible to do this 
>> based
>> off the port the request came in on (that would then require you to 
>> setup a
>> set of 'port' and 'port + 1' pairs for each possible shoutcast DSP you
>> wanted to connect.  This is not a very elegant solution however, and 
>> is
>> marginally better than starting up multiple icecast instances.  
>> although we
>> may consider implementing it if enough people ask for it.
>
> IMHO, it's much better than having to run multiple instances. 
> Especially
> since you're already doing magic with the paired ports.
>
>  -r
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From greg at orban.com  Wed Dec 29 19:08:04 2004
From: greg at orban.com (Greg J. Ogonowski)
Date: Wed, 29 Dec 2004 11:08:04 -0800
Subject: [Icecast] icecast2.2 and aac?
In-Reply-To: <20041229082127.79377.qmail@web60209.mail.yahoo.com>
References: <20041229082127.79377.qmail@web60209.mail.yahoo.com>
Message-ID: <6.1.2.0.2.20041229110637.03a97898@66.220.31.130>

Icecast 2.2 works fine with AAC/aacPlus at any bitrate.

32kbps here:

http://stream.orban.com:80/eval

-greg.



At 00:21 2004-12-29, qiang Bao wrote:
>it seems that icecast 2.2 can only stream aac at 128kbps!
>
>mp3 and ogg are ok at all bitrates.
>
>is it a bug or my config wrong?
>
>
>Do you Yahoo!?
>Jazz up your holiday email with celebrity designs. 
><http://us.rd.yahoo.com/evt=29910/*http://celebrity.mail.yahoo.com>Learn more.
>_______________________________________________
>Icecast mailing list
>Icecast at xiph.org
>http://lists.xiph.org/mailman/listinfo/icecast


__________________________________________________________________________
Greg J. Ogonowski
VP Product Development
ORBAN / CRL, Inc.
1525 Alvarado St.
San Leandro, CA  94577  USA
TEL +1 510 351-3500
FAX +1 510 351-0500
greg at orban.com
http://www.orban.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041229/498f91dd/attachment.htm>

From Dennis at heerema.net  Wed Dec 29 20:53:08 2004
From: Dennis at heerema.net (Dennis Heerema)
Date: Wed, 29 Dec 2004 21:53:08 +0100
Subject: [Icecast] icecast2.2 and aac?
In-Reply-To: <6.1.2.0.2.20041229110637.03a97898@66.220.31.130>
References: <20041229082127.79377.qmail@web60209.mail.yahoo.com>
	<6.1.2.0.2.20041229110637.03a97898@66.220.31.130>
Message-ID: <WorldClient-F200412292153.AA53080004@heerema.net>

Trying to get the LE version for months now, still treamguys can?t 
deliver....

Regards,

Dennis Heerema


-----Original Message-----
From: "Greg J. Ogonowski" <greg at orban.com>
To: qiang Bao <jakobao at yahoo.com>, icecast at xiph.org
Date: Wed, 29 Dec 2004 11:08:04 -0800
Subject: Re: [Icecast] icecast2.2 and aac?

Icecast 2.2 works fine with AAC/aacPlus at any bitrate.

32kbps here:

http://stream.orban.com:80/eval

-greg.



At 00:21 2004-12-29, qiang Bao wrote:

it seems that icecast 2.2 can only stream aac at 128kbps!
 
mp3 and ogg are ok at all bitrates.
 
is it a bug or my config wrong?


Do you Yahoo!?
Jazz up your holiday email with celebrity designs. Learn more. 
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast


__________________________________________________________________________
Greg J. Ogonowski
VP Product Development
ORBAN / CRL, Inc.
1525 Alvarado St.
San Leandro, CA  94577  USA
TEL +1 510 351-3500
FAX +1 510 351-0500
greg at orban.com
http://www.orban.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041229/50246405/attachment.htm>

From greg at orban.com  Wed Dec 29 21:04:17 2004
From: greg at orban.com (Greg J. Ogonowski)
Date: Wed, 29 Dec 2004 13:04:17 -0800
Subject: [Icecast] icecast2.2 and aac?
In-Reply-To: <WorldClient-F200412292153.AA53080004@heerema.net>
References: <20041229082127.79377.qmail@web60209.mail.yahoo.com>
	<6.1.2.0.2.20041229110637.03a97898@66.220.31.130>
	<WorldClient-F200412292153.AA53080004@heerema.net>
Message-ID: <6.1.2.0.2.20041229125717.03eac2b0@66.220.31.130>

Dennis-

Orban Opticodec-PC LE is available now, as of last Tuesday, the release 
date of Icecast2 v2.2.

StreamGuys is filling all orders now.

Thanks.
-greg.




At 12:53 2004-12-29, Dennis Heerema wrote:
>Trying to get the LE version for months now, still treamguys can?t deliver....
>
>Regards,
>
>Dennis Heerema
>
>-----Original Message-----
>From: "Greg J. Ogonowski" <greg at orban.com>
>To: qiang Bao <jakobao at yahoo.com>, icecast at xiph.org
>Date: Wed, 29 Dec 2004 11:08:04 -0800
>Subject: Re: [Icecast] icecast2.2 and aac?
>
>Icecast 2.2 works fine with AAC/aacPlus at any bitrate.
>
>32kbps here:
>
>http://stream.orban.com:80/eval
>
>-greg.
>
>
>
>At 00:21 2004-12-29, qiang Bao wrote:
>>it seems that icecast 2.2 can only stream aac at 128kbps!
>>
>>mp3 and ogg are ok at all bitrates.
>>
>>is it a bug or my config wrong?
>>
>>
>>Do you Yahoo!?
>>Jazz up your holiday email with celebrity designs. 
>><http://us.rd.yahoo.com/evt=29910/*http://celebrity.mail.yahoo.com>Learn more.
>>_______________________________________________
>>Icecast mailing list
>>Icecast at xiph.org
>>http://lists.xiph.org/mailman/listinfo/icecast
>
>
>__________________________________________________________________________
>Greg J. Ogonowski
>VP Product Development
>ORBAN / CRL, Inc.
>1525 Alvarado St.
>San Leandro, CA  94577  USA
>TEL +1 510 351-3500
>FAX +1 510 351-0500
>greg at orban.com
>http://www.orban.com


__________________________________________________________________________
Greg J. Ogonowski
VP Product Development
ORBAN / CRL, Inc.
1525 Alvarado St.
San Leandro, CA  94577  USA
TEL +1 510 351-3500
FAX +1 510 351-0500
greg at orban.com
http://www.orban.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041229/27a14a4d/attachment.htm>

From Dennis at Heerema.net  Thu Dec 30 00:25:04 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Thu, 30 Dec 2004 01:25:04 +0100
Subject: [Icecast] icecast2.2 and aac?
References: <20041229082127.79377.qmail@web60209.mail.yahoo.com><6.1.2.0.2.20041229110637.03a97898@66.220.31.130><WorldClient-F200412292153.AA53080004@heerema.net>
	<6.1.2.0.2.20041229125717.03eac2b0@66.220.31.130>
Message-ID: <003101c4ee06$0ef8b010$0202a8c0@heerema.local>

Greg,

Thanks! hope i will receive it, it's a nice step forward in quality vs bitrate!

Regards,

Dennis Heerema
  ----- Original Message ----- 
  From: Greg J. Ogonowski 
  To: Dennis Heerema ; qiang Bao ; icecast at xiph.org 
  Sent: Wednesday, December 29, 2004 10:04 PM
  Subject: Re: [Icecast] icecast2.2 and aac?


  Dennis-

  Orban Opticodec-PC LE is available now, as of last Tuesday, the release date of Icecast2 v2.2.

  StreamGuys is filling all orders now.

  Thanks.
  -greg.




  At 12:53 2004-12-29, Dennis Heerema wrote:

    Trying to get the LE version for months now, still treamguys can?t deliver....
     
    Regards,

    Dennis Heerema


      -----Original Message-----

      From: "Greg J. Ogonowski" <greg at orban.com>

      To: qiang Bao <jakobao at yahoo.com>, icecast at xiph.org

      Date: Wed, 29 Dec 2004 11:08:04 -0800

      Subject: Re: [Icecast] icecast2.2 and aac?


      Icecast 2.2 works fine with AAC/aacPlus at any bitrate.


      32kbps here:


      http://stream.orban.com:80/eval


      -greg.




      At 00:21 2004-12-29, qiang Bao wrote:

        it seems that icecast 2.2 can only stream aac at 128kbps!



        mp3 and ogg are ok at all bitrates.



        is it a bug or my config wrong?



        Do you Yahoo!?

        Jazz up your holiday email with celebrity designs. Learn more. 

        _______________________________________________

        Icecast mailing list

        Icecast at xiph.org

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



      __________________________________________________________________________

      Greg J. Ogonowski

      VP Product Development

      ORBAN / CRL, Inc.

      1525 Alvarado St.

      San Leandro, CA  94577  USA

      TEL +1 510 351-3500

      FAX +1 510 351-0500

      greg at orban.com

      http://www.orban.com 



  __________________________________________________________________________
  Greg J. Ogonowski
  VP Product Development
  ORBAN / CRL, Inc.
  1525 Alvarado St.
  San Leandro, CA  94577  USA
  TEL +1 510 351-3500
  FAX +1 510 351-0500
  greg at orban.com
  http://www.orban.com 



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


  _______________________________________________
  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/20041230/5b3c03be/attachment.htm>

From geoff at hitsandpieces.net  Thu Dec 30 01:10:39 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Thu, 30 Dec 2004 11:10:39 +1000
Subject: [Icecast] Shoutcast compatibility suggestions
In-Reply-To: <6.0.1.1.2.20041229083213.03376cc0@www.oddsock.org>
References: <Pine.LNX.4.61.0412291615050.1178@data.home>
	<6.0.1.1.2.20041229083213.03376cc0@www.oddsock.org>
Message-ID: <Pine.LNX.4.61.0412301053070.1178@data.home>

oddsock wrote:

> The authentication handshaking (as well as the actual stream 
> data) comes over "port + 1", while "port" is used only for sending in 
> metadata updates.

Oh yuck!

> * The shoutcast DSP sends in metadata update requests over "port", but does 
> not specify any kind of mountpoint (obviously since it knows nothing about 
> them).

Indeed.  So much for my idea, at least in the form I presented it.  But 
this does make it essential to have a regular listen socket on 
shoutcastsourceport-1, which could probably be more strongly worded in the 
docs (e.g. metadata updates won't work if you don't do this).  Of course, 
I've not really checked the docs for this (it might already be in there), 
but the config file sample seemed to suggest that it was a good idea rather 
than strongly recommending against not doing it (if that makes any sense).

I do agree that defining port pairs would be a bit clunky, but the whole 
thing has a ring of clunkiness about it (not Xiph's fault of course), and 
given that we are treating the base port specially with the metadata then 
perhaps this would be the best way to do it.  And perhaps it would be less 
confusing to have a <shoutcastcompat> section with all the required values 
or something.

Geoff.





From jakobao at yahoo.com  Thu Dec 30 05:28:07 2004
From: jakobao at yahoo.com (qiang Bao)
Date: Wed, 29 Dec 2004 21:28:07 -0800 (PST)
Subject: [Icecast] Re: Icecast Digest, Vol 7, Issue 34
In-Reply-To: <20041229200004.A85A31CB52@westfish.xiph.org>
Message-ID: <20041230052807.80564.qmail@web60203.mail.yahoo.com>


Message: 2
Date: 29 Dec 2004 15:30:25 +0000
From: Karl Heyes 
Subject: Re: [Icecast] icecast2.2 and aac?
To: qiang Bao 
Cc: icecast 
Message-ID: <1104334224.30220.23.camel at bogus.hackers.club>
Content-Type: text/plain

On Wed, 2004-12-29 at 08:21, qiang Bao wrote:
> it seems that icecast 2.2 can only stream aac at 128kbps!
> 
> mp3 and ogg are ok at all bitrates.
> 
> is it a bug or my config wrong?

AAC is not specifically handled. The stream data that is sent in, gets
sent out to listeners, icecast doesn't even know it's 128kbps.

Without knowing the details of the problem you're having it's hard to
say what the cause is.

karl.




Message: 5
Date: Wed, 29 Dec 2004 11:08:04 -0800
From: "Greg J. Ogonowski" 
Subject: Re: [Icecast] icecast2.2 and aac?
To: qiang Bao , icecast at xiph.org
Message-ID: <6.1.2.0.2.20041229110637.03a97898 at 66.220.31.130>
Content-Type: text/plain; charset="us-ascii"

Icecast 2.2 works fine with AAC/aacPlus at any bitrate.

32kbps here:

http://stream.orban.com:80/eval

-greg.



At 00:21 2004-12-29, qiang Bao wrote:
>it seems that icecast 2.2 can only stream aac at 128kbps!
>
>mp3 and ogg are ok at all bitrates.
>
>is it a bug or my config wrong?
>
>


I use winamp 5 with oddcast plugin. The plugin showed it sent 200Kbps AAC to icecast,but icecast can only stream out at constant bitrate 128Kbps ??

I mean that icecast stream aac at constant bitrate which is 128.    128kbps  32KHz

it can stream at 32KHz 44.1KHz 48Khz,i know that.

 

I also want to know how to make it stream at other bitrates?

and which source support HE-AAC?

Thank you for your work!

Sincerely


		
---------------------------------
Do you Yahoo!?
 Meet the all-new My Yahoo! ? Try it today! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041229/55bad6c5/attachment.htm>

From Dennis at Heerema.net  Thu Dec 30 10:01:27 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Thu, 30 Dec 2004 11:01:27 +0100
Subject: [Icecast] icecast2.2 and aac?
References: <20041230050339.92360.qmail@web60209.mail.yahoo.com>
Message-ID: <005701c4ee56$93dbf300$0202a8c0@heerema.local>

ICecast i capable of sorts of streams, that is not your problem.

Your stream source client (DSP) is the part who must be capable of streaming the format you want.

For AAC use oddcast DSP www.oddsock.org capabale of AAC, LAME Mp3, and OGG (Free to use) very good at OGG specially with the vorbis 1.1 aoTuVb3 DLLs

For AAC Plus (HE_AAC) use Orban opticodec for PC (witch is capable of every bitrate you want, even dolby up to 48 Channels i believe) and the orvan LE codec witch is limited to 32 Kbps 32 khz, but cheaper. (www.orban.com) sounds great uses SBR like in mp3Pro

there is shoutcast (www.shoutcast.com) only capable of streaming MP3 format, but really good at this (free to use).

The guys of shoutcast made als nsvtools (look at the video stream  forums at winamp.com) witch is capable of streaming video, but also audio only ans is capable of streaming AAC (with a dolby codec) (free to use and very beta)

There is http://www.spacialaudio.com/ witch have a complete DJ package SAM and a winamp plug-in capable of streaming MP3pro, OGG, WMA, LAME MP3 and MP3 (no freeware)

All of them are windows capable and a lot of them support other platforms like BSD and other Linux variants too.

I probably forgot a lot more, specially the streamclints for one type of platform only, maybe somebody els can give more info on the clients for linux platform versions only.

Regards,

Dennis



  ----- Original Message ----- 
  From: qiang Bao 
  To: Dennis Heerema 
  Sent: Thursday, December 30, 2004 6:03 AM
  Subject: Re: [Icecast] icecast2.2 and aac?

  At 00:21 2004-12-29, qiang Bao wrote:

        it seems that icecast 2.2 can only stream aac at 128kbps!
         
        mp3 and ogg are ok at all bitrates.
         
        is it a bug or my config wrong?






        I mean that icecast stream aac at constant bitrate which is 128.    128kbps  32KHz

        it can stream at 32KHz 44.1KHz 48Khz,i know that.



        I want to know how to make it stream at other bitrates?

        and which source support HE-AAC?

        Thank you for your work
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041230/425ac38c/attachment.htm>

From mihamina at mail.rktmb.org  Thu Dec 30 07:08:24 2004
From: mihamina at mail.rktmb.org (Rakotomandimby (R12y) Mihamina)
Date: Thu, 30 Dec 2004 08:08:24 +0100
Subject: [Icecast] XML parsing error I can't find
Message-ID: <1104390504.649.30.camel@ngeza>

Hello,
I'm running Debian/Linux and installed the Debian package of Icecast.
It's 2.2.0 one.
I got a parsing error I can't detect.
When launching Icecast :
[...]
Starting icecast2: Starting icecast2
Detaching from the console
I/O warning : failed to load external entity "/etc/icecast2/icecast.xml"
FATAL: error parsing config file (/etc/icecast2/icecast.xml)
XML config parsing error
[...]

- Permission on /etc/icecast2/icecast.xml is "all can read"
- error.log does not tell me nothing (obviuos: the deamon is not
launched)
- on Debian, the owner is changed by the rc script (it overrides the
changeowner directive in icecast.xml)

Would you help me to find it out?
I paste you the conf file (passwords are fake :-) )...

<icecast>
    <limits>
        <clients>100</clients>
        <sources>2</sources>
        <threadpool>5</threadpool>
        <queue-size>102400</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>10</source-timeout>
        <burst-on-connect>1</burst-on-connect>

        <burst-size>65535</burst-size>
    </limits>
    <authentication>
        <!-- Sources log in with username 'source' -->
        <source-password>xxxxxx</source-password>
        <!-- Relays log in username 'relay' -->
        <relay-password>xxxxx</relay-password>
        <admin-user>xxxxxx</admin-user>
        <admin-password>xxxxxx</admin-password>
    </authentication>
    <directory>
        <yp-url-timeout>15</yp-url-timeout>
        <yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url>
    </directory>
    <hostname>mail</hostname>
    <listen-socket>
        <port>8000</port>
        <!-- <bind-address>127.0.0.1</bind-address> -->
    </listen-socket>
    <!--
    <relay>
        <server>127.0.0.1</server>
        <port>8001</port>
        <mount>/example.ogg</mount>
        <local-mount>/different.ogg</local-mount>

        <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    </relay>
    -->
    <fileserve>1</fileserve>
    <paths>
                <!-- basedir is only used if chroot is enabled -->
        <basedir>/usr/share/icecast2</basedir>

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

    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <!-- <playlistlog>playlist.log</playlistlog> -->
        <loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
    </logging>

    <security>
        <chroot>0</chroot>
    </security>
</icecast>
-- 
ASPO Infog?rance       http://aspo.rktmb.org/activites/infogerance
Unofficial FAQ fcolc   http://faq.fcolc.eu.org/
LUG sur Orl?ans et alentours.
T?l : 02 38 76 43 65 (France)



From Dennis at Heerema.net  Thu Dec 30 23:22:43 2004
From: Dennis at Heerema.net (Dennis Heerema)
Date: Fri, 31 Dec 2004 00:22:43 +0100
Subject: [Icecast] icecast2.2 and aac?
In-Reply-To: <20041230050339.92360.qmail@web60209.mail.yahoo.com>
References: <20041230050339.92360.qmail@web60209.mail.yahoo.com>
Message-ID: <41D48DC3.90905@Heerema.net>

Hi All,

Got today the Orban Opticodec-PC encoder LE and it sounds great at 
32Kbps and 44.1Khz and even lower it sounds great!!
Now even people with dial-up can listen to FM quality streams!

Got a test stream up, if you're intrested, with some rights free (RIAA 
free) music (dutch language made by a friend of mine).

http://dir.xiph.org/index.php?sgenre=&stype=&search=doosfm

there are some more users in the yp dir:

http://dir.xiph.org/index.php?sgenre=&stype=&search=aac

Regards,

Dennis Heerema



qiang Bao schreef:

>
>
> */Dennis Heerema <Dennis at heerema.net>/* wrote:
>
>      
>     Regards,
>
>     Dennis Heerema
>
>         -----Original Message-----
>         From: "Greg J. Ogonowski" <greg at orban.com>
>         To: qiang Bao <jakobao at yahoo.com>, icecast at xiph.org
>         Date: Wed, 29 Dec 2004 11:08:04 -0800
>         Subject: Re: [Icecast] icecast2.2 and aac?
>
>         Icecast 2.2 works fine with AAC/aacPlus at any bitrate.
>
>         32kbps here:
>
>         http://stream.orban.com:80/eval
>
>         <http://stream.orban.com/eval>-greg.
>
>
>
>         At 00:21 2004-12-29, qiang Bao wrote:
>
>>         it seems that icecast 2.2 can only stream aac at 128kbps!
>>          
>>         mp3 and ogg are ok at all bitrates.
>>          
>>         is it a bug or my config wrong?
>>
>>
>>          
>>
>>         I mean that icecast stream aac at constant bitrate which is
>>         128.    128kbps  32KHz
>>
>>         it can stream at 32KHz 44.1KHz 48Khz,i know that.
>>
>>          
>>
>>         I want to know how to make it stream at other bitrates?
>>
>>         and which source support HE-AAC?
>>
>>         Thank you for your work!
>>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! Mail - Easier than ever with enhanced search. Learn more. 
> <http://us.rd.yahoo.com/evt=29916/*http://info.mail.yahoo.com/mail_250> 


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

From geoff at hitsandpieces.net  Fri Dec 31 00:16:33 2004
From: geoff at hitsandpieces.net (Geoff Shang)
Date: Fri, 31 Dec 2004 10:16:33 +1000
Subject: [Icecast] XML parsing error I can't find
In-Reply-To: <1104390504.649.30.camel@ngeza>
References: <1104390504.649.30.camel@ngeza>
Message-ID: <Pine.LNX.4.61.0412311015240.1178@data.home>

Hi:

Can't see any problems.  The only thing I can think of is maybe your actual 
config file has some funky passwords in it that the XML parser doesn't 
like.  Have you tried parsing the file exactly as you sent it to us?

Geoff.


-- 
Geoff Shang <geoff at hitsandpieces.net>
Phone: +61-418-96-5590
MSN: geoff at acbradio.org

Make sure your E-mail can be read by everyone!
http://www.betips.net/etc/evilmail.html

Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html


From srbi24 at hotmail.com  Fri Dec 31 17:44:10 2004
From: srbi24 at hotmail.com (Scott Baker)
Date: Fri, 31 Dec 2004 09:44:10 -0800
Subject: [Icecast] Icecast not streaming from playlist. (Newbie)
Message-ID: <BAY103-F14270C5D6BFFB8FEB41523C39D0@phx.gbl>

Hi all,
I'm new to the streaming audio thing, but have been a linux user for 7 or 8 
years.  Here's some background:

I work in a really EMI-nasty environment that prevents receiving radio 
broadcasts. In order to listen to sporting events, local news, etc. I 
planned to set up icecast to stream live audio snatched from a radio at 
home, and listen to it at work.

I installed icecast, libshout, etc. on my linux box at home without any 
problem. I also installed ices-0.4 and ices 2 so I could do ogg and mp3 data 
types. I have lame, xmms, , libogg and liborvis (or whatever the libraries 
are called). I'm connected via a 256kb DSL line at home and several T1s at 
work.

To test my setup, I created playlists. One uses mp3s and one uses ogg files. 
both ices versions point to their respective playlists and start up OK.

The problem occurs in both MP3 and ogg "streams".   My browser sees the 
mountpoints and connects to them, but the all systems I've tried to connect 
from (A windows box and 2 Sun stations) insist on downloading the entire 
contents of the playlist before playing anything. For example, my mp3 
playlist has ~100 songs in it. When I connect to the mountpoint, the system 
wants to download all 100 songs before it will begin playing. The way it's 
set up now, I might as well just place my music files on the Apache server 
and play them one at a time. It is not streaming the audio. Thus, I have not 
yet tried ices-live.

I've been through all the READMEs, docs, and read several mailing lists. Am 
I missing something stupid here?

Thanks,
Scott




From mail at dwipal.com  Fri Dec 31 21:02:03 2004
From: mail at dwipal.com (Dwipal Desai)
Date: Fri, 31 Dec 2004 13:02:03 -0800
Subject: [Icecast] Live streaming from Mac OS X
Message-ID: <38AE6DBE-5B6F-11D9-9D2B-000A95A31EDA@dwipal.com>

I am trying to stream live audio from a Mac OS X ibook to a linux  
machine running mplayer2 using instructions
http://www.macosxhints.com/article.php? 
story=20020704134818926&query=live+itunes+streaming

I managed to compile everything (Icecast 2.2.0, libshout2, etc).
To compile icecast, i had to use "fakepoll.h" header file from  
sealiesoftware.com/fakepoll.h to get around with the poll.h errors on  
Mac OS X.

The command i am using to send stream to icecast server is:
esdrec | lame -b 128 - - | ./example
(Am example.c as it reads from stdin.)

The icecast server starts fine, libshout example file connects to the  
server, but it seems that the server is dropping the stream somewhere.  
I am basically not able to play the stream.

Dumping the output of lame to a file and playing it back again is  
working, so there is something with icecast.

Any suggestions on how to fix this ?

Below is the icecast error_log file:

  [2004-12-30 18:02:00] INFO main/main Icecast 2.2.0 server started
  [2004-12-30 18:02:00] WARN main/main YP server handling has been  
disabled
  [2004-12-30 18:02:00] INFO stats/_stats_thread stats thread started
  [2004-12-30 18:02:00] INFO fserve/fserv_thread_function file serving  
thread started
  [2004-12-30 18:02:01] DBUG slave/_slave_thread checking master stream  
list
  [2004-12-30 18:02:13] INFO connection/_handle_source_request Source  
logging in at mountpoint "/radio.mp3"
  [2004-12-30 18:02:13] DBUG connection/connection_complete_source  
sources count is 0
  [2004-12-30 18:02:13] DBUG connection/connection_complete_source  
source is ready to start
  [2004-12-30 18:02:13] DBUG source/source_init Source creation complete
  [2004-12-30 18:02:13] DBUG stats/modify_node_event update node  
connections (1)
  [2004-12-30 18:02:13] DBUG stats/modify_node_event update node  
source_client_connections (1)
  [2004-12-30 18:02:13] DBUG stats/process_source_event new source stat  
/radio.mp3
  [2004-12-30 18:02:13] DBUG stats/process_source_event new node public  
(0)
  [2004-12-30 18:02:13] DBUG stats/process_source_event new node  
listenurl (http://192.168.2.10:8000/radio.mp3)
  [2004-12-30 18:02:13] DBUG stats/modify_node_event update node sources  
(1)
  [2004-12-30 18:02:13] DBUG stats/modify_node_event update node  
source_total_connections (1)
  [2004-12-30 18:02:13] DBUG stats/process_source_event new node  
listeners (0)
  [2004-12-30 18:02:13] DBUG stats/process_source_event new node  
server_name (no name)
  [2004-12-30 18:02:22] DBUG connection/_handle_get_request Source found  
for client
  [2004-12-30 18:02:22] DBUG source/source_main Client added
  [2004-12-30 18:02:22] INFO source/source_main listener count on  
/radio.mp3 now 1
  [2004-12-30 18:02:22] DBUG stats/modify_node_event update node  
connections (2)
  [2004-12-30 18:02:22] DBUG stats/modify_node_event update node  
client_connections (1)
  [2004-12-30 18:02:22] DBUG stats/modify_node_event update node clients  
(1)
  [2004-12-30 18:02:22] DBUG stats/modify_node_event update node  
listeners (1)
  [2004-12-30 18:02:24] DBUG source/get_next_buffer last 1104458533,  
timeout 10, now 1104458544
  [2004-12-30 18:02:24] WARN source/get_next_buffer Disconnecting source  
due to socket timeout
  [2004-12-30 18:02:24] INFO source/source_shutdown Source "/radio.mp3"  
exiting
  [2004-12-30 18:02:24] DBUG source/source_clear_source clearing source  
"/radio.mp3"
  [2004-12-30 18:02:24] DBUG format-ogg/format_ogg_free_headers  
releasing header pages
  [2004-12-30 18:02:24] DBUG format-ogg/free_ogg_codecs freeing codecs
  [2004-12-30 18:02:24] DBUG source/source_free_source freeing source  
"/radio.mp3"
  [2004-12-30 18:02:24] DBUG stats/modify_node_event update node sources  
(0)
  [2004-12-30 18:02:24] DBUG stats/process_source_event delete source  
node /radio.mp3
  [2004-12-30 18:02:24] DBUG stats/modify_node_event update node clients  
(0)

  Thanks in advance !
  Dwipal



From wb8erj at hotmail.com  Fri Dec 24 07:11:22 2004
From: wb8erj at hotmail.com (M T)
Date: Fri, 24 Dec 2004 02:11:22 -0500
Subject: [Icecast] Icecast RPM for Fedora Core 3
Message-ID: <BAY101-F423EC3B98889650580561A9FA60@phx.gbl>

Hello,

I would love to help out! I have downloaded your rpm on to my freshly 
installed Fedora core 3 machine.

I do have some questions though, I was wondering if you coule please email 
me direct. Once I get things straightend out, I will gladly post on the 
list..

           -- Mike

     WVMC FM
Mansfield, Ashland, Willard, Ohio
  http://www.wvmcfm.com




From umar at natrix.wcrb.com  Mon Dec 27 19:52:15 2004
From: umar at natrix.wcrb.com (Rob Landry)
Date: Mon, 27 Dec 2004 14:52:15 -0500 (EST)
Subject: [Icecast] Icecast 2.2.0 and Ices2: no audio
In-Reply-To: <1103853461.9035.5568.camel@bogus.hackers.club>
References: <20041223125202.C32217@natrix.wcrb.com>
	<1103853461.9035.5568.camel@bogus.hackers.club>
Message-ID: <20041227145038.H31152@natrix.wcrb.com>


On Thu, 24 Dec 2004, Karl Heyes wrote:

> On Thu, 2004-12-23 at 18:11, Rob Landry wrote:
> ...
> > When I look at http://192.168.0.128:8000/status.xsl, everything looks ok.
> > But when I click on "Click to listen", it brings up xmms, but there's no
> > indication of audio, and xmms shows a bit rate of 1 kbps.
> >
> > This is a machine that formerly ran icecast 1.3 and liveice under OpenBSD
> > 2.8, so I know the hardware is OK.
>
> what are you capturing, probably silence based on those figures. check
> your mixer settings

I ran alsamixer; it says I'm capturing "Line", which is the correct input.

Are there any other settings I should check?

Thanks,


Rob Landry



From coffeehouseprivate at hotmail.com  Wed Dec 29 07:46:33 2004
From: coffeehouseprivate at hotmail.com (All al)
Date: Wed, 29 Dec 2004 02:46:33 -0500
Subject: [Icecast] Help! I have a question about configuration of icecast
	and oddcast
Message-ID: <BAY24-F375FC02BD98CC1A6F7DC7BCA9B0@phx.gbl>

Hey,

I want to broadcast my music with the p2p program, but I in the processing 
to configuring my utilities such oddcast. I am behind a router and when I 
try to connect
Oddcast I keep getting the message ?unable to connect to socket?. What the 
heck does that mean? I think it has to do something with UDP and TCP, but I 
don?t know which one to choose when I?m port forwarding it from my router. 
Also should I use ?localhost? or the router IP address in the icecast.xml 
file, which would then be directed to my laptop. Please help, I want to 
share my music so badly, and will try anything!!!!!

Please give me instructions on it, from the ?what to do if you are behind 
the router point of view?.

Sincerely,

Silviu Teseleanu

P.S. my website is www.freewebs.com/tranc3energy
Check it out

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/



From al.owns at ntlworld.com  Thu Dec 30 00:31:09 2004
From: al.owns at ntlworld.com (Alex Jones)
Date: Thu, 30 Dec 2004 00:31:09 +0000
Subject: [Icecast] Ices and ALSA / OSS
In-Reply-To: 200406291707.i5TH7rkE015429@krazykat.nc.rr.com
Message-ID: <1104366669.14654.8.camel@flashpoint.lakeside.weej.net>

Hello Karl

In reference to:
http://lists.xiph.org/pipermail/icecast/2004-June/007473.html

I am also receiving this error with an M-Audio Audiophile 2496 device
running with the ice1712 ALSA module. I've not quite figured out how to
test it with a hw pcm because it isn't accepting any of my formats. I've
no idea how ALSA's plug opens it but I've tried all the obvious ones,
(2x96000xS24_LE, 2x44100xS16_LE included) but I'm at a loss. However,
this period thing is preventing me from being able to use my card with
ices.

If it's any help and in case you don't already know, the card is 24 bit
and 96000 Hz by default.

I look forward to your reply, and many thanks in advance.

Alex Jones
al.owns at ntlworld.com



From jakobao at yahoo.com  Fri Dec 31 13:48:12 2004
From: jakobao at yahoo.com (qiang Bao)
Date: Fri, 31 Dec 2004 05:48:12 -0800 (PST)
Subject: [Icecast] icecast2.2 and aac? 
Message-ID: <20041231134812.72940.qmail@web60201.mail.yahoo.com>


below is what i have talked about with Dennis Heerema.

but we didn't get the way.
 
anyone can help me??
 
thanks??
Thank you for explaining this patiently.
BUt i think you still don't understand what i said.
I just want to know why the icecast stream aac at a constent 128kbit/s  ?
 
i know i can use Orban opticodec or other sourec clients.
 
now my source client is oddcast.
 
it can stream aac at all bitrates(32-448 kbps) and frequency(32Khz 44.1Khz 48Khz).
 
now icecast receives aac data that is 200kbps(or any other bitrates)  from source client but only streams it at 128Kbps. 
 
i don't know why.
 
there is a picture in attachment to describe this status.
 
i have listened to the station on icecast site(http://dir.xiph.org/index.php?sgenre=&stype=&search=aac) and  they are all streaming at 128kbps!!!!!!
 
i mean that icecast stream aac at constant bitrate which is 128.    128kbps  32KHz






		
---------------------------------
Do you Yahoo!?
 All your favorites on one personal page ? Try My Yahoo!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041231/6f3bd0e4/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ??????2.JPG
Type: image/pjpeg
Size: 88491 bytes
Desc: ??????2.JPG
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20041231/6f3bd0e4/attachment.bin>