gmax21
07-15-2008, 07:41 PM
I wasn't sure what forum to post this in, so apologies if it's in the wrong place.
I've seen a couple of posts regarding Icecast but nothing firm, will you be support Ice?
One of the features I love about icecast is mount point/fallback. You can have one mountpoint that listeners to connect to, you can then have DJ fallbacks and set their order which one takes priority.
1 Fallback could just have music ready to play when your DJ goes off air, whilst another one allows your DJ to come on-line without going straight to the main source. If you had to cut them off just use a point just connect in to the one with higher permissions.
I'm rubbish at explaining perhaps this post does more justice:
http://icecast.imux.net/viewtopic.php?t=4933&highlight=multiple
I have a basic goal I would like to accomplish with my icecast server. I would like a 24 hour stream going that will either be LIVE DJs (external source) or random track played from the server (local 24 hour stream). I'd also like this switching between LIVE and playlist be seamless to the listener. As I'm sure everyone else on here wants to accomplish the same thing I'd like your opinions on how to do this.
My approach:
mount A = 24 hour constant stream
mount B = DJ (external source)
Mount B has a fallback to A. So, this means that when a DJ cuts his/her stream off listeners will automatically be bounced to mount A with no interruption. So an external source cutting off situation seems to be easy enough but what about this ...
Mount A is a 24 hour source that will never be cut off so how can I get icecast to automatically switch over to the LIVE mount when an external source connects? I was thinking the script that is called for stream_auth could kill the 24 hour source connection which will then enable the fallback for the 24 hour mount. But then the mounts can't be unique for the DJs. To solve that issue maybe another icecast server is needed. This other icecast server will be a relay for DJs to connect to and then passed onto the mater icecast server which listeners will connect to.
if fallback override on mount B is enabled then any listeners on the fallback mount A will be moved when A starts up.
And the other question, when will your demo be ready to try on-line. I know I can download a copy for a few days, but if possible I'd rather not mess about in case this solution isn't for me, although from what I see it's everything I've ever for web radio.
I've seen a couple of posts regarding Icecast but nothing firm, will you be support Ice?
One of the features I love about icecast is mount point/fallback. You can have one mountpoint that listeners to connect to, you can then have DJ fallbacks and set their order which one takes priority.
1 Fallback could just have music ready to play when your DJ goes off air, whilst another one allows your DJ to come on-line without going straight to the main source. If you had to cut them off just use a point just connect in to the one with higher permissions.
I'm rubbish at explaining perhaps this post does more justice:
http://icecast.imux.net/viewtopic.php?t=4933&highlight=multiple
I have a basic goal I would like to accomplish with my icecast server. I would like a 24 hour stream going that will either be LIVE DJs (external source) or random track played from the server (local 24 hour stream). I'd also like this switching between LIVE and playlist be seamless to the listener. As I'm sure everyone else on here wants to accomplish the same thing I'd like your opinions on how to do this.
My approach:
mount A = 24 hour constant stream
mount B = DJ (external source)
Mount B has a fallback to A. So, this means that when a DJ cuts his/her stream off listeners will automatically be bounced to mount A with no interruption. So an external source cutting off situation seems to be easy enough but what about this ...
Mount A is a 24 hour source that will never be cut off so how can I get icecast to automatically switch over to the LIVE mount when an external source connects? I was thinking the script that is called for stream_auth could kill the 24 hour source connection which will then enable the fallback for the 24 hour mount. But then the mounts can't be unique for the DJs. To solve that issue maybe another icecast server is needed. This other icecast server will be a relay for DJs to connect to and then passed onto the mater icecast server which listeners will connect to.
if fallback override on mount B is enabled then any listeners on the fallback mount A will be moved when A starts up.
And the other question, when will your demo be ready to try on-line. I know I can download a copy for a few days, but if possible I'd rather not mess about in case this solution isn't for me, although from what I see it's everything I've ever for web radio.