From: David B. <dav...@gm...> - 2009-04-30 11:37:22
|
Hi Stephen, On Wed, Apr 29, 2009 at 10:04 PM, Stephen Clower <st...@st...> wrote: > I am working on a general automation system for a small internet radio > station. We recently heard about Liquidsoap and absolutely love what it > has to offer. Thanks. Great to hear, as usual :) > Despite altering the > timeout and length parameters in the playlist() function, I am unable to > find a way to get Liquidsoap to queue up any of these long files. The > results from the log indicate that it tried, but fails, to download each > file over the network. I should really put more information in the log, notably I think the RID (request ID) is not given for failed downloads. This would be useful to then "trace <rid>" (this is a server command), to know if the download failed, or if the sanity check failed (check that we have a codec accepting this audio file). Even when the request fails and is destroyed (i.e., the RID isn't listed anymore in "alive"), you can still inspect it for a fair amount of time (very long unless you allocate a lot of requests). Without the RID in the logs you can still try to guess it: just try all RIDs, or have a script do it... Of course, getting this information and understanding the problem will be easier with a simpler script. If you have a simple script, and if those files are public, you're welcome to send it to this list. I'd then try to understand the situation myself. HTH -- David |