similar to: problems streaming ogg with ices2 and icecast2

The documentation for Icecast2 references a structured XML document containing statistics, such as the following from the docs: <?xml version="1.0"?> <icestats> <client_connections>13</client_connections> <connections>14</connections> <source_connections>1</source_connections>

I have just finished setting up ices2 => icecast 2 on Suse9. Have 5 or so .ogg tracks in a playlist. Also downloaded a full copy of winamp 5 for win. If I point my browser at 10.1.1.1:8000/playlist.ogg then I get the screen to download file I dont know what is but winamp doesnot up. If I use the open URL feature in winamp and give it 10.1.1.101:8000/playlist.ogg Then winamp try to connects

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 >

I have managed to get icecast to start, but when I browse to the admin directory, I get this output: http://127.0.0.1:8000/admin/stats.xml XML Parsing Error: no element found Location: http://127.0.0.1:8000/admin/stats.xml Line Number 1, Column 1: Am I supposed to wrap this output in an xhtml page, like when doing an AJAX query? Kind Regards, Keith Roberts

hi everyone i'm trying to get the variables from status.xml using php (based on the Shoutcast status file from casterclub.com) here is my file <?php $ip = "xxx.yyy.zzz"; $port = "xxxx"; $password = "xxxx"; <p>////////////////start the parsin action\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ //opening socket $fp =

Hello, On 08-03-18 05:54, ScanCaster wrote: > Is there some simple way to get just the listener count on mounts out of > IceCast, specifically 2.4.1 > > Via BASH preferred, or CLI php if I must, I guess python 2.x would be an > option too. (3.x is not an option though!) > > All the stuff I've seen is scrapping things from the status.xsl, which is > bad form. Well,

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

All: Another thing I've always noticed is that the sources & source_connections stats become incorrect if the sources connect at the ''exact same time'' ?? The reason I say this is the OddCast encoders as I've mentioned in previous postings acting in a Chain, have the same "reconnect" timer (of '2 seconds' on modern hi/lo, '4 seconds' on

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

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

Hello fellow mailing list readers, My question relates to multiple / duplicate connections to the ice cast server from the same IP address. I am well aware that this is an issue that lies with the music player (listener agent) used by the listener. When a listener connects to the stream, sometimes it appears as two connections to the stream from the same IP address. This may last only a few

in the status2.xsl there seems to be some extra commas ... --snippet of status2.xsl Global,Client:<xsl:value-of select="connections" /> Source: <xsl:value-of select="source_connections" />,,<xsl:value-of select="listeners" />,, <xsl:for-each select="source"> <xsl:value-of select="@mount" />,,<xsl:value-of

I got the following script from this mailing list but when i try using it doesnt really seem to work and gives me the following error. Warning: fopen(http://...@64.157.204.179:9095/admin/stats): failed to open stream: Bad file descriptor in E:\Public ftp\epakimusic\test.php on line 9 Error reading Icecast data from 64.157.204.179:9095. So could someone please help me out with this.. or if

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

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>

hallo firstly sorry for posting to wrong thread i want to ask if somebody could explain meaning of log records below DBUG stats/modify_node_event update global connections (686) DBUG stats/modify_node_event update global client_connections (685) number in parentheeses is increasing in every log line what is menaing of this number? because this number goes over 59669 and it seems that after

I have been trying to get my station listed in the icecast directory. I would appreciate someone reviewing this to see what is wrong. I've studied the documentation and I think I am doing what is required, but my station is not showing up in the icecast yp directory. I'm using icecast 2.3.2 I have the directory entry in the icecast.xml config file: <directory>

you can pull it with jQuery via javascript for example evry 10 seconds, and update the informations you want, at least its the way i do it. Am 23.11.2023 um 00:13 schrieb Thomas Jensen: > 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

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);

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.