similar to: Adding to Icestats Available Raw Data

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

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

Good morning, On Fri, 2019-05-10 at 17:59 +0100, Paul Martin wrote: > On Fri, May 10, 2019 at 10:35:39AM -0500, Rick Keniuk wrote: > > > I may have asked this previously, but I am still on a mission to get > > metadata on my OPUS streams (FLAC if possible also). > > https://tools.ietf.org/html/rfc7845.html (Section 5.2) > > ...which is similar to Ogg Vorbis

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

Hello all, I may have asked this previously, but I am still on a mission to get metadata on my OPUS streams (FLAC if possible also). I am using IceCast v2.4.4 (on Windows 8.1) and RadioCaster as an encoder for OPUS streams and I know that sending the streams directly to IceCast will not pass metadata for song title and artist. I have tried using a built-in server in RadioCaster and I can see

I think I got it. I needed to change the following: http://xxx.xxx.xxx.xxx:8000/admin/listclients.xsl?mount=/mountpoint to http://xxx.xxx.xxx.xxx:8000/admin/listclients?mount=/mountpoint and that gives me the XML. No need to change or modify anything. Now how do I get the json as I prefer json? Reaz > On Sep 22, 2020, at 1:51 PM, Reaz Baksh <reaz at dhantal.com> 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 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

Good afternoon, I have two playlists going, on separate mount points, and they both exhibit this behavior. It appears that ices is shutting down when it reaches the end of the playlist. I'm getting these same four lines at the end of the logs of both playlists: [2019-12-08  00:00:53] INFO playlist-builtin/write_ogg_data module shutdown requested [2019-12-08  00:00:53] INFO input/input_loop

Hi there, I'm trying to stream audio from my audio card using ices2/icecast2. I've been following the unofficial HOWTO at http://www.6809.org.uk/media/ices2-howto.shtml. So, I've downloaded and installed libshout2, ices2 and icecast2. Everything starts up OK and I can get stats by pointing my browser at the admin page: <?xml version="1.0" ?> -

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

Good afternoon, On Thu, 2019-03-28 at 21:15 +0800, Prince Naryk wrote: > can u please check my config file and see if there is something wrong with > it, You define the same listen port 3 times. Also your hostname is not set to a hostname but an IP. You also set max clients to 5000. Which is fine for Icecast. However your OS may add additional restrictions. Why do you define a

Hi guys, Can anyone share some (deep technical) light on how «Server Side Spot Replacement" on live radio streaming with Icecast can be done? Thanks, BR Rune -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast-dev/attachments/20170411/e322cb01/attachment.html>

Good afternoon, On Mon, 2019-05-13 at 17:55 +0100, Paul Martin wrote: > On Mon, May 13, 2019 at 08:45:40AM +0000, Philipp Schafft wrote: > > Support for metadata in Opus is a feature of Icecast 2.5.x. It has first > > been included in v2.5.0-beta.2. But please note that this is only about > > displaying. > > I can see support for reading it from incoming Ogg/Opus

I'm using the KH edition of Icecast 2.4.0 but it may also related to the standard release. I added the following to my config xml file but the file cannot be parsed is the error... <mount type="default"> <max-listener-duration>28800</max-listener-duration> </mount> Any ideas of the problem? Thanks. -------------- next part --------------

Thank you, ogginfo returned: ----- Note: Stream 1 has serial number 0, which is legal but may cause problems with some tools. New logical stream (#1, serial: 00000000): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: ffmpeg Channels: 1 Rate: 22050 Nominal bitrate: 35.333000 kb/s Upper bitrate not set Lower bitrate not set Vorbis stream 1: Total data

Good morning, On Sun, 2020-10-11 at 10:24 +1000, Damian wrote: > Can I also ask, which is the recommended course of action? Sure, just keep in mind that we had weekend, so people were off. ;) > Should I rebuild icecast with OpenSSL or is there now a fixed version > via backports that I can use? Based on... On Sat, 2020-10-10 at 23:06 +1000, Damian wrote: > Edit (apologies for the

Anyone know any workarounds for OPUS/FLAC metadata on IceCast? I’ve monitored my inbound stream and this is working correctly (or at least the formatting and data for the OPUS stream is identical to the MP3/AAC+ streams). I see people with OPUS streams and metadata but they may not be using IceCast. Is it safe to assume we’ll see this in the next version? Rick

Couldn't you also just have a client stream locally from icecast that can do things on metadata change? I mean it's a bit icky but it'd work. ---- Philipp Schafft wrote ---- >Good morning, > >On Thu, 2018-11-08 at 12:45 -0500, Alex Hackney wrote: >> I actually got this to work this morning finally. The problem was on my >> auth server. > >Perfect. :) >

Hi all, >From time to time my server getting multiple connection from a same listener. I don't know if it's a bug of the player, or a case of abusing. The situation is "flooding" of the server, the same listener connected to ICE in multiple instances, and using "real" bandwidth (e.g 128K x 30)! how do you handle this situation on your servers?