On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote:> > Is the metadata relayed to connecting clients. i.e. take a client that > supports shoutcast-style metadata, like winamp (and probably most others). > Connect as a listener to the relay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is > unlikely, though - that code hasn't been changed lately AFAIK)Or connect via telnet and see what's really going on ;-) HTTP/1.0 200 OK Content-Type: audio/mpeg icy-br: 64 icy-genre: Talk icy-metaint: 8192 icy-name: Enemy Combatant Radio icy-notice1: <BR>This stream requires Winamp<BR> icy-notice2: SHOUTcast Distributed Network Audio Server/FreeBSD4 v1.9.2<BR> icy-pub: 1 icy-url: http://sf.indymedia.org/ Server: Icecast 2.0-alpha2/cvs Yes, it copies over the icy headers exactly as-is... Now what's interesting, prehaps this is a bug??? this is the headers as given by a Icecast2 origionated stream: HTTP/1.0 200 OK Content-Type: audio/mpeg ice-bitrate: 16 ice-description: SF Indymedia ice-genre: Talk ice-name: Enemy Combatant Radio ice-public: 1 ice-url: http://sf.indymedia.org/ icy-metaint: 16000 Server: Icecast 2.0-alpha2/cvs notice that, with exception of the last, they're all ice-* not icy-*... prehaps this is incompatable with the way most players operate to get stream data? Is this a typo?> I couldn't say whether or not this metadata is propogated to the stats core > (and I think from there to the YP update stuff?). Maybe that's what is > missing.I don't know because I don't have a shoutcast server in front of me to compair it's YP with ours, but yes, Icecast2 is not sending this information to YP servers. I would very much prefer if it were to send it in Icecast2 YP style and not Shoutcast (ICY) style, prehaps running the field names through a translation table? Just the three are really needed, tho song info and bitrate are needed too, but the stream name, description, and genre are musts... the associated URL would be good too, the listenurl is provided by Icecast2 itself, and the rest of the information isnt really that important.> > What's the alternative to <relay-shoutcast-metadata> if you want to > > relay Icecast2 metadata vs shoutcast metadata, so I can fix the > > non-shoutcast entries? Do you use this for icecast1 servers as well? > > This option turns on relaying of shoutcast-protocol mp3 metadata. icecast 1.x > optionally uses this (it also has a second, UDP based, way of doing metadata. > Few clients support it, icecast2 doesn't support it), and icecast2 uses it if > it's using metadata at all.Is there harm in having it turned on for 1) MP3 streams which origionate from a Icecast2 server, and 2) for Ogg streams origionating from a Icecast2 server? Should it be on or off, in other words, for best preformance? -------------- next part -------------- A non-text attachment was scrubbed... Name: part Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.xiph.org/pipermail/icecast-dev/attachments/20030625/f8d81d04/part.pgp
On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote:> > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add > <relay-shoutcast-metadata>1</relay-shoutcast-metadata> > to the appropriate <relay>It's not working... how long has this been in CVS? Actually all the relay entries, even the ones that are relaying Icecast2, have it. Here's the entry for "Enemy Combatant Radio"'s hifi MP3 that is not working: <relay> <server>radio.us2.indymedia.org</server> <port>8200</port> <mount>/</mount> <local-mount>/sf-hifi.mp3</local-mount> <relay-shoutcast-metadata>1</relay-shoutcast-metadata> </relay> Here's what's being sent to, and responding from, the YP CGI: Wed Jun 25 07:05:52 2003 < [MiniFieldStorage('action', 'add'), MiniFieldStorage('listenurl', 'http://liveradio.indymedia.org:8001/sf-hifi.mp3'), MiniFieldStorage('type', 'MP3 audio')]>YPResponse: 0 YPMessage: Stream name is required. And here's the header from the source server: icy-name:Enemy Combatant Radio icy-genre:Talk icy-url:http://sf.indymedia.org/ Content-Type:audio/mpeg icy-pub:1 icy-br:64 Clearly, the stream name is not being relayed from shoutcast. I compiled this icecast from CVS less than a week ago, I believe, in an attempt to fix YP and thus make it useable. What's the alternative to <relay-shoutcast-metadata> if you want to relay Icecast2 metadata vs shoutcast metadata, so I can fix the non-shoutcast entries? Do you use this for icecast1 servers as well? <p> -------------- next part -------------- A non-text attachment was scrubbed... Name: part Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.xiph.org/pipermail/icecast-dev/attachments/20030625/80e5943b/part.pgp
On Wednesday 25 June 2003 15:11, Arc wrote:> On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > > icecast1/shoutcast/etc so that this information is available to YP > > > > Eh? It does. I even tested that with someone's shoutcast stream. It > > works. Just add > > <relay-shoutcast-metadata>1</relay-shoutcast-metadata> > > to the appropriate <relay> > > It's not working... how long has this been in CVS? Actually all the > relay entries, even the ones that are relaying Icecast2, have it. > Here's the entry for "Enemy Combatant Radio"'s hifi MP3 that is not > working:Is the metadata relayed to connecting clients. i.e. take a client that supports shoutcast-style metadata, like winamp (and probably most others). Connect as a listener to the relay. Do you get metadata? You should. If you don't, the metadata relaying could have been broken (I think this is unlikely, though - that code hasn't been changed lately AFAIK) I couldn't say whether or not this metadata is propogated to the stats core (and I think from there to the YP update stuff?). Maybe that's what is missing.> What's the alternative to <relay-shoutcast-metadata> if you want to > relay Icecast2 metadata vs shoutcast metadata, so I can fix the > non-shoutcast entries? Do you use this for icecast1 servers as well?This option turns on relaying of shoutcast-protocol mp3 metadata. icecast 1.x optionally uses this (it also has a second, UDP based, way of doing metadata. Few clients support it, icecast2 doesn't support it), and icecast2 uses it if it's using metadata at all. Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.