Icecast Streaming Media Server

[Anonymous]

Hi guys,

I have been enjoying the use of icecast for some time now and with great success. Recently I migrated from using MP3 files to aacPlus, so that the output bandwidth can also be received by my mobile phone (need to use my flat-rate data plan ).
The only problem right now is that it won't play the introduction file anymore. THe introduction file has been transcoded to the same format as the stream (48kb/s stereo 44100) and resides in the directory /introSound/intro.aac above the <web-root>-directory.
I am able to play the file by calling it directly and winamp gives no errors and the logs are ok, but when using the file as an intro file it fails....

Can anyone help me with this?
Appreciate it...7

MOUNT INFORMATION

[karlH]

If the intro file option is really set (we can only guess) then you should see the entry mentioned in the error log (even if it fails to open).

karl.

[kozlov]

Is your file really compatible with your stream? You should check if file is compiled with use of MPEG-2 or MPEG-4, you shouldn't use Parametric Stereo (or even SBR) if your stream doesn't, you should take care about information tags... hm?
_________________
polska dokumentacja serwera Icecast2 / polish documentation of Icecast2

[Anonymous]

[Anonymous]

Here is a picture of my web-admin page stating the options that are present in the mount... As is seen, the intro options is set....

http://chicao82.multiply.com/photos/photo/10/46

[karlH]

ok, your icecast xml is generated but that doesn't help us determine much. Your access log does indicate that icecast finds the /introSound/intro.aac file in webroot. You should see a message at level 4 (DBUG) in the error log saying something like

[....] DBUG ... intro file is ....

or maybe a

.... Cannot open intro file

Neither of which has been confirmed or denied

karl.

[Anonymous]

Tnx for trying to help me out guys.

I'll try to post some more info, here is the code generated in the error.log when the mount is first set-up, I think the problem is originating here, I don't get any messages stating that the intro cannot be opended when a client connects to the stream, I get no messages at all, that's why I think libshout specifies an incorrect format for the <intro> field.... could anyone check into this?
Currently using the format intro= in the <audio_info> field, I already tried to set it up like the bitrate (ice-intro=....) but that does not even show an intro node on the admin page. I think this is the problem, but I cannot find any source code containing how to setup the intro file on the fly. I checked libshout, ezstream, darkice, icegenerator and liquidsoap... but none specify the format.....

Correct me if I am wrong, but I think i am just defining the format wrong, anyone knows how to do it right in the HTTP-request originating from the source?

[karlH]

ah, I see what you are doing. No the intro file setting is in the icecast xml, it is not supplied by the source client. Intro files are only specified by the icecast server because they can apply to both relays and source clients. If you are regenerating the icecast xml then that is where you should add the intro file setting.

I don't think that libshout is aac aware. It can certainly send through aac data but it does no timing (shout_sync) and the content type may very well be limited to ogg and mp3. I haven't heard of anyone doing aac via libshout. Resolving the content type part should be easy enough but timing requires detailed knowledge of the format.

karl

[Anonymous]

Doing aac via libshout is already built by me;) Timing is built into the encoder, I can set it to real-time streaming, so just sending it as raw data to icecast through libshout works.
Streaming works normally, only problem was the intro file, but I am using random mount-point names, so is there an option in the icecast.xml file where I can put an introfile for all the mount points that will be run upon the server??

[karlH]

There's no global/default option for it, it wasn't as useful due to the fact that in most cases with multiple mountpoints, they tend to use different formats and/or settings which would make a global intro file setting wrong in one or more cases. The per-mount <intro-file> setting is the what you need to set.

I don't know if it would be useful in your situation but you _could_ avoid the re-writing of the icecast xml by using my branch work (kh27 is latest). You can specify a mount-name like /*.aac and if you wanted to pass source client auth off to a php type script then you can do that via auth url using the stream auth option.

karl.

[Anonymous]

In this thread http://icecast.imux.net/viewtopic.php?t=1156 it is stated that setting:

[Anonymous]

Of course the xml

[karlH]