Hi, On Feb 2, 2008 10:41 PM, Vincent Tabard <[EMAIL PROTECTED]> wrote: > My question is quite basic: I need to get a grab on what I play and when > (visual feedback + precise, "far-future", duration computations + determinist > playout + Xfading), how much of Liquidsoap can I re-use through libliq, and > how > much will I need to reimplement on my own?
In theory, everything in liq can be put in libliq. If anything is missing, it should just be a matter of editing $(libliq_sources) in src/Makefile. For now, let's not care about what should not be in that lib, as long as you have any use for it. You'll get playlist parsing, and also the precise duration computation that is currently not used in liquidsoap (Request.duration). Concerning cross-fading, it's a bit more tricky. If you re-implement it by yourself, it's okay, and you'll have a good control on how it affects duration. On the other hand, if you want to re-use cross() or smartcross() you need to implement a source for your precisely-timed-playlist. And in that case, why not implementing that source in "normal" liq and access it using liq scripts ? I guess you're not going that way anyway. > I don't think these features can be implemented as a "simple" telnet > interface, > unless I give up the playlist part, and switch to feeding request queues. It > will also require constant polling of Liquidsoap to check the elapsed / > remaining time, current song, player state, etc. To put it shortly, I feel > that > maintaining consistency between Liquidsoap and the interface will be a real > pain in the neck. I'm not sure about all that. I don't feel like trying, so I'll leave the opinion-making to you. May the force be with you. -- David
