Icecast Streaming Media Server

[kewlkeed]

Hello all.

I am wondering what would be the better server to use in a multiple instance environment. I notice with shoutcast, as each server instance starts, it allocates the ram and CPU it needs to do the job and doesn't let them go (Even if nobody is on the stream). This makes it very machine intensive for streams that may not even be active.

Does Icecast allocate resources only as needed, or does it do the same thing as Shoutcast. I am looking at an environment where maybe only 50% of the streams will be active at any given point, so I'd like to do a bit of a "trunking" principle with the machine resources since most won't be in use all the time. I'd rather be able to run a few more instances with the notion that not ALL will be loaded at the same time. (yes it's oversubscription and nasty)

[karlH]

icecast only allocates resources when it needs them, whether it's for connecting clients or streams.

karl.

[kewlkeed]

Thanks!

I know this probably gets asked a million times... But is there a simple step by step guide to making icecast shoutcast compatable?

I find tips and stuff here and there, but there doesn't seem to be a comprehensive guide. I need the exact functionality as shoutcast, but the shoutcast server itself is terribly coded in its resource allocation.

I've tried to make this work, but I just keep running into problems. At this point I can now stream to the server but that's it, no listeners.

Because of the mount point issue (Which doesn't seem to even exist in shoutcast world)...

Should I be attempting to hook my source to xxx.xxx.xxx.xxx/mountpoint - on the port 8000
and my listeners to
xxx.xxx.xxx.xxx/mountpoint - on the port 8000
(Assuming I'm using port 8000 in the config)

[kewlkeed]

OK I answered my own question on how mount points work... And I have it successfully working.

BUT now my bigger question. DO I NEED mount points?

I would much rather have source on
xxx.xxx.xxx.xxx:8000
and listener on
htt://xxx.xxx.xxx.xxx:8000
without needing any /stream mounts etc. and with both source and listener on the same port (Exactly like shoutcast)

Is this possible?

[karlH]

For most people, who use the shoutcast style source clients, all you need is to set the <shoutcast-mount> setting in the listen-socket block. This will define the port N and N+1 that they need. As you have already indicated, players will just use the xxx:8000/mountpoint

karl.