The ice-* headers are the standard protocol for connecting to icecast2, the trouble is making all source clients adhere to the standard. The option is to be very militant about it, and basically deny any source clients that do not connect with the ice-* headers , but we chose the more compatable route...although there is a limit to this compatability....I would strongly urge darkice to use the ice-* headers (including the new ice-audio-info header) to provide stream information to icecast2. oddsock At 09:50 AM 7/9/2003 -0400, you wrote:>On Wed, Jul 09, 2003 at 06:38:33AM -0700, mark burdett wrote: > > yes this is darkice. perhaps we could work in 'icy-public' support...? > >Or begin a standardisation process and modify darkice to comply with it. ><p>--- >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-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.
On Wed, 9 Jul 2003, Arc wrote:> > yes this is darkice. perhaps we could work in 'icy-public' support...? > > Or begin a standardisation process and modify darkice to comply with it.The problem is that the icy headers are those used by the shoutcast server and sources, and this has been reverse-engineered, not published as a standard. So, the deal would be to find out what the shoutcast DSP uses (or what the shoutcast server expects) and standardise to that. Geoff. --- >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-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.
yes this is darkice. perhaps we could work in 'icy-public' support...? --mark On Tuesday, Jul 8, 2003, at 19:58 US/Pacific, Arc wrote:> On Tue, Jul 08, 2003 at 03:40:42PM -0500, oddsock wrote: >> what source client is generating that ? > > I believe they run darkice, Mark Burdett would have to supply more > specific details as this is a relay of their lofi-mp3 stream. > >> The icy-* header that icecast is looking for is icy-pub, not >> icy-public...I >> don't think there ever *was* an icy-public, the two variations were >> ice-public and icy-pub. > > Well that's what happens when there isnt a documented standard. > Seriously, and no offense intended, but the whole "b"/"bitrate" > variation in the YP implementation plus "icy-br" and other > variations... > > You can't expect compliance to an undocumented/inconsistant standard. > Darkice generating icy-public suprises me very little, but I will say > that these streams were previously working and stopped with a recent > upgrade. > > <mime-attachment>--- >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-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.
On Wed, Jul 09, 2003 at 06:38:33AM -0700, mark burdett wrote:> yes this is darkice. perhaps we could work in 'icy-public' support...?Or begin a standardisation process and modify darkice to comply with it. <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/attachments/20030709/636b89f9/part.pgp