On 08/01/2012 01:35, drew Roberts wrote: > On Sat, Jan 7, 2012 at 7:55 PM, Wayne Merricks > <[email protected]> wrote: >> Hi all, >> >> Due to an unexpected wiring fault and the untimely death of my broadcast >> hardware encoder this week, I had to bypass most of my broadcast rack which >> included a silence detector and a compressor amongst a myriad of other odds >> and ends. Thankfully we have a backup IP Codec but the hardware will be out >> of action for a while so as a temporary measure I set up a darkice/icecast >> server which is acting as a relay source for Live 365 as well as our >> satellite/short wave broadcaster. >> > snip >> Everything was going fine with darkice until it had been broadcasting for >> approx 12 hours and promptly killed itself. I think this might simply be >> due to a bug in version 0.2 that is in the Ubuntu repos. I've installed v >> 1.1 from source but have yet to have the required 12 hours elapse. Has >> anyone come across this issue? > Well, I stream using darkice and iirc in my earlier days I used to try > and send from a local darkice to a remote icecast server. Darkice > would die when the network had issues. I solved this by putting in a > local icecast server and letting the remote icecast server be fed from > that. > > I don't know what your configuration is so I can't say if this may be > affecting you. > >> Any information would be gratefully received, >> >> Wayne > all the best, > > drew
+1 for the local icecast server - it'll solve most issues you have with darkice. We used darkice for years without issue - it's a nice bit of software. You can indeed use JACK and we do so, because we can then do rotter off the same audio input for logging output. We use God (a process monitor written in Ruby) to monitor it all - here's an example config file for jackd, rotter and darkice. https://gist.github.com/8a75de9fe7372e90204d If anything goes wrong, god recovers it. You can use JACK effects, but make sure whatever you do recovers itself after a power loss scenario without intervention. You'll likely need to write some scripts to do this, look at the Jamin tool if you want a nice simple pre-TX processor which supports loading a settings file on startup specified on the command line. All you need is to use jack_connect to hook it all up after boot and you'll be sorted. James Harrison _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
