Hi, Yes, this is an annoying problem. I'm not sure what to propose...
First, this is not specific to pulse. When you execute your script, it creates sources, which are attached to clocks, and finally the clocks initialize and activate their sources. This last phase fails if an output is improperly setup, or for other reasons. The difficulty is that this last phase is implicit, so with the current model there is no way to get feedback about the failure of initializations. The implicit initialization causes other problems. For example, it is possible to desactivate a source using source.shutdown() but then you can't reactivate it. At the core of liquidsoap, it's perfectly doable, but for the user it's not accessible -- although tricks such as output.dummy(source) simulate it. On a related note, liquidsoap scripting doesn't have exceptions, so it's generally annoying to deal with errors. So, we need to think of ways to give you more control... David ------------------------------------------------------------------------------ Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
