On Sun, 7 Mar 2004, Dale Ghent wrote:> What's the purpose of this NSV protocol?As far as I'm able to tell, and I admit to knowing very little indeed, I get the impression that it's something like Quicktime or Ogg (ie. a container format). Presumably it still uses HTTP(ish) protocols (i.e. TCP), but who knows. They reckon it's documented, so I guess you could dig up more info on it if you wanted to know. but like Oddsock said, why bother? We should only hope that Xiph get some (any) version of Theora out for playing with before Nullsoft Video sees the light of day, or we'll know where everyone's going to go.> I'm trying really hard not to get into a soapbox, but why is it that > the audio streaming community has such a hard-on for so many protocols.I'm guessing it's because people keep on finding situations that don't meet their requirements, so they write their own. Either that, or some people just want to make a buck, and that of course requires doing something that at least looks different which you can sell to people.> This YP who hates that YP > Poor protocol documentation on almost all of the above.FWIW, I'm pretty sure the new icecast YP spec is documented somewhere (I remember reading it), though I'm not sure if it's actually linked to from anywhere. Not sure if the icecast2 protocols are documented anywhere though, apart from the code itself. Geoff. <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-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.
On Monday 08 March 2004 18:18, Geoff Shang wrote:> FWIW, I'm pretty sure the new icecast YP spec is documented somewhere (I > remember reading it), though I'm not sure if it's actually linked to from > anywhere. Not sure if the icecast2 protocols are documented anywhere > though, apart from the code itself.There's no real icecast2 protocol documentation, so I'll add some here: Use HTTP. If you're writing a client, use the custom "SOURCE" method to provide a source. See, it's really simple when you just delegate 99% of the spec to the HTTP spec :-) <p>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.
On Mar 7, 2004, at 4:36 PM, oddsock wrote:> well, I'm not sure that's the reasoning... > > from Tom P : > "i'm making changes to yp which will detect the presence of mp3pro > within a non-encapsulated stream and prohibit its listing. nsv/nsa is > an open protocol...........What's the purpose of this NSV protocol? Is it some sort of container protocol that Nullsoft is pushing as some "standard" in audio webcasting? I'm trying really hard not to get into a soapbox, but why is it that the audio streaming community has such a hard-on for so many protocols. I'm not taking about codecs, I'm talking about ways to get the content from point A to point B. Off the top of my head, we have: ICY vs. HTTP. UDP vs. inline metadata RTP/SDP vs. TCP This YP who hates that YP Poor protocol documentation on almost all of the above. Spite on a policy level between software designers (nullsoft vs. icecast vs. $codec etc.) And how many RFCs or IETF drafts are written on the subject? A quick search reveals SDP/RTP RFCs and _that's it_. I'm of the opinion that streaming audio on the Internet is neither as "free" or as "open" as people think it is. Everyone is hold up in their own sandbox, as it were, and it's just being perpetuated. /dale --- >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.