Icecast Streaming Media Server

[Anonymous]

I'm familiar enough with Windows 2003 Server and another person set up Icecast server (2.2) on the box and we have the mount points for each DJ and our fallback but the old 'admin' said he's capped the stream at 64kbps... can this be changed by just changing the encoder info? I've looked through the XML files and am not sure if I can upgrade our stream to 96 or even 128 without re-installing Icecast (upgrading to 2.3). I plan to roll out 2.3 or even RC1 or RC2 as soon as I can learn enough about it and make the rollout a smooth transition (for instance, does the icecast config XML need changes?), but would like to be able to start 96KB streaming as soon as possible...

Thanks for helping out a newby!

Peave

Tom Wylde
Wylde Radio on
Cygnus Radio
http://www.cygnusradio.com

[MikeS]

You didn't mention what source client (the software that actually _creates_ the stream) you were using. That - since it creates the stream - is what decides on the bitrate.

Icecast itself has no way of limiting the bitrate of the streams it serves, currently, so no icecast changes should be needed to increase your stream bitrate. If you're bandwidth-limited, though, you might want to decrease the maximum allowed listeners.

Upgrading to a new version should not require any config changes.

Mike

[Guest]

Thanks Mike. Did a test at 96 and it worked great. Using SAM3 to run the encoders.

OK, next down time, the Icecast server gets upgraded.

Thanks much. I appreciate it a lot. I was mostly concerned with any upgrade issues or problems anyone's had since upgrading just so I know it'll only have a small downtime if I have to replace the older version first and old xmk files, etc.

Thanks a lot.

Peace

[Anonymous]

Upgraded to 2.3.1 and replaced the icecast config files and it will not find my original main mount point.

Help!


Thanks!

[karlH]

If something doesn't find the mountpoint then it's probably because the source client cannot stream on it. Check your xml config, the assword sent by your source client, and of course the error log.

karl.

[Anonymous]

I used the config file from 2.2 and when Icecast starts on the stream server, it automatically loads all the mountpoints listed in the config file... except the default mountpoint. But if I manually 'start' the icecast.xml or punch in the command line for my ezstream server or restart the Ice server and then start the auto, it will ONLY load the default, (but all other encoders will work) I'm using UServ and IceCast and the source clients are all SAM 3 Broadcaster from Spacial Audio with the encoders set at MP3/MP3Pro (and using MP3Pro).

All of our DJ mountpoints point to the default. There's a separate mount point for each and they stream by connecting obviously with the password to their own mount point that relays to the default mount.

Thinking there were no configuration changes and that it was an upgrade as opposed to a completely new version that wouldn't save the stats and reporting files much less the config file, I guess I have a lot of reading to do...

Thanks. I appreciate you help and patience with a newby here.

[Anonymous]

[karlH]

What do you mean by the default mountpoint? remember we haven't seen your xml file to know the exact configuration. It sounds like you have various mountpoints for your DJs and then this default mountpoint but we have no idea on how they interact. It could be a relay, or some of these could be set as fallback.

karl.

[Anonymous]

PM'd you my icecast.xml file, Karl. Thank you very much for having a look.

[Anonymous]

The separate DJ encoder info relays to the fallback file instead of the default cyg1_hi mount point now.

I'll PM you the ezstream xml file and IceCast admin page url. Let me know if there's more you need, Karl.

Can't tell ya how much I appreciate your help. If ya want, please feel free to bill me for your time and help.

peace.