similar to: IceCast Listenter Count Stat - BASH or php?

just parse status-json.xsl with php's curl/json_parse... ScanCaster: > On Mon, 12 Mar 2018 22:07:34 +0100, Jeroen van Oosten wrote: > > > Well, you can create your own XSL with less data. I use this (as > > web/simple.xsl): > > Well since I don't know XSL, BASH etc. was my go to choice... > > BUT... > > Doing this gets > 404's from a

Hello, On 06-12-15 13:58, Yahav Shasha wrote: > > >To me it sounds like a bug; surely the fallback never needs > statistics, > only the real steam because this is where listeners connect to. > > > Well, the fallback mount is still a mount-point nonetheless. you could > still use it as a "regular" mount-point even if its configured as a >

On Fri, 14 Nov 2014, Dean Sauer wrote: > In a search for access to various ways to interact with Icecast via > Python, I ran across this: > > http://xiph.org/~brendan/pyshout2/pyshout2-0.0.1.tar.gz > > Which is now dead (404). I don't think this library would have helped. I expect it would be useful for source clients to send media to a server. > I have a need to be

I must try that. Will let you know asap! btw I'm not "trying to stick with the one that has the most universal "default browser support" but instead trying to avoid a LOT of listeners writing me "my player/browser/whatever doesn't connect, it doesn't understand ogg / opus / xspf " etc. etc. - so mp3 it is. It's simple surviving :) On 3/18/20, Jeroen van

On 26/03/2020 13:49, Chip wrote: > Thanks. > > Indeed - but is it it possible to block IP addresses on a per > mountpoint level? For example, my user with /mountpointA.ogg does not > mind being hammered by connections from 93.184.216.34 [example.com > <http://example.com>] but my user with /mountpointB.ogg wants to block > that IP address. If the mountpoints are at

On 08/03/2020 16:24, Gavin Stephens wrote: > Sorry for the late update. I didn't realise the replies came and went > off list regarding this. > > I had another suggestion made to me it could still be bad pem files > and to try converting them to pfx then back to pem files, which I did, > and fortunately this fixed it. > > The error message I was getting in the Icecast

Hello, On 15-04-17 15:19, Chris Howard wrote: > Hi, > > I see two statistics on the admin web page. > > On my system "listeners" is usually 0. Sometimes I will > actually catch it at 1 or 2, but it is 0 99% of the time. That is the current number of listeners. > On the other hand "listener_connections" is always > going up. If I refresh the screen

Thank you Philipp. I'm running icecast 2.4.2 and based on the "Available Raw Data" in the Icecast docs page (http://icecast.org/docs/ icecast-2.4.0/server-stats.html), it doesn't appear "album" or "year" are available for the stats-json.xsl file to get. But it may be misunderstanding what I'm seeing and just don't know how to properly customize the

Hello, I've come across a small problem and I'm not sure it's a bug or a misconfiguration in icecast, so I thought I'd ask here. The situation: we have an automated radio station that is fed from a dedicated virtual machine with SAM broadcaster. I set up a stream with a fallback mount; SAM connects to the fallback. Now, whenever the DJ wants to broadcast live all he has to do is

Hello, I've upgraded from 2.3.1 to 2.3.2. I've been used to list all mount points by <xsl:for-each select="source"/> under /icestats. Howver now the /icestats elemets contains only source elemets which have been requested at least once. That means the list (e.g. /stats.xsl under web directory) is empty after server start. I've found out this regresion presents only

I've been trying to track down this mysterious 'icestats' file that the status.xsl and status2.xsl read data from. There is no physical file as far as I can tell, but a perusal of the code seems to indicate that the server generates it on the fly when the XSL file requests it. So then I tried servername.com:8000/icestats but I got nothing. So I really got nothing, I would prefer

M Edwards <medwards@ualberta.ca> said: > I've been trying to track down this mysterious 'icestats' file that the > status.xsl and status2.xsl read data from. There is no physical file as far as > I can tell, but a perusal of the code seems to indicate that the server > generates it on the fly when the XSL file requests it. So then I tried >

On 2008-11-20, Karl Heyes <karl at xiph.org> wrote: > Petr Pisar wrote: >> Hello, >> >> I've upgraded from 2.3.1 to 2.3.2. I've been used to list all mount >> points by <xsl:for-each select="source"/> under /icestats. >> >> Howver now the /icestats elemets contains only source elemets which have >> been requested at least

Is there a way to add additional metadata fields to icestats in such a way as to be accessible to stats-json.xsl? In particular I am interested in adding "album" and "year". -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20160818/6bbd1420/attachment.html>

Thank you, Ben! I was afraid it would be very complicated to get the information extracted, but it was very simple. My only problem now is to find a way to update the text on the webpage. I was hoping sleep(5) could do the trick, but it does not work. <?php if (1) { $jsonobj=file("http://radio.protestbandet.dk:8000/status-json.xsl"); //var_dump($jsonobj);

Hi all, I just wrote this script (attached) which I thought others might find useful -- it updates the song title of every mountpoint with the current number of listeners for that mount. It can be seen in action on http://radio.ethereal.net:8000/stale, where it runs every minute out of cron. The script should be self-explanatory, but feel free to write me privately with any questions or

On Thursday 22 July 2004 04:56, Myke Place wrote: > I'm curious if it is possible to create custom .xsl files in the /admin > directory, using the same xsl params that appear in in the web > interfaces that ship with Icecast2. Yes. Though I don't know if using an arbitrary one works from the admin directory. Certainly you can put them in icecast's webroot directory (or some

Hi Reaz, IP Address != Location of user in many cases. Think VPNs for instance. Of course if you're set on going that route, I'm pretty sure that status-json.xsl (in your webroot) has the IP address option simply added to a section that does not show it: <xsl:template match="icestats/source/source_ip"><xsl:if

Hello Jordan Thanks for the reply.  I commented out all the fields in the status-json.xsl but it didn't give me the listener IP.  The example below would show me the source IP.  I can get the IP from the web interface at this location, http://xxx.xxx.xxx.xxx:8000/admin/listclients.xsl?mount=/dhantal, but that means I would have to scrape the web interface which I don't want to do.

Too much work. If I am able to see it on the web interface I should be able to get a Json or XML file with this in it. The reason I need this is to show current listeners and from where they are listening. I do this with the other streaming software without any modifications or adjustments. This should be easy. Reaz > On Sep 22, 2020, at 11:16 AM, <jorr at streamguys.com> <jorr at