Displaying 20 results from an estimated 6000 matches similar to: "Source XML for status.xsl"
2004 Aug 06
0
Source XML for status.xsl
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
>
2004 Aug 06
2
commas are status2.xsl?
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
2004 Aug 06
2
Custom .xsl files?
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
2016 Aug 19
1
Icecast Digest, Vol 146, Issue 7
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
2004 Aug 06
3
'ice_login' not in icecast.xml ?
Nevermind, that stats.xml page is worthless anyways.
got a updated version of icecast2 status
http://www.casterclub.com/icecast_status.php
parses the status2.xsl page
<p><p>Dave St John
(C.E.O.)
Xstream1.com
Mediacast1.com
Casterclub.com
(720-641-7586)
----- Original Message -----
From: "Dave St John" <dstjohn@mediacast1.com>
To: <icecast-dev@xiph.org>
Sent:
2004 Aug 06
1
Source XML for status.xsl
Alright, first off:
Where is the password for admin specificied? In the <admin></admin> section of
the XML config?
Shouldn't there be a directory admin/ in my webroot for icecast? Currently the
only files in my webroot are status*.xsl and some experimental xsl files.
--thanks
Michael Edwards
http://www.walledcity.ca
>===== Original Message From Michael Smith
2008 Nov 19
2
Icecast 2.3.2 doesn't list all mount points
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
2024 Sep 02
2
Strange behaviour with admin/stats.xsl disappearing
Greetings icecasting amigos!
I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement.
The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest server, for mass distribution.
The ingest / origin server runs fine.
I opted for
2004 Aug 06
1
Adding more to stats.xml WAS:Source XML for status.xsl
/me grumbles about upcoming finals:
I note that the mountpoint entry displays the current songs title and artist,
but not the album. In the particular case of my station, album is often more
important (recognizable) as there are a variety of pop/classical artists who
do music for anime. So I'd like to add an album nature but am going to need a
quick overview on how stats.xml is generated.
2005 Apr 17
0
Listener count in stream title
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
2004 Aug 06
2
status2.xsl info...
Quick thought, if the fields are separated by "," & a title/artist/.. has
a comma in it then it causes a few problems with parsing.
Likewise if there are multiple streams it might be nice to have each stream in it's own line so it is easier to grab the info.
Also, status.xsl displays streams even after they have been stopped.
dmz
--- >8 ----
List archives:
2024 Sep 02
1
Strange behaviour with admin/stats.xsl disappearing
Hi,
On 2 Sep 2024, at 12:19, Marek Dziembowski wrote:
> Greetings icecasting amigos!
>
>
> I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement.
>
> The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest
2004 Aug 06
2
Status.xml
Hi,
I have an XSL file that just transfers the XML straight through, see
status-xml.xsl here:
http://www.ecs.soton.ac.uk/~njh/libshout-doc/
<p>I also have an improved version of status.xsl there.
<p><p>Cheers,
<p>nick.
<p><p>>Hi everybody,
>
>If I understand well, the purpose of XSL files is re-formatting XML files.
>When I checked the admin
2011 May 13
1
Standard method to read current listeners without user/password
Hi all,
This is the output of status2.xsl:
MountPoint,Connections,Stream Name,Current
Listeners,Description,Currently Playing,Stream URL
Global,Client:60461 Source: ,,7,,
/foxcub,,,7,, - Brian Eno - Dune Prophecy theme,
It doesn't look like any csv output I've ever seen.
Some of the output seems to be string literal and some of it is the
actual server information, and at some parts
2020 Sep 21
2
Listener stats
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.
2004 Aug 06
1
metadata update is delayed for 2 songs
well
when i streamed the station using foobar.. then foobar2000 displayed the metadata correctly...
but at that time.. when i checked out status2.xml, stats.xsl and stats.xml , the metadata is displaced incorrectly.. two songs behind..
i've tested the stream broadcasting using winamp2, foobar200 w/ oddcast dsp plug in.
you can check out my station at http://ny.icecast.net:8646/play.ogg
2020 Sep 22
2
Listener stats
What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)?
Either of those options would get you remote IP addresses, both a slightly different view in that logs are after a connection closes, while netstat is while the connection is open.
-----Original Message-----
From: Icecast-dev <icecast-dev-bounces at
2018 May 13
2
Parsing status-son.xsl
Hi,
I realise that the web is littered with posts and discussions concerning the topic of getting icecast stats from the xsl files (status-son.xsl) in the icecast web directory. As you may know, many of the solutions are outdated and example links are broken. I have limited knowledge of how to write my own javascript to get this info to display on my own website. Wondering if anyone can refer me
2004 Aug 06
1
Parsing problem
If you want a good way to test out your xsl files, the following will help
quite a bit :
1. get a copy of the stats tree in a file somewhere : wget
http://admin:hackme@server:port/admin/stats;mv stats stats.xml
2. run xsltproc stats.xml yourfile.xsl
xsltproc will try to perform the transform and give you much better
messages than icecast will (icecast just says Cannot parse, but xsltproc
2020 Sep 22
2
Listener stats
Good afternoon,
On Tue, 2020-09-22 at 11:43 -0400, Reaz Baksh wrote:
> Too much work.
I would like to refer to Jordan Erickson's comment here.
> 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.
Why not just use the API? Remove the ".xsl" from any URL in the admin
interface and get the raw XML. The rendered webinterface