Re: [Savonet-users] input.harbor shoutcast bug?

[David B. <dav...@gm...>]

Hi,

It seems that there is some confusion between global and per-source
parameters, which might or might not be a bug.

When you set the per-source port 8005 you might also need to specify
that the source is icy (pass icy=true). When you change to 8765 an
8766 is not open, this seems to indicate that the source runs in
icecast mode (see
http://savonet.sourceforge.net/doc-1.0.0-beta1/harbor.html about the
two contiguous ports used in icy mode).

The global harbor server seems to still start on the globally-set port
even when the only harbor source uses another port (this is the
8005/8006 that you observed, corresponding to the global setting
harbor.port, independent of the "port" param of harbor sources). I
don't know if this is a good idea or not but it shouldn't be a big
problem anyway.

I hope this helps you to understand what's going on...

> So my first question is if ports 8005 / 8006 are standard ports for
> shoutcast or if it is a bug in the liquidsoap implementation.

One surprising thing is that the global icy param doesn't have an
influence on the per-source icy param. We could change this but it'd
look a little ugly (i.e. change that param to a string, either "true",
"false" or "global", the latter being the default).

> After using port 8005 for the harbor I am still able to connect via
> icecast, but when trying shoutcast I can see a connection attempt in the
> logs followed by a "Failed: nth" error.

This is really a bug, at least you shouldn't see an ugly error like
this. I think the problem here is that the source wants to be icecast,
and the global harbor wants to be icy, and there is a conflict because
they use the same port.

Hopefully all this should help you to clarify the picture. Please send
us more info if you get some. Eventually, Romain should be able to
give the final word and choose if/how to fix/clarify the harbor code.

Cheers,
-- 
David