Hi Andre,
Sorry for sounding so pessimistic last time, I was just a bit tired.
Anyway, your spec should not be so difficult to implement fully in
liquidsoap. We just need to break it down to pieces of the right size
to keep things readable / thinkable.
What really helps is that one show only plays once over one liquidsoap
execution, because you launch one liquidsoap per day, loaded with a
description of each show, right?
In a first time, let's forget about time slots. It sounds like a show
could be something of the form:
sequence(opener, playlist.once(files_list), closer, filler)
Here opener and closer produce only one track; they could be
single(..) sources or could be wrapped in a once(..) operator.
With that definition the closing jingle won't be played if the
playlist is too long. If the closer is played too early, the filler
comes in.
The global structure of the script should be something like:
SHOW1 = ...
SHOW2 = ...
...
radio = switch(track_sensitive=false,[ ({SLOT1},SHOW1), ({SLOT2},SHOW2)... ])
radio = mksafe(radio) # or fallback with a failsafe jingle
output1(radio)
output2(radio)
...
I've put a track insensitive switch so that a show starts exactly when
needed. It will interrupt the previous show (during a normal track, a
closer, or the filler); a transition can be added to make that smooth.
How does that differ from what you have, and do you see any problem
with that approach?
Cheers,
--
David
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users