Yes, I know about DTMF, and that would be the most ideal setup, because the network I want to syndicate does use these. But, I am just trying to give another option in case DTMF is harder to implement. Like I said, in the system I used to use, we were able to create timed events inside of a playlist, thus insuring precise connect and disconnect. DTMF would be even better, but I understand that would be harder perhaps to set up so maybe the timed event in the playlist could be easier.
I say this, because just having some things play before, and connecting to the stream whenever won't work. I only want to pick up the shows, but NOT the network's commercials. My own commercials, sweepers, etc all have varying lengths, so it is impossible to be able to calculate that out for an exact start time without something in the system giving it some smarts, like "if this event is longer than the time before this is supposed to happen, then do this instead." Usually, what one would do is to have a backup folder with instrumental tracks, where one could be selected, and that would play for a few seconds, to bridge the gap between your last sweeper, commercial or whatever, and the start of the timed event. Again, the idea is to pick up the show pretty much exactly when it starts. Obviously, one may have to play a bit with start time to get it exact, but it can be done. Again, DTMF would be better, but in case of that being harder or taking more time to implement, being able to set a start time would be the best alternative. I can't just set some files to play and then pick up the stream. Some files could be shorter, and the stream could get picked up too early. Some files could be longer, and then the stream could be picked up too late. So there needs to be something in place that the system knows, this event starts at this time, so if what is about to be played can't finish in time, do this instead.
I know I could just use RB desktop, and program all this using dtmf, but the idea is to NOT have to use the computer all the time. That's why the Cloud service exists in the first place. I don't see that the current options can make this work as I am needing in this use case. For everything else I am doing with it, it has been absolutely fantastic. I just need this one implementation.