I have almost the same setup here (rivendell -> broadcast rack ->
streaming pc jack -> same pc liquidsoap -> same pc icecast -> live365
via relay).
I won't say its a perfectly glitch free setup but I listen to the output
at work all day and have never noticed anything more than an occasional
hiccup that is too infrequent to really put a 1 in x number of days
figure to it.
Perhaps consider splitting Riv from the streaming?
Wayne Merricks
The Voice Asia
On 22/09/14 11:57, Rob Landry wrote:
JACK is running in realtime mode, but I'm using a generic Debian kernel.
There is a sound card present in the machine, but I'm not using it; I
have JACK taking audio from Rivendell and feeding it to liquidsoap to
generate the stream, which then goes to an icecast instance on the
same machine. My streaming provider is live365.com, which relays from
icecast.
Rob
On Thu, 18 Sep 2014, Wayne Merricks wrote:
Simple answer is Higher latency should equal more time for the
computer to process the audio. This all depends on how CPU starved
the process may be due to other higher priority processes.
Which leads me to is JACK running in realtime mode? Do you have a
real time kernel? (not always easy, Ubuntu doesn't ship one any more
in the normal repos for example).
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
