Icecast Streaming Media Server

[Anonymous]

What's the best way to setup oddcast/icecast for live streaming via my line-in (which I have working fine already) and also static files for on-demand streaming. Would i define a separate <mount> section in my config file? Do I need Oddcast to serve the static files, or does Icecast just point people to the static .mp3 files in a specific dir on my system? I'm a little confused... Thanks!!
-Jon

[karlH]

Files that are downloaded from the server are placed under the directory specified as webroot in the xml. You don't gnerally use a mount for them unless you want listener authentication to apply.

karl.

[Anonymous]

Thanks for the reply Karl. So I simply place the static MP3 files in the directory specified as webroot in the xml? I do want authentication for them, as I have authentication for the live stream also. So I'll setup a Mount for them. That all there is to it? Do you have an example xml you can show me by chance?

[karlH]

we ship example xml files to show how things like this can be configured, most settings are completely optional but the mount name will be the reference you have for the file from webroot eg /myfile.mp3.

karl.

[Guest]

Thanks Karl. OK, I can stream the static files in "webroot" if I specify the file name in the URL on the listening PC. I want authentication to stream them, and I want them to show up in the browser on the first page (Icecast2 Status page) to make it easy to choose what I want to listen to. I tried setting up multiple mount points, but only the original stream.mp3 one shows up. The first mount is my live stream, and the second one is a static file called todays_show.mp3 in the webroot. Here's my config file:

<icecast>
<limits>
<clients>100</clients>
<sources>2</sources>
<threadpool>5</threadpool>
<queue-size>524288</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>
<source-password>*removed*</source-password>
<relay-password>*removed*</relay-password>
<admin-user>admin</admin-user>
<admin-password>*removed*</admin-password>
</authentication>
<hostname>*removed*</hostname>
<listen-socket>
<port>8000</port>
</listen-socket>
<mount>
<mount-name>/stream.mp3</mount-name>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="1"/>
</authentication>
</mount>
<mount>
<mount-name>/todays_show.mp3</mount-name>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="1"/>
</authentication>
</mount>
<fileserve>1</fileserve>
<paths>
<basedir>./</basedir>
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<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>
</security>
</icecast>

[karlH]

while static files can have authentication applied to them via <mount>, they don't get expanded via the stats (and therefore in the xsl), you can of course hard code any names you want within the xsl files themselves but for xsl expansion it would require some sort of selection mechanism and that hasn't been discussed yet.

karl.