Well, I don't really see what's wrong with the "dump via configuration" option. You probably don't know all the possibilities. Indeed, some are quite recent.
First, we have fallible outputs on the SVN version, soon to be released. This means that an output (when you pass it the fallible=true option) can automatically start/stop its output process (write to a file, for example) when its source becomes (un)available. For your example, it enables you to dump directly the live input, which is fallible.
Also, you have telnet commands provided by all outputs, including the file outputs. By default an output is automatically started (and when it's fallible, it'll automatically start as soon as its source becomes ready). But if you pass start=false it won't start unless you tell it to start. And you can even install event handler (on_track, etc) to stop it automatically.
If you still feel that something is missing, please provide more details and we'll try to help you more specifically.
well, after a long time of research i found some solutions. you're nearly right, i did know all the possibilities of "dump via configuration", but had no clue how to use them, or if i really do need them. now i know, i do!
i think this is a general problem, i didn't understand the docs, they should be more precise and give some hints. most of my knowledge about configurating liquidsoap i got by analyzing the example scripts of the other radios...
this is not meant to complain, i realy am happy, that all my problems could be solved for now, thank you all for liquidsoap!
ps: maybe i could help making the docs more understandable. please let me know, if you need my help, somehow.
http://www.sellrails.info wrought iron stair railings
http://www.shanhairail.info decorative railing
http://www.whole-railing.info deck railings
ok, you can set an output.file.whatever and start/stop it by its start/stop- function via telnet.
no need for a telnet dumpfile command.