Hello,
First let me thank you for making this terrific piece of flexible
software, great work!
I'v run into a few small issues using Liquidsoap 0.3.3. We are using the
telnet interface to manage a request queue, but we sometimes have some
problems with this:
- The first problem is that sometimes - not sure when and why - the
telnet interface locks up after issuing the '.next' command on a
queue. Instead of returning the next songs to be played, an error
message is returned :
> prutsmx.playlist.next
< ERROR: Invalid_argument("Array.make")
< END
If this command is sent once more, no reply is received from
liquidsoap - not even an END message - and the telnet interface does
no longer respond. Reconnecting also does not seem to fix this.
- The second issue has to do with the on_air command. We are using a
default playlist, which is overruled by the queue if anything is
requested. The on_air commmand results two numbers when the playlist
is interrupted in favour of the request. Often the first number is the
track currently playing (the request), but *sometimes* it seems that
both numbers are reverted. Is there order of numbers replied from the
on_air command defined ?
- The third issue is more of a question. Whenever a request is filed,
the queue kicks in and interrupts the currently playing track from
the playlist. Is there a way to let the current track finish before
switching to the request queue ?
Thank you for your time,
Ico
--
:wq
^X^Cy^K^X^C^C^C^C
