similar to: About Fallback-mount and fallback-override

At WXBH-LP we had a similar need, and we solved it using mpd (music player daemon) to coordinate our feed to icecast. mpd is a music player (supporting playlists, etc.) originally designed for local network streaming, but it has several attributes that make it suitable for other things: * Items in its playlists can be local audio files or remote streams (e.g. DJ streams). * It

is it free and will it work with my shoutcast server? On 9/25/10, John List <johnlist at gulfbridge.net> wrote: > At WXBH-LP we had a similar need, and we solved it using mpd (music > player daemon) to coordinate our feed to icecast. > > mpd is a music player (supporting playlists, etc.) originally designed > for local network streaming, but it has several attributes that

I have been playing with Icecast only for a couple of days, and I am trying to figure out how to do something. I want a listener to have to only deal with one stream, but I want to be able to switch the source of that stream between multiple sources (DJs). The core idea is that the listener only deals with /live.mp3 while in the background I can problematically switch between a series of live

On Fri, 2003-12-05 at 17:39, Rádio IRCBrasil - André Marcelo wrote: > So it´s very simple, i do a dj with the ircbrasil.ogg and a fallback > playlist.ogg > > so, when onde disconnect for the other enter, the playlist will assume and > my listenners will not disconnect, an i right? > > i yes, i dont need do the relay configuration, it will be very very simple no, you want

Hi Mark, Add extensions to all of your mountpoints for the appropriate audio codec/format you're using. For example, <mount-name>/test.opus</mount-name> for an Ogg/Opus stream. Don't forget to add extensions in the <fallback-mount> sections, too. I didn't look too closely at your config otherwise, that error was standing out. Cheers, Jordan P.S. Please

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

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

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

Hi Ross, Sorry if anyone else has already answered this. Yes there is. Icecast can produce stats in any format desired using XSLT templates. These take the built-in XML as input and can format the output any way you like. There are two XSLT templates included with Icecast2 by default, status.xsl and status2.xsl. Status2.xsl would be easy to parse as it outputs in CSV format. The format

On Wednesday 30 July 2003 17:38, dmz wrote: > Quick thought, if the fields are separated by "," & a title/artist/.. has > a comma in it then it causes a few problems with parsing. If you need to parse it, use the raw xml form. It's more parseable. I don't know what the point of status2.xsl is. > > Likewise if there are multiple streams it might be nice to have

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

On Thu, 5 Jun 2003, Geoff Shang wrote: > Ok. I don't know much about the admin stuff so I won't comment on that. > I think Mike might have posted about it before, so a search of the list > archives might prove useful. Okay I'll look around and see what I can find... > the webroot and XSL files questions are related. To use the XSL files, put > them into the directory

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

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

Marc, Lines with a <!-- and --> are commented and not used. You need to remove these around the mount items. The <<!-- looks like it needs fixing. Ross. -----Original Message----- From: Mark [mailto:mark at tafn.org.uk] Sent: Monday, 17 October 2016 9:35 p.m. To: Ross Levis Subject: Re: [Icecast] Icecast help Hi Ross, First many thanks for your help I have done what you

Hi everybody, I am wondering if it is possible to generate the XML/XSL files on a remote server (status.xsl, status2.xsl or stats.xsl). I am trying to create a player that parses status.xml every 20 seconds in order to show the currently played song (my player doesn't support ICY). Here is the problem: if 1000 users are currently connected, status.xsl will be requested 3000 times in a minute,

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 Fri, 2003-12-05 at 15:37, Rádio IRCBrasil - André Marcelo wrote: > I did a sujestion give me by karlH and brendan, i an running a icecast > master in port 8500 how relay, where the listenners connect, with a local > point ircbrasil.ogg and the relay poing djs.ogg and a secund server, in port > 8600, where the djs connect to streamin. The first dj enter ho djs.ogg and > the other

> ---------- Marvin wrote --------- > From: Marvin Scholz <epirat07 at gmail.com> > Date: Thu, 13 Feb 2020 at 22:51 > > On 13 Feb 2020, at 23:44, Chip wrote: > > > > This is successful: > > > > curl http://example.com:8000/status-json.xsl > > > > But this: > > > > curl -I http://example.com:8000/status-json.xsl > > >

how can i collect such metadata dump? dave, can u help me.. as i don't have access to the server..? can u fwd the metadata dump file to michael for me plz.. thx... -----Original Message----- From: Michael Smith <msmith@xiph.org> To: icecast@xiph.org Date: Mon, 29 Dec 2003 15:04:48 +1100 Subject: Re: [icecast] metadata update is delayed for 2 songs On Monday 29 December 2003 14:54, Phi