David Baelde wrote:
> By the way let me add that this:
>
> On Tue, Nov 24, 2009 at 2:28 PM, kosnickx <kosni...@gmail.com> wrote:
>
>> ({1w00h-1w01h59m59s},monday00o),
>> ({1w02h-1w07h59m59s},monday02o),
>> ({1w08h-1w11h59m59s},monday08o),
>> ({1w12h-1w17h59m59s},monday12o),
>> ({1w18h-1w19h59m59s},monday18o),
>>
>
> is unnecessarily complex, and even "wrong" in the sense that it
> doesn't cover all the time interval. When you write 1w00h-1w02h it
> already means "until 2 oclock excluded" i.e. "until 1:59:59 included".
> So just remove those 59m59s and you'll get what you want. Right now,
> none of these intervals is valid at 1:59:59.
>
> David
>
>
I just did what you proposed.
Well this doesn't work either. I mean that unless the previous dj stops
streaming to the server the new one can not be heard even though the new
one is correctly connected to the server.
So in order to make things simpler i will try to explain what i tried to do:
dj1 streams to liquidsoap (using input.harbor) from 00:00 until 02:00
dj2 streams to liquidsoap (using input.harbor as well) from 02:00 until
04:00
so at 00:00 dj1 streams to liquidsoap which in turn sends this stream to
an icecast server and this goes on until 02:00
at 02:00 (ok this could be 01:59:59) dj2 starts streaming to liquidsoap
which in turn *should* send this new stream to the icecast server (i use
some switching in my script for this)
what happens now is that at 02:00 dj1 keeps streaming to liquidsoap
which in turn keeps sending dj1 stream to the icecast (even though the
switch option says that now its time for the dj2 to do so). Liquidsoap
receives (indeed) dj2 streaming but does not send it to icecast server
*unless* dj1 stops his streaming to liquidsoap.
I hope i made things a little clear.
Well it would be nice if there was an answer to this , but in any case
dj1 can always stop the streaming to liquidsoap ;)
Another thing i noticed is this.
While trying to achieve what i described, i noticed that if there is
some problem with some stream to liquidsoap, the thread (remember i use
input.harbor) stays *open* and in that case the dj can not reconect to
this mount point as liquidsoap returns "mount point taken" (or something
like it) as an answer ...
Well i use idjc to stream to liquidsoap (or icecast server). This app
has the option to stream to different servers at the same time. So while
trying the above, i used this option. I streamed as dj1 to stream 00:00
until 02:00 and again as dj2 to stream 02:00 until 04:00. A few times
the second stream crashed but it seemed to me that the thread concerning
this stream remained open so dj2 was not able to reconnect to this
harbor (got a response "mount point taken" ). The solution was to
restart the liquidsoap script.
Hope i don't disturb you guys much.
Nick
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
