Well maybe the icecast source code counts as official documentation
somehow. Look for all occurences of "httpp_getvar" on
https://github.com/xiph/Icecast-Server/blob/master/src/source.c
2017-03-01 21:43 GMT+01:00 Daniel Eckl <daniel.eckl@xxxxxxxxx>:
While I couldn't find official documentation, this seems to be a very
comprehensive list: https://gist.github.com/ePirat/adc3b8ba00d85b7e3870
2017-03-01 0:59 GMT+01:00 John McHarry <jmcharry@xxxxxxx>:
That answers my question. Is there a document that states what a source
client can specify?
On Tue, 2017-02-28 at 21:35 +0100, Daniel Eckl wrote:
icecast 2 does not support to change a fallback mountpoint from
remote, via API or anything else. This can only be changed in
icecast2 config file followed by a service reload. There is nothing a
source client like darkice can do here.
Depending on what you want to achieve, maybe cascading fallbacks
could be of any help. You can point the fallback-mount to another
mountpoint that ships the fallback stream. But additionally this
mountpoint can also have a fallback-mount configured itself that is
being used when the first fallback has no source itself.
For another explanation of this multi-level fallback please refer to
the icecast2 documentation at http://icecast.org/docs/icecast-2.4.1/c
onfig-file.html#mountsettings
Regards,
Daniel
2017-02-28 18:42 GMT+01:00 John McHarry <jmcharry@xxxxxxx>:
I should have been clearer. There is an optional icecast2 mount
point
parameter, fallback-mount, which has as its value the name of
another
mount point on the server to which a client will be connected if
the
current source shuts down. Can this be included in darkice.cfg, and
will it be passed to the server?
On Tue, 2017-02-28 at 14:20 -0300, Rafael Diniz wrote:
I feel it's icecast which should support, not darkice.
Could you please explain me what exactly you wanna do?
On 02/28/2017 12:50 PM, John McHarry wrote:
Does darkice support fallback-mount for icecast2 servers?
