[icecast] icecast acceptable headers

oddsock oddsock at oddsock.org
Thu Nov 20 19:47:11 PST 2003



the problem is probably that nsvcap most likely tries to attach using the 
"shoutcast source" protocol, which is some strange variation of HTTP (but 
definitely not HTTP).... It's strange-ness and non-HTTP-ness is the reason 
why icecast doesn't support connecting the Shoutcast DSP to it.  So I don't 
think any magical combination of headers will get live NSV 
working...although if we ever build in Shoutcast strange-non-HTTP-ness into 
icecast, it should work no problemo...The problem, to support connecting 
the SHoutcast DSP (and probably NSVcap) we have to majorly hack icecast to 
support this "custom" protocol, which we really don't like doing :)

oddsock
At 08:33 PM 11/20/2003 -0700, you wrote:
>this is what i have so far that works, well sorda
>------------------------
>Content-type:audio/mpeg
>ice-mount:/crap
>ice-name:[L A T E X - T V] - LIVE!!
>ice-genre:Industrial, EBM, Electronic
>ice-public:0
>ice-bitrate:280
>ice-url:http://www.latexradio.com
>ice-description:boooo
>ice-audio-info:bitrate = 280, 152kbps video, 128kbps audio
>
>
>content type works
>cant figure out the mount or how to set that properly, it just defaults to /
>genre, url, description dont work either.
>
>As you can see im testing the nsvcap tool to see if i can connect to the
>icecast2 server, on demand works fine if your video file is encoded
>correctly
>http://mediacastone.com:8006/video-demo/sensation_2002_white_edition_djs_version.nsv
>i know im probably pissing in the wind but what the heck, boredom brews
>curiosity :)
>any direction would be appreaciated.
>
>
>
>
>
>
>
>Dave St John
>Mediacast1 Administration
>----- Original Message -----
>From: "Michael Smith" <msmith at xiph.org>
>To: <icecast at xiph.org>
>Sent: Thursday, November 20, 2003 7:51 PM
>Subject: Re: [icecast] icecast acceptable headers
>
>
> > On Friday 21 November 2003 13:17, Dave St John wrote:
> > > Anyone know of the correct header that are sent to the icecast2 server?
> > >
> > > example the ones sent to a shoutcast server are
> > > icy-name:whatever station
> > > icy-genre:Industrial, EBM, Electronic
> > > icy-pub:1
> > > icy-br:256
> > > icy-url:http://www.mediacast1.com
> > > icy-reset:1
> > >
> > > just need to know what the equivelant is for icecast2.
> >
> > The same. ice-* or icy-* headers from the source are forwarded as-is to
>the
> > listening clients, with the exception of the password header, where
>present.
> >
> > This means that if the client understands the shoutcast ones, and you use
>the
> > shoutcast ones, it'll work as-is.
> >
> > 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-request at xiph.org'
> > containing only the word 'unsubscribe' in the body.  No subject is needed.
> > Unsubscribe messages sent to the list will be ignored/filtered.
> >
>
>
>--- >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 at xiph.org'
>containing only the word 'unsubscribe' in the body.  No subject is needed.
>Unsubscribe messages sent to the list will be ignored/filtered.

<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 at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.



More information about the Icecast mailing list