search for: mnsho

...the second "line" outputted from the file. So, without any state information being passed back and forth from audio program<->icecast<->ices, the only way left to track the state of the script is to read/write external files. That seems a bit inelegant to me, but that's MNSHO, and maybe I'm screwing something up. :) > ices has no way of telling you whats been used to play streams as that > is inside icecast, there is practically no feedback from icecast. It > sounds like you want something from icecast itself. Yeah, I hadn't realised that when I asked...

...ot; outputted from the file. > > So, without any state information being passed back and forth from audio > program<->icecast<->ices, the only way left to track the state of the script > is to read/write external files. That seems a bit inelegant to me, but that's > MNSHO, and maybe I'm screwing something up. > :) No, you're exactly right. The script module is relatively primitive - it was intended mostly as a somewhat useful, but simple proof-of-concept. The intent was to eventually (optionally) have stateful in-process scripts (using perl or python, as...

Hey all. I've got my streams running, they're working quite awesome so far. But I've got a question about automation, and the ices2 "script" playlist option. Is there anywhere I can go to get detailed information on how this works? I'm wondering about passing information back and forth, for example, or if there's anyway to collect information like the audio program