similar to: Metadata Swapping: How do they do it?

Think I answered my own question really. The display in iTunes, for example, is swapping between what in status.xsl would be Stream Title and Current Song. If Song is updated like so: http://admin:password@myserver.pulverradio.com:8000/admin/metadata? mount=/high.mp3&mode=updinfo&song=ACDC+Back%20In%20Black ...then what exactly is the verbage to update StreamTitle?

On Thu, 2005-05-05 at 20:17, Ian Andrew Bell wrote: > Think I answered my own question really. > > The display in iTunes, for example, is swapping between what in > status.xsl would be Stream Title and Current Song. > > > If Song is updated like so: > http://admin:password@myserver.pulverradio.com:8000/admin/metadata? >

On 5-May-05, at 12:52 PM, Karl Heyes wrote: >> My (potentially misguided) belief is that the client >> downloads/receives >> the latter attribute once, on initially connecting to the relay. >> >> KH and I have been playing with a branch he built that lets you >> configure all that stuff in the icecast.xml file however it's not >> making it into the

Sending again .... is this thing on? On 11-Feb-05, at 9:20 PM, oddsock wrote: > At 10:21 PM 2/11/2005, you wrote: >> Now that 2.2.0 is out, we can update metadata on-the-fly. At >> pulverradio.com we are working on an injector that takes the song info >> from our broadcast automation software and dumps it in (thanks guys >> for >> the help). I realize that we

At 10:21 PM 2/11/2005, you wrote: >Now that 2.2.0 is out, we can update metadata on-the-fly. At >pulverradio.com we are working on an injector that takes the song info >from our broadcast automation software and dumps it in (thanks guys for >the help). I realize that we can inject the song info like so: > >http://server.ip:port/admin/metadata?mount=/

Now that 2.2.0 is out, we can update metadata on-the-fly. At pulverradio.com we are working on an injector that takes the song info from our broadcast automation software and dumps it in (thanks guys for the help). I realize that we can inject the song info like so: http://server.ip:port/admin/metadata?mount=/ mountpoint&mode=updinfo&song=ACDC+Back+In+Black .... but are there

Right... I understand how the stream works and we have no confusion at all then. So I need to create a script to re-inject MP3 Metadata from my handy-dandy XML file (when it changes) which is easily done if, as you say, there're a few variables that the admin.cgi can listen for (of course Icecast has no admin.cgi) The info you've provided for Shoutcast is useful and you allude to

As a follow-up to this thread: http://lists.xiph.org/pipermail/icecast/2004-May/007171.html ... I am still attempting to relay effectively from two separate Audioactive encoders via an icecast server. Since we last discussed this Audioactive have updated their firmware to comply to the standards for MP3 streaming more explicitly. And according to Michael Icecast was patched to be more

At 08:24 AM 2/15/2005, you wrote: >Sending again .... is this thing on? sorry, meant to respond, been very busy of late.... >On 11-Feb-05, at 9:20 PM, oddsock wrote: > >>no...at the moment, only "song" is supported. All other stream info >>details (URL, Genre, etc) is not currently update-able via the admin >>interface. The must be supplied by the source

When "Icy-MetaData: 1" is in the HTTP request to the server, that indicates that the client wants to receive meta data inlined with the mp3 data stream. The metadata interval is reported by the server via the "icy-metaint" header in the response stream. Such data looks like the following within the mp3 stream StreamTitle='Ozzy Osbourne - Crazy

At 06:19 PM 11/22/2004, you wrote: >Like any other major radio station we output our music from automation >software via analog audio through a mix board in a studio, where we insert >other stuff like live DeeJays, etc. only to have that stream re-encoded by >hardware MP3 encoders for distribution to our network of IceCast servers. > >The chain of song information gets broken

Like any other major radio station we output our music from automation software via analog audio through a mix board in a studio, where we insert other stuff like live DeeJays, etc. only to have that stream re-encoded by hardware MP3 encoders for distribution to our network of IceCast servers. The chain of song information gets broken as soon as we output from the Automation software,

i see that icecast retains song titles only when running in full debug mode (with DEBUG_FULL defined in icecast.h). is this observation correct? how can i find out when a new song is being streamed by a source? can i determine this accurately by examining song title (souce.info.streamtitle)? or, is there a more reliable method? <p>pls. let me know. thanks, deva <p>On Mon, 17 Feb

Linux blort.psg.com 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:02:19 UTC 2014 i686 i686 i686 GNU/Linux # icecast2 --version Icecast 2.3.3 <listen-socket> <port>43000</port> </listen-socket> <listen-socket> <port>43001</port> <shoutcast-compat>1</shoutcast-compat> </listen-socket> source is

On Tuesday 18 February 2003 19:37, Deva Seetharam wrote: > i see that icecast retains song titles only when running in full debug > mode (with DEBUG_FULL defined in icecast.h). is this observation correct? Ah. You must be talking about icecast 1.x. I was talking about icecast2. What I said is not at all accurate for icecast 1.x, you should ignore it. > > how can i find out when a

Hello, Can anybody tell me how stream titles, which are non-ASCII, are sent? For example, at ShoutCast.com, there are Asian and European streams that send encoded strings. However, I can't see how to detect what type of encoding they are using. e.g. UTF8, ISOLatin1, etc. If I could work out the encoding, then I can display the names properly. Any differences between how IceCast and

Michael, thanks for your propmt replies. > > i see that icecast retains song titles only when running in full debug > > mode (with DEBUG_FULL defined in icecast.h). is this observation correct? > > Ah. You must be talking about icecast 1.x. I was talking about icecast2. What > I said is not at all accurate for icecast 1.x, you should ignore it. how do i get icecast2? when i

Howdy Folks: Is there a way in v2.4.2 to include a ?StreamUrl=? field in the stream metadata as well as ?StreamTitle=?? It appears that the administrative interface only populates StreamTitle. For example: http://server.example.com:8000/admin/metadata?mount=MyMount&mode=updinfo&song=MySong will insert only ?StreamTitle=MySong?;. Googling around has brought up some possible

On Tue, 7 Aug 2001, Richard Fromm wrote: > to clarify, the behavior that i saw was that most of the time the title > streaming appeared in the client, but sometimes it did not. i think i've nailed this down. the problem is if the icecast server starts in the middle of a song already being sourced to it. (which you can get by starting icecast, start ices, then shutdown and restart

If propagation of Ogg Vorbis is the (or a) goal of Icecast then probably the best strategy is to build an embedded Ogg Flash Player of some sort, so that people unwittingly become Ogg users without lifting a finger, and broadcasters can start using it without fear that they'll lose listeners due to their protocol choice. I've been streaming for more than 7 years now with Quicktime,