Icecast Streaming Media Server

[comedown]

Hi guys,

at the end i decided to use a Win2k3 server for my IceCast2 installation.

Now i have IceCast2 + Winamp + EdCast on my windows vps.

When i'm streaming from the playlist all works fine.

The problem is when i need to stream from my pc. Icecast doesn't allow more than one source for each mountpoint so, before connecting to the server from my pc i need to stop edcast on the server. This works very fine.

But i need to do this automatically, whit the windows scheduler. Practically i need to disconnect the local source (killing the process, banning the source i dont know) to make possible to the remote source to connect.

The only idea i have at the moment is to kill the edcast process and then restart it (it will try to connect to the server every 5 seconds, and it will connect only when i stop streaming from my pc).

Any other advice? Can i disconnect (and reconnect) a source client from IceCast?

I think i can also connect from my pc to another mountpoint and then move listeners to it, but i dont think that's a good idea.

Thanks.

[karlH]

If you don't want to use a fallback to move listeners then use a simple 3 mountpoint setup. An example of this is if you want the a mountpoint to still register on the directory. eg A is what the listeners connect to, B is what one source client connects on and C is what the other source client connects on.

A is a relay of the always on mountpoint eg C
B fallback overrides C

A becomes a copy of C until you connect on B, at which point A become a copy of B. Whether you stop C when B is active is up to you.

karl.

[comedown]

Thanks KarlH.

I'm sorry for my coninuos questions, but i think i'm working on something that nobody have ever used before. I think i'll write down a tutorial for other users whic wants to create a webradio only with free software in windows (in linux it's the simpliest thing i've ever done).

I can't understand very well your solution. Can you please give me the config.xml file?

Thankyou

Ps: Yesterday evening i've found another solution: i can simply kill the source from the IceCast2 Web Interface and before the playlist source reconnects to the server i can connect from my pc to the mount point. Anyway, that's not a so good idea.

EDIT: Ok i've tried whit this configuration but it doesn't seems to be working.

[comedown]

UP

[karlH]

The relay doesn't see the new http details over fallback as those only occur at the initial connection. The only way at the moment is to restart the relay connection to get new headers but that won't fit in well to the setup described. In theory the association between the streams could be defined better for local relay case allowing for those http details to be transferred easily but that isn't currently available.

karl.

[comedown]

Ok, this is not a big problem.

Can i force stream data to the relay as i do with mount point?

[karlH]

mount definitions apply to relays as they do with source clients

karl.

[comedown]

So the relay has to take stream name and description from the mp that's relayng, but it seems not to be working...

[karlH]

As I've already said, the stream name and description that is sent to listeners of the relay is only provided when the relay connects, they don't get any updates mid stream (think http header updates mid-download of a file). The mount settings for those details are for directory and stats and where introduced to deal with inactive on demand relays not as an override of source client content. I've said as well that if the stream name/description is to update then there needs to be a closer tie in but that has issues for directory updates.

karl.

[comedown]

[karlH]

The 2 usual reasons for this are typo (that looks ok though) or not defined. The not not defined case could be down a mountpoint name mismatch or commented out <mount> section. loading the xml into a browser should help to identify commented sections.

karl.

[comedown]

I haven't any mount section for my listen.mp3 relay.

Do i also have to create a mountpoint whit the same name of the relay local-mountpoint?

[karlH]

max-listeners is a <mount> setting, not a <relay> setting.

karl.

[comedown]

Yes i know.

So, how can i limit relay's listeners?

[karlH]

as I've already said, mount setting apply to both relays and source clients amd ,ac listeners is a mount setting so define a mount section for the local mount for the relay and specify the max listeners in that.

karl.