On Tue, 08 Feb 2011 23:41:39 -0500, Romain Beauxis <[email protected]> wrote:
> 2011/2/7 <[email protected]>: >> Hi, > > Hi Andre, > >> To better understand some strange behaviour with output from my >> switch-based program scheduling, I'd like to clarify exactly what >> is the default behaviour in liquidsoap. >> >> I use 'track_sensitive=false' to trigger an abrupt end of the >> current playing track when the 'Show block' allotted time expires. >> >> >> icmp3 = mksafe(switch( >> track_sensitive=false, >> [ >> ({09h00-09h30}, sstol), >> ({09h30-10h00}, mfts), >> . . . >> ] >> )) >> >> When the next switch element kicks in, it should play the first >> item in the sequence that is defined for that new time-slot. >> >> Now for the questions: >> >> 1. If a new listener tunes in part way through a time-slot, would >> they hear only the current track in progress? Or would they hear >> everything from the very beginning of the show's time-slot (even >> though its 'play-time' has already occurred)? >> >> 2. If liquidsoap experiences a crash mid-way through a time-slot, >> is restarted, would it restart the time-slot from its beginning? >> >> 3. Does the liquidsoap *remember* what has been played and cue >> new listeners to that point? > > About 1) and 3): the streams produced by liquidsoap have no > consideration for the listeners. They basically are continous flow of > audio data. Icecast does the work of redirecting this flow to each > listeners. Further, when a listener connects, he receives the stream > at the point it is in the view of icecast. > These aspects differ a lot with on-demand streaming systems when the > streams can be customized for each listener. re: 1) That's what I thought should happen: when a listener connects, he will *tune-in* to wherever the audio stream sent by liquidsoap to icecast is at that moment. However, what I'm experiencing with almost all streams: I connect, and I'm brought to the beginning of the time-slots' show, irregardless of what time I connect. That is not what I expected. So, essentially, you're saying it's a problem with icecast and/or the client's audio player? I get different results with different players. None of them show the title of the current show, even though locally, using the same playlist/single, they show up with that player. I'm trying to track down where the problem is for the weird 'Show block' stream disorder, and as well and probably related, the lack of displayed ID3 tags. Strange thing is - about a month ago, the ID3 tags worked fine. > However, we strongly believe that you should experience very few > liquidsoap crashes :) I just added Shoutcast today. First time it worked flawlessly. Second time I accessed it. received a Cry socket errorors: / source not responding (or somesuch), and barfed liquidsoap startup. > > Romain Sigh . . . Thanks, Andre ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
