[icecast] ices2 and Icecast2 on debian configuration question
davidmarceau at sympatico.ca
Tue Jun 1 13:28:32 PDT 2004
I have a Debian sarge 512 MB RAM machine with icecast2 and ices2 that I
installed via aptitude. I have a 3MBit/s download and 800KBit/s upload
I would like to configure icecast2 and ices2 properly.
Here is my situation:
1)I have a dtdns address omac.darktech.org
2)icecast2 and ices2 on port 8000 would be fine.
3)I simply want to broadcast my 6 year old niece's voice which I have
converted to .ogg using the blade encoder.
i.e. bladeenc elyse4.wav elyse4.ogg
3.3)I don't seem to need a relay since I am running both icecast2 and
ices2 on the same machine.
4)I ran ices2 ices-playlist.xml
5)I ran icecast2 -c icecast.xml
6)I went to my brother's machine who uses another internet provider and
uses a windows ME box(non-techie guy). I did
7)Instead of delivering elyse4.ogg as a stream, it seemed to deliver the
entire file before it played it in winamp.
8)I didn't quite configure everything properly because I was unsure as
to what the playlist.txt file should contain. I guessed and only placed
"elyse4.ogg" in it.
1)What do I have to change in my ices2 and icecast2 configs in order for
it to stream instead of doing a complete file transfer?
2)What is the execution order for ices2 and icecast2. Should I start
ices2 first and then icecast2 or do icecast2 first and then ices2
second? I am guessing it should be icecast2 first but the documentation
does not seem to tell me that.
3)Since I am running both ices2 and icecast2 on the same machine, do I
still need a user password for ices2 and icecast2 to communicate to each
4)Considering my 800KBit/s upload bandwidth, what would be the
recommended maximum number of listeners that I could stream? I am
guessing that 800Kbit/64= 12...roughly twelve 64Kbit streams. Is this
the correct method or is there more that I should consider here? I am
guessing there is but it's best to ask right?
Thanks for taking the time to help.
Here are my icecast2 and ices2 xml config files:
<!-- Sources log in with username 'source' -->
<!-- Relays log in username 'relay' -->
<!-- Admin logs in with the username given below -->
<!-- Uncomment this if you want directory listings -->
<!-- You can use these two if you only want a single listener -->
<!-- You may have multiple <listener> elements -->
<!-- <bind-address>127.0.0.1</bind-address> -->
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords
<!-- basedir is only used if chroot is enabled -->
<!-- Note that if <chroot> is turned on below, these paths must
be relative to the new root, not the original root -->
<!-- Aliases: treat requests for 'source' path as being for
May be made specific to a port or bound address using the
and "bind-address" attributes.
<alias source="/foo" dest="/bar"/>
<loglevel>0</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<!-- run in background -->
<!-- where logs, etc go. -->
<!-- 1=error,2=warn,3=info,4=debug -->
<!-- set this to 1 to log to the console instead of to the file
<!-- optional filename to write process id to -->
<!-- <pidfile>/home/ices/ices.pid</pidfile> -->
<!-- metadata used for stream listing (not currently used) -->
<genre>talking and singing</genre>
<description>debut internet radio appearance</description>
<!-- input module
The module used here is the playlist module - it has
'submodules' for different types of playlist. There are
two currently implemented, 'basic', which is a simple
file-based playlist, and 'script' which invokes a command
to returns a filename to start playing. -->
<!-- random play -->
<!-- if the playlist get updated that start at the
<!-- if set to 1 , plays once through, then exits. -->
<!-- Stream instance
You may have one or more instances here. This allows you to
send the same input data to one or more servers (or to
mountpoints on the same server). Each of them can have
parameters. This is primarily useful for a) relaying to
independent servers, and b) encoding/reencoding to multiple
If one instance fails (for example, the associated server goes
down, etc), the others will continue to function correctly.
This example defines two instances as two mountpoints on the
same server. -->
<!-- Server details:
You define hostname and port for the server here, along
the source password and mountpoint. -->
<!-- Reconnect parameters:
When something goes wrong (e.g. the server crashes, or the
network drops) and ices disconnects from the server, these
control how often it tries to reconnect, and how many times
it tries to reconnect. Delay is in seconds.
If you set reconnectattempts to -1, it will continue
indefinately. Suggest setting reconnectdelay to a large
if you do this.
This describes how long the internal data queues may
basically lets you control how much data gets buffered
ices decides it can't send to the server fast enough, and
either shuts down or flushes the queue (dropping the data)
For advanced users only.
<!-- Live encoding/reencoding:
Currrently, the parameters given here for encoding MUST
match the input data for channels and sample rate. That
restriction will be relaxed in the future.
<nominal-bitrate>64000</nominal-bitrate> <!-- bps. e.g.
64000 for 64 kbps -->
--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the Icecast