Icecast Streaming Media Server

[Anonymous]

I am running Fedora Core 6 that is current on all patches.
I have the following installed:
ices-2.0.1-4.fc6
icecast-2.3.1-3.fc6
lame-3.97-1.fc6 (not sure if I really needed this installed but I was trying everything)

I have no problems streaming ogg files, they work like a charm. In fact, I have 3 streams running right now. A classical, jazz and a rock and roll for different portions of the house.

Now I am trying to stream an mp3 file as an introduction to our homepage. I chose mp3 because none of my relatives who visits our homepage uses linux. No matter how much I argue with them I have been unable to turn them from the dark side. And if I did I wouldn't have anything to argue with them about.

The log file fills up with these errors:

[2007-03-10 13:59:58] INFO playlist-builtin/playlist_read Currently playing "/etc/ices/a.mp3"
[2007-03-10 13:59:58] WARN playlist-builtin/playlist_read Corrupt or missing data in file (/etc/ices/a.mp3)
[2007-03-10 13:59:58] INFO playlist-builtin/playlist_read Currently playing "/etc/ices/b.mp3"
[2007-03-10 13:59:58] WARN playlist-builtin/playlist_read Corrupt or missing data in file (/etc/ices/b.mp3)

The files exist, they are not corrupt as far as I can see, I have used id3v2 to add the metadata to them. Xine can play them and does not complain about them being corrupt.

Here is the configuration file I am using for ices:

ices-mp3.xml
<-- snip -->
<?xml version="1.0"?>
<ices>
<!-- run in background -->
<background>1</background>
<!-- where logs, etc go. -->
<logpath>/var/log/ices</logpath>
<logfile>ices.log</logfile>
<!-- 1=error,2=warn,3=info,4=debug -->
<loglevel>4</loglevel>
<!-- set this to 1 to log to the console instead of to the file above -->
<consolelog>0</consolelog>

<!-- optional filename to write process id to -->
<!-- <pidfile>/home/ices/ices.pid</pidfile> -->

<stream>
<!-- metadata used for stream listing (not currently used) -->
<metadata>
<name>Example stream name</name>
<genre>Example genre</genre>
<description>A short description of your stream</description>
</metadata>

<!-- 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. -->

<input>
<module>playlist</module>
<param name="type">basic</param>
<param name="file">mp3.txt</param>
<!-- random play -->
<param name="random">0</param>
<!-- if the playlist get updated that start at the beginning -->
<param name="restart-after-reread">0</param>
<!-- if set to 1 , plays once through, then exits. -->
<param name="once">0</param>
</input>

<!-- 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 different
mountpoints on the same server). Each of them can have different
parameters. This is primarily useful for a) relaying to multiple
independent servers, and b) encoding/reencoding to multiple
bitrates.
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. -->
<instance>
<!-- Server details:
You define hostname and port for the server here, along with
the source password and mountpoint. -->
<hostname>localhost</hostname>
<port>8000</port>
<password>xxxxxxxxx</password>
<mount>/test.mp3</mount>

<!-- 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 value
if you do this.
-->
<reconnectdelay>2</reconnectdelay>
<reconnectattempts>5</reconnectattempts>

<!-- maxqueuelength:
This describes how long the internal data queues may be. This
basically lets you control how much data gets buffered before
ices decides it can't send to the server fast enough, and
either shuts down or flushes the queue (dropping the data)
and continues.
For advanced users only.
-->
<maxqueuelength>80</maxqueuelength>

<!-- 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.
-->
<encode>
<nominal-bitrate>64000</nominal-bitrate> <!-- bps. e.g. 64000 for 64 kbps -->
<samplerate>44100</samplerate>
<channels>2</channels>
</encode>
</instance>

</stream>
</ices>
<-- snip -->

My mp3.txt file with the names of the mp3 files:
<-- snip -->
/etc/ices/a.mp3
/etc/ices/b.mp3
<-- snip -->

I call everything like this:
cd /etc/ices
ices ices-mp3.xml

That is when the errors start.

All help is greatly appreciated!!!

[karlH]

It is well understood that ices2 cannot read mp3, patent licensing for mp3 is a continuing problem. ogg is not a linux only codec, if you really want to handle audio from a web page then use use a java applet like cortado.

karl.

[MoeRadio.ru]

Or you can also install ices0, which handles mp3. I have FC 6 as well and just found this rpm today: