code/example.
than a HTTP call. In theory, it should be possible to implement your own
automatic registration of such handers. But. let's start with the idea:
see how to receive JSON metadata and insert them into the source. In
but adapted to the ICY metadata update protocol.
name and perhaps some parameters/authentication mechanism. I don't remember
Post by Christo GrozevDear Romain,
Further to Markâs question/use case, I am trying to parse metadata from a
third-party streaming encoder that connects to my input.harbor. The
unexpected behavior is that there seems to be a delay of a few seconds
between the moment harbor reports (logs) receiving the meta data update
request from the encoder, and the time liquidsoap âprocessesâ the metadata,
such as in an on_metadata event.
I need to eliminate this delay. Is there a way to capture the GET request
header when it arrives so I can act on it immediately? I tried doing this
via harbor.http.register but then it hijacks completely the request and the
metadata does not get updated in the stream.
Maybe there is an easy way to capture the logged events and parse them? (a
round-about hack would be to go via file.watch and the logfile, but I am
sure there is a more sane solution J)
Thanks for any feedback!
Christo
*Sent:* Wednesday, April 12, 2017 10:04 PM
*Subject:* Re: [Savonet-users] Liquidsoap input.harbor connections
You could try to to use the on_connect parameter from input.harbor and
pass your parameters as headers.
Yes, that's what I thought. So to be clear I can mutiple endpoints on the
same port and those are unique connections and each connection can use a
different output, right?
It'd be really nice if we could pass parms in the URL and parse those to
create dynamic outputs based on the parms. What I've done is to create
commands that are issue over telnet to dynamically creating inputs and
outputs before a streaming client connects, that works. But it'd be so much
easier not having to use Telnet (point of failure, processing overhead,
resource overhead).
My use case is that there are an unknown (but reasonably low) number of
potential streaming clients that might connect and be connected at the same
time for anywhere from an hour to maybe 3 hours (each client may be a
different duration). Since I don't know the number streamer clients in
advance at any given moment in a day I need to dynamically build the inputs
and outputs as a client starts to connect (all this is driven by a Web site
interface sending a few commands to liquidsoap over a Telnet connect).
Or is there already a way to parse parms in the endpoint URL and take
http://theserver:9000/live?abc=123&xyz=456
<http://h5ks.mjt.lu/lnk/ADsAAHKI7CgAAAAAAAAAAGgH3uUAASJ-8QAAAAAAAAgArwBY7QrGeRODKGx2Rr6NqTadH_U5jAAHnU0/1/vK4yhTlDpK0GE2xg2WWjkw/aHR0cDovL3RoZXNlcnZlcjo5MDAwL2xpdmU_YWJjPTEyMyZ4eXo9NDU2>
Mark
Hi Mark,
input.harbor connections are unique and scoped by: mountpoint, port
If you need multiple connections, you can thus use multiple endpoints
s1 = input.harbor("source1",port=8000)
s2 = input.harbor("source2",port=8000)
other_s1 = input.harbor("source1",port=8005)
Makes sense?
Romain
Hi, is it possible to accept multiple connects from different clients on
the input.harbor endpoint (for sending audio streams) and have those
connections sent out to different output.icecast endpoints? Or do I have
to set up unique input.harbor endpoints for each potential client? If I
can do that with one endpoint what's the best approach to setting that up?
Mark
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
<http://h5ks.mjt.lu/lnk/ADsAAHKI7CgAAAAAAAAAAGgH3uUAASJ-8QAAAAAAAAgArwBY7QrGeRODKGx2Rr6NqTadH_U5jAAHnU0/2/rDL1zksw13JnGFpuVp9SGQ/aHR0cDovL3NkbS5saW5rL3NsYXNoZG90>
_______________________________________________
Savonet-users mailing list
https://lists.sourceforge.net/lists/listinfo/savonet-users
<http://h5ks.mjt.lu/lnk/ADsAAHKI7CgAAAAAAAAAAGgH3uUAASJ-8QAAAAAAAAgArwBY7QrGeRODKGx2Rr6NqTadH_U5jAAHnU0/3/XQW-AiOM-OnSTvq92lc8jQ/aHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vc2F2b25ldC11c2Vycw>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://h5ks.mjt.lu/lnk/ADsAAHKI7CgAAAAAAAAAAGgH3uUAASJ-8QAAAAAAAAgArwBY7QrGeRODKGx2Rr6NqTadH_U5jAAHnU0/4/q_0os7yG4y8YZNMk886igA/aHR0cDovL3NkbS5saW5rL3NsYXNoZG90>
_______________________________________________
Savonet-users mailing list
https://lists.sourceforge.net/lists/listinfo/savonet-users <http://h5ks.mjt.lu/lnk/ADsAAHKI7CgAAAAAAAAAAGgH3uUAASJ-8QAAAAAAAAgArwBY7QrGeRODKGx2Rr6NqTadH_U5jAAHnU0/5/wwjkmQWgFi7WktDTCEnkqA/aHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vc2F2b25ldC11c2Vycw>
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Savonet-users mailing list
https://lists.sourceforge.net/lists/listinfo/savonet-users
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Savonet-users mailing list
https://lists.sourceforge.net/lists/listinfo/savonet-users