| View previous topic :: View next topic |
| Author |
Message |
Anonymous Guest
|
Posted: Sun Apr 06, 2008 12:55 am Post subject: I don't know if my idea can work |
|
|
Hi,
i have one problem and i don't know how to fix it, or if it is generally possible.
Also my english is not so good to understand everything what is written here.
Ok, now my problem or the scenario:
One DJ is connected to IceCast Server and the mount point is e.g. Club1.
Now i would like to connect a second DJ to the same mount point at the same time so they can do a good hand over from one show to the next one.
The second idea is as followed:
DJ 1 is connected to mount point Club1.
DJ 2 is connected to mount point Club2.
The listeners should be connected to Mountpoint Club.
Now the DJ's should relayed from Club1 and Club2 to Club at same time.
The result (2 DJ on one stream at same time) should be the same.
Can somebody help me if this is possible or have somebody another idea to solve this problem.
IceCast Version 2.3.1 is used.
Best regards
Peter |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Apr 06, 2008 1:11 am Post subject: |
|
|
You mean mixing the streams. No, icecast cannot do that as it only sees the compressed data stream. You would need to decompress the stream and then find some way of identifying how to sync up the 2 streams.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sun Apr 06, 2008 2:35 am Post subject: |
|
|
Hi Karl,
thanks for quick reply.
Also i find out that it isn't possible what i want (or not with the tools we have).
So my other idea is (as i found some threads) to do as followed:
Listener behind Relay One
Relay One: Mount /Playlist (will override from DJ's)and Mount DJ's
Relay Two: Mount /DJA (Fallback is DJB) and Mount /DJB (Fallback is DJ A)
So what should happend:
If no DJ is connected the Playlist will send Audiodata. At the moment one DJ (A) will connected the Playlist will be overwritten and the DJ will send the datas.
Now my idea is: DJ (B) can connect to B and is like a standby (because it will not automatically swapped from A (only fallback). At the moment the DJ A will disconnect the relay will swap to DJ B and he send the datas.
Now DJ A again can prepare and if DJ B is disconnected it will swapped back.
This all happen at relay two.
At the moment no DJ is streaming anymore the Relay One should swap back to Playlist.
On more question. If it possible to do a multiple fallback? E.g. 12 DJ'S at station. If 1 is not present 2 will checked. If 2 is not present 3 will checked and so on? So at least all DJ's have an own mount name.
Sounds strange, but i think it isn't or?
Did you mean that this could work?
Thanks
Peter |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Apr 06, 2008 1:13 pm Post subject: |
|
|
Only one fallback can be configured per mount although they can cascade A to B to C but I would avoid fallback loops if you can.
The usual setup I'd recommend for handling multiple DJ switchover is a mountpoint from a playlist (eg /playlist), a mountpoint for each DJ (eg DJ-A,B,C...etc) each configured to fallback/override to /playlist and a relay mountpoint for your listeners (eg /live) configured to read from /playlist. DJ-A connects and takes the relay from /playlist, when finished it puts it back and then another DJ can connect.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sun Apr 06, 2008 3:25 pm Post subject: |
|
|
Uggh,
that sounds complicate for a noob like me. But you it is to say...try and error.
So i will find out how to condigure the mounts as you described.
The idea to make it with a multi fallback was to avoi that the playlist will catch the stream again because there would be normaly a active point with higher priority.
So as i understand, there can be only one DJ connected and when he has allready disconencted the next one can connect. Is this right?
By the wy, i will try and test. I can do it without time pressure on the original server in parallel to the exisitng shoutcast. So if it will not work nothing can happend until the server itself will not break down
Thanks for your help @ Karl.
Maybe i will ask again if there are some new problems
*grrr, i think i'm really to stupid for that. If i read the xml i got crazy.
If it possible that someone could send me a short example for the code, special how to conifgure the relays?
Meanwhile i will continue searching
THX |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Apr 06, 2008 3:40 pm Post subject: |
|
|
icecast can have many streams connected at the same time, but 2.3.1 can only have one shoutcast source client connected at any one time.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sun Apr 06, 2008 5:57 pm Post subject: |
|
|
| karlH wrote: |
icecast can have many streams connected at the same time, but 2.3.1 can only have one shoutcast source client connected at any one time.
karl. |
Uuugh,
now you confused me totally
ok, i come one step closer.
All sources (DJ's) must use a programm which will send datastructure for icecast (e.g. simplecast).
Now i get it that the playlit will be overwritten at the moment another DJ connected (on a mount).
The problem is during the hand over.
At the moment the first DJ disconnect, the fallback will take place and the listener are set back to the playlist for a short time until the other DJ has connected.
Exact this is the point i like to avoid.
Is there somewhere a possibility to delay the fallback to the playlist, so the next DJ get some time to connect?
If there is some than that would be helpfull because we can better life with a short "silence" than everytime with a short part of the playlist.
The main reason for do it all:
I want to leave from shoutcast because it can not handle the switching in an sufficient way.
But thanks for your answer |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Apr 06, 2008 6:17 pm Post subject: |
|
|
if the switchover is always short and silent then specify a fallback-mount which is file in webroot, the file could be encoded just silence if you wish.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Sun Apr 06, 2008 8:52 pm Post subject: |
|
|
| karlH wrote: |
if the switchover is always short and silent then specify a fallback-mount which is file in webroot, the file could be encoded just silence if you wish.
karl. |
Sounds good, but i found another problem by doing this.
If i make this the scenario will be as followed.
If the first DJ disconnect the fallback to the "Silent File" will proceded. So far so good. If the next DJ now connect h the new mount will overwrite the fallback "Silent utput" and the Dj got the streaming through the listener. Well done. I like....but....
what happend if no other Dj connect. In this case the "Silent File" will continue all time, or?
Is there a possibility to run this file only for a specifc time (e.g. 10 sec.) and after this time it will also fall back to another mount (playlist) which is located on the server.
Or maybe is there somewhere a possibility to suppres the output from a mount for the first couple of seconds, or to delay the output so that the DJ'S (if there are some) have the possibility to hand over.
Now i tried the whole afternoon, comming step by step forward but at the end no result i really like by testings.
I don't have any more idea to handle it
But i must say, up to your informations i reached more than with shoutcast before.
By the way. I test on Win32 (only locally) and the original test server is running Linux.
You see, this is my "only" Problem how to handle a hand over for different cases. |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Sun Apr 06, 2008 10:16 pm Post subject: |
|
|
A fallback to file will loop, but it won't fallback further and there's no delay. In theory, the mechanism you suggested could be added but it would need to be thought through first, especially with the fallback override mechanism.
karl. |
|
| Back to top |
|
 |
Anonymous Guest
|
Posted: Mon Apr 07, 2008 5:00 pm Post subject: |
|
|
[Hi Karl,
thank you for all your informations.
Finally i found a way to handle.
I will do as followed:
Ech DJ who want to get online is registered and logged in at our HP.
So each DJ can connect to his own mount.
During the handover he will get information from the other one that he can take the stream.
Now we move the users to antoher mount. That could done by the same command wich is used in the Webapplet.
The only modification of this applet is that the DJ who take the stream can not choose from where to where he move the listeners. This informations will set automatically by the information (mount) from actual DJ (Mount has listener) and mount from next DJ (no listeners).
So it is not exactly what i was looking for, but by this i don't expect any more problems and the fallback can be in generall the playlist.
I hope this will work
Thanks a lot for your good help, ideas and comments. |
|
| Back to top |
|
 |
|