On Sun, 08 Jan 2012 01:52:25 +0000 James Harrison coerced some electrons to say:
> +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. Another +1 on the local icecast server. I used to do that when we used darkice as the encoder, but I've since switched to liquidsoap (savonet.sourceforge.net). Liquidsoap can be configured to work with jack, but it also can be built with some effects. Liquidsoap has been rock solid for us. I've been using it since version 0.3.8, and it's even more better now that it's reached version 1.0. Search the rivendell mailing list archives, or contact me directly if you want more details. ~d
signature.asc
Description: PGP signature
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
