Hi Romain! >> To clarify: >> >> If they are allowed to connect between 1pm and 2pm, then my external >> script can check the time and allow their connection. But once 2pm has >> been reached, how do I disconnect them so that the next person can connect? >> >> Additionally, if someone is allowed on at 1pm because that's when their >> show starts and the previous one ends. Most people would want to >> connect a few minutes prior to 1pm just to make sure they're on time. >> But if someone else is connected because their show hasn't finished yet... >> >> Is it resource intensive to have dozens of input.harbor() mount-points >> set up like it would be to have dozens of input.http()? If not, I could >> use other functions (like switch()) to handle the broadcast timing. Can >> the various input.harbor() mountpoints all listen on the same port like >> Icecast2 allows (I would imagine so)? > > No, it is does not consume more ressources to define several harbor mount > points. It may consume more ressources if two sources are connected at the > same time, but this is not a surprise ;-) > > I'd say that the best for you would be to use a switch with several harbor > sources, indeed. And yes, they all listen to the same port like for icecast !
Thanks for the response. I began testing out multiple harbor sources and noticed a difference in behavior between that and input.http(). With input.http(), it would just broadcast the stream as-is. When I switch to a commercial for two minutes and then switch back to the stream, it would pick up in the middle of the stream right where it is, meaning that whatever was streamed in the two minutes during commercial would have been lost, and this is exactly what I would expect. However, with input.harbor(), the stream was put on hold during the commercial, and resumed where it left off. This is definitely not what I want. How can I make input.harbor() function like input.http() in this regard? ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users