similar to: Unknown IceCast fails

Hi Lev, On 9/7/19 5:04 AM, Lev Zhbakov wrote: > I have node.js script, which works in daemon mode. The script reads IceCast ogg stream itself (on the fly) and sends audio tags to website. My suggestion would be to look at the JSON metadata functionality: http://icecast.org/docs/icecast-2.4.1/server-stats.html If you aren't running Icecast >= 2.4.1 (latest is 2.4.4), then you *really*

After reading this posting in the icecast archives (http://www.xiph.org/archives/icecast/3483.html) about setting the stream url in the metadata with ices2, I couldn't see that it actually was possible to set the ice-url anywhere. Please let me know if the attached patch is any use, and if I'm sending it to the right place! (Unix linefeeds). I use it with Peercast. It means you can add

I run two streams from ezstream via Icecast2 - one over http and one over https. In the ezstream config file I have defined two servers (http and https) and the two streams point to the different servers (by their names). But, if I go to the following two url's, Icecast report same (http-) 'streaming url' for both: https://radio.horsens-garage.rocks:8443/

Hello All, I wrote a PHP function to parse the icecast stats log and return as much information in a structured array as possible (well, as much as I care about, anyway). Because the stats log is not easily machine-parseable, I thought this might be useful to somebody. The log is parsed using Perl-compatible regexps, so it should easily port. I have only my own setup to test this on, so