Icecast Streaming Media Server

[Anonymous]

Hi,

I have defined a <fallback-mount> to an aacplus-file:

<mount>
<mount-name>/Streamname24k-aac</mount-name>
...
<fallback-mount>/Offline24k.aac</fallback-mount>
...
</mount>

If the player send the stream-request to the Icecast-Server (2.3.1) and the stream is offline (no source), the fallback-mount-file should be sent to the player. The problem is, that Icecast write the wrong content-type to the HTTP-Header:

Content-Type: application/octet-stream

instead of

Content-Type: audio/aacp

This happens only, if there is no source contect to Icecast!

The effect is, that Winmap do not play the stream because of the wrong content-type. What can I do?

[karlH]

It will the first time I've heard of winamp using the mime type. Can you clarify that the requested mountpoint does not end in .aac

<mount-name>/Streamname24k-aac</mount-name>

karl.

[Anonymous]

Yes, the mount-point/name is named "/Streamname24k-aac" and NOT "/Streamname24k.aac".

If the source is sending data to this mount-name, Icecast answers with "Content-Type: audio/aacp" and reduce the sendingspeed according to the bitrate of this stream. Winamp is playing the stream.

If the source is not connected to Icecast (=the mount-point is offline), Icecast answers with "Content-Type: application/octet-stream" and send the data of the defined fallback-file (Offline24k.aac). This file has the ending .aac and contains aacplus-data. Icecast also do not reduce the sendingspeed. Winamp is receiving and receiving and play nothing.

I have an other mount-point defined for mp3. Here Icecast send always the correct content-type!

[karlH]

maybe you are missing the mime type, also your mountpoint should end with .aac not -aac.

karl.

[Anonymous]

I have renamed the mount-point to .aac and now Winamp is playing. The contect-type is still application/octet-stream.

Thank you for your support.

[karlH]

icecast uses mime types defined on your system, if the extension isn't matched then you get the application/octet-stream default.

karl.

[Anonymous]

Can you tell me, how I can chance/define the mine-type on my system (Windows 2003) ?

[karlH]

I don't know windows that well, checking the source it seems that the mime types file icecast looks for is in the current directory which is different from the unix one. Whether that is because of windows not having a common place for it I don't know, but edit a text file in the icecast directory and insert a line

audio/aacp .aac

karl.

[mobhaku]

Hi!

I have exactly the same problem and also use Icecast on Windows.
I tried to register the audio/aac type in the registry and added a mime and mime.types file in the main directory of icecast, but it doesn't help.
It seems to happen with aac-files, on-demand or as fall-back. With live-streams there is no problem, since the encoder decides which type it should be.
Does somebody know how we can tell icecast in Windows that a file with the extension .aac should be of the type audio/aac?
Thanks in advance and best regards,

Harreld

[karlH]

The windows build hasn't got the path right for win32. It's looking in the current directory instead of the install directory, so it depends on where you start it. That really needs fixing up along with the internal defaults. Can you report it on bugs.xiph.org if not already done so.

karl.

[mobhaku]