DJ switches using NSVCAP

[Subfader]

Hi, DJ switches are no problem with DJ's using normal SHOUTcast DNAS streaming to a server, because the next DJ just hits auto-reconnect and can't connect till the previous disconnects, only then he is clearly on air by seeing the bytes being sent. Listeners don't get disconnetced while that.

Seamless DJ switches are impossible using NSVCAP. If the next DJ connects (Start Capture) while a previous DJ is on air NSVCAP will just start capturing without telling you that you're not on air. The next DJ has to wait till the previous disconnected (including the delay) and then he must connect to be really on air.

Is there any way to get around this procedure and to let the next DJ auto-reconnect like in SHOUTcat DNAS?

cheerio

[Klausi2007]

Originally posted by Subfader
... Seamless DJ switches are impossible using NSVCAP. If the next DJ connects (Start Capture) while a previous DJ is on air NSVCAP will just start capturing without telling you that you're not on air. The next DJ has to wait till the previous disconnected (including the delay) and then he must connect to be really on air.

Is there any way to get around this procedure and to let the next DJ auto-reconnect like in SHOUTcat DNAS?

cheerio

If you change some little details on your switching procedure,
the switching looks like "seamless" to your listeners.

1. Be shure, the framerate is absolutely the same at the next DJ

2. in the "headers" part of NSVCAP you have to change (or add) the following line:
icy-reset:0

3. The previous DJ has to talk (chat, msn, whatever) to the next DJ when he stops the capture

4. The next DJ can start capture immediately.

This works only on the same video framerate and the same video codec. If your audio is AACP, the audio bitrate can be different, eg. the pevious DJ streams with 96kBit AACP and the next DJ comes with 64kBit AACP.

I think, this is not what you think about "seamless" but it's a way to switch over to the next DJ without disconnecting any listener. It works for me since 2003 :-)

I hope, this helps a little bit.