SHOUTcast technical manuals?
 

Where would I pickup a technical manual on the details regarding the UDP stream connection, data stream formats, etc, if I wanted to write my own listening software?

I am only concerned with .WAV (uncompressed) for now for simplicity, so if something other than SHOUTcast would be more appropriate, please let me know.

Any help would be greatly apprecaited.

thanks,
dane

SHOUTcast uses TCP not UDP.

TCP, fine... that's not that big a deal. Do you know where I can get the details for the stream format, connection, disconnection, etc?

dane

if you know about sockets and tcp streams then u dont really need the docs, just create a listening port, then when a client connects, make them communicate

buffer the incomming connection, then send it on a different port to clients that connect to it

shouldn't be to hard

dont think there is any docs on this, but maybe im wrong

Someone pointed me to a website that has the Shoutcast Metadata format, which was helpful (http://www.smackfu.com/stuff/programming/shoutcast.html), but indicated that Shoutcast only supports MP3 (although I would imagine it would stream any filename you gave it?)..

I am familiar with sockets, but don't want to mess with Linux. DOS apps don't lend themselves to networking well, and I'm not a windows programmer. I'm an embedded systems guy.. I've got a couple options I can use though...

what exactly are you trying to do

creating a source for the shoutcast server, or making a shoutcast server???

if you are trying to make a source then i see why the docs would be very important to u

about the formats, it supports video and mp3 so i dont see why wav is a problem, although wav is a very bulky format, so its not really a good option for streaming

Well not true. Do to RIAA and stuff. You can't stream CD's, midi, or any other format besides

wav, and MP3

I have more documentation here.

http://forums.radiotoolbox.com/viewtopic.php?t=74

Thanks for the additional web link, I'll check it out.

As for what I'm trying to do, no I am not simply setting up a server. I am creating a listening device that I want to support multiple server protocols, and obviously need those protocols to support the server...