Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
is there a way to let multiple harbor clients get mixed together?
for live radios its not nice if the broadcast is interrupted because the
dj's swap. imagine the following case:
harborclient 1 ends its show,
harborclient 2 will resume/start a new show
in our radio we set a silent fallback for 10 seconds, this works quite
good. one client can disconnect and another can connect in that 10 sec.
we do not want 2 harbor ports, or any portredirection.
would it be possible to let harbor mix 2 sources together, or is there a
workaround for that?
From: David Baelde <david.baelde@gm...> - 2010-04-12 21:12:50
On Mon, Apr 12, 2010 at 12:20 PM, email@... <email@...> wrote:
> is there a way to let multiple harbor clients get mixed together?
> we do not want 2 harbor ports, or any portredirection.
Then no, there's no way. Liquidsoap can do anything with sources, but
if you don't want two separate sources, there's little we can do.
Le lundi 12 avril 2010 23:12:43, David Baelde a écrit :
> On Mon, Apr 12, 2010 at 12:20 PM, email@... <email@...> wrote:
> > is there a way to let multiple harbor clients get mixed together?
> > [...]
> > we do not want 2 harbor ports, or any portredirection.
> Then no, there's no way. Liquidsoap can do anything with sources, but
> if you don't want two separate sources, there's little we can do.
I am not sure that you talk about the same thing.
You can have two different source clients that connect to the same harbor
I believe the question is more can you define add([a,b]) where a and b are
From: David Baelde <david.baelde@gm...> - 2010-04-12 21:42:21
Sorry, I read "we do not want to harbor mount points", which would
have been a problem. Two different harbor sources (on two different
mount points, on the same port) are no problem, and you can do
whatever you want with those sources, they are sources like any other.
(Note that with shoutcast sources, two mounts = two ports.)
For example you could have:
harbors = fallback([harbor1,harbor2])
Here it's important to use a two-layered fallback, and not a single
track-insensitive fallback, otherwise an harbor source could interrupt
the other (which is probably not wanted). The transitions could
involve silence before going back to music, and a connection on any
harborX would interrupt that silence to go back to a live stream.
However, if you want that a new harbor connection triggers a
transition from the other harbor, it's only possible in one direction
(depending on the order in the fallback).