Icecast Streaming Media Server

Galan · Joined: 16 Feb 2010 Posts: 4

If I'm interpreting what I'm reading and seeing correctly, it looks like Icecast returns a standard HTTP "200 OK" to a GET query, whereas Shoutcast returns an "ICY 200 OK", and it appears this may be causing Windows Media Player to not add an "ICY-MetaData:1" to its requests, and thus Icecast is not returning metadata in the stream. Does this sound correct?

If so, can anything be done about it? Does Icecast have an option to return the perhaps less "proper" but more common "ICY 200 OK" reply? I've noticed some players are fine with Icecast's HTTP 200 OK return, and they request and parse metadata just fine, but it'd be nice to get Windows Media Player to where song metadata could also be displayed from an Icecast server.

Thanks,
Galan

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

You are incorrect. the icy-metadata request header is sent before any response from icecast. afaik wmp does not request metadata at all but I don't use it so I cannot say for sure.

karl.

Galan · Joined: 16 Feb 2010 Posts: 4

Ok. Flipping the question around, then ... any idea if Icecast *can* be configured to push metadata that WMP can recognize? I know WMP was displaying it from my stream back when I was using Shoutcast, but it stopped once I switched to Icecast. I just confirmed again tonight that WMP does show metadata for some streams. (But I watched the interaction between it and the server and never saw an "ICY-MetaData:1" go by, only the "StreamTitle".)

Thanks,
Galan

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

Obviously icecast cannot just push the metadata as the metadata inserts break the codec specification, so the player has to be aware of them. If wmp is requesting metadata with the header you mentioned then icecast will provide what it knows about (the status page will show that). If that data has not been provided to icecast then it would be empty and wmp would not receive those updates.

Your last statement seems at odds with what you are asking though, StreamTitle is the text within the metadata insert, icy-metadata is a request header (shortly after GET ....) and icy-metaint: is in the response headers. Only after the response header is provided will the metadata inserts occur.

karl.

Galan · Joined: 16 Feb 2010 Posts: 4

Karl,

Thanks. Yes, though I'm new to Shoutcast and Icecast, I've been deeply involved in streaming for a long time now, and I agree with your statements, and it's odd to me, too.

I forgot to search for an "icy-metaint" in the data, so I guess I'll do some more captures today and see if they're there. I agree, one would expect it to be there by all rights, but I was wondering if maybe WMP was smart enough to do pattern searching on the data, looking for a StreamTitle in the data "just in case"?

Though I'm a developer, I'm not needing to develop anything in this case, just get metadata to show up in WMP from Icecast. All my searches about this subject have turned up empty, to my surprise, which is why I decided to turn to this forum. Your willingness to help is appreciated. I'll check back in again with any additional findings I get. Smile

Thanks,
Galan

jcr · Posted: Wed Feb 17, 2010 6:49 pm Post subject:

Main problem with Windows Media Player is: "This player is the one which does not look at standard metadata"". It looks for what it expects, and this is mostly Windows Media Server information..

If other players such as winamp, vlc, xine, and many more, display correct information and WMP does not, right conclusion should be "WMP is broken" and not the rest of business is broken..

Il often have here in France such complains... But when I tell them to try with alternate players and everything works as intended, with 3 or more alternatives, the real thing is "blame wmp".
_________________
Epsilon Friends Radio Icecast Radio on CentovaCast admin panel. Icecast hosting

Galan · Joined: 16 Feb 2010 Posts: 4

jcr,

>> ... right conclusion should be "WMP is broken" and not the rest of business is broken..

And I would agree with that - the only thing is, in this case, WMP did display metadata from Shoutcast, it's Icecast it's not displaying data from. So it's almost more like I'm saying "blame Icecast". Wink

But yes, I get your point, and it does bother me that I don't see WMP giving an ICY-MetaData field, which from what I'm reading is clearly wrong. That's what led me to wonder if it was waiting to see an "ICY 200 OK" come back before it did. But the only thing I truly have to "solve" right now is "how to get Icecast to behave like Shoutcast".

Thanks,
Galan

jcr · Posted: Wed Feb 17, 2010 7:37 pm Post subject:

What makes me wonder WMP is broke is "ICY 200 OK" never was a standardized reply..

What shoutcast makes and wants does not make this a "standatd"..
_________________
Epsilon Friends Radio Icecast Radio on CentovaCast admin panel. Icecast hosting

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

Why not determine first if the metadata is requested and supplied to the player. The ICY message could be worked around but there is no point in changing from a standard (http) to something non-standard if what you are wanting is not being asked for.

For all we know the problem may actually be the metadata interval size.

karl.

jcr · Posted: Wed Feb 17, 2010 8:24 pm Post subject:

Hi Karl,

From what I couls trace WMP problem depends on very random factors:
1) version and patch level
2) windows version

This clearly sounds like a wmp bug.. I had to explain this ti many of my customers and listeners o various streams here Smile

_________________
Epsilon Friends Radio Icecast Radio on CentovaCast admin panel. Icecast hosting