Re: And now...

[Bruce Oblander]

Got it...but one (well maybe two) more question:

I send "x-audiocast-streamurl: myurl" to FreeAmp *once* when it connects to my server.

I'm then sending "x-audiocast-streamtitle: trackTitle" to FreeAmp as the titles
change.

is this correct or did I mis-read the code?

Thanks!

bruce

[EMAIL PROTECTED] wrote:

 On  4 Aug, Bruce Oblander wrote:
  Sorry to break in here but...
 
  Mark and Rob, I'm the crazy guy working on the Java streaming mp3 server and was
  pondering the secret formula for feeding Title Streaming to FreeAmp. Ummm, what
  is it? Well, I confess, I'm just looking for shortcuts to avoid dissecting code.

 Well, it would be best for you to read io/src/tstream.cpp in freeamp
 and xmit/Transmitter.cpp (int CVS) of Obs.

 However, the quick upshot is this:

 The client creates a upd server sockets and when it connects to an http
 stream, it sends the port number to the remote server. The
 shout/icecast server will then transmit the title of the stream in the
 style of a http header.

 In the case of RTP/multicast, the server will simply transmit the
 titles one port number higher on the same multicast address.

 --ruaok Freezerburn! All else is only icing. -- Soul Coughing

 Robert Kaye -- [EMAIL PROTECTED]  http://moon.eorbit.net/~robert

Re: And now...

[robert]

On  6 Aug, Bruce Oblander wrote:
 Got it...but one (well maybe two) more question:
 
 I send "x-audiocast-streamurl: myurl" to FreeAmp *once* when it connects to my 
server.
 
 I'm then sending "x-audiocast-streamtitle: trackTitle" to FreeAmp as the titles
 change.
 
 is this correct or did I mis-read the code?

No, the url and title are each sent when a new stream starts, and in
the case of Obsequeuim every 10 seconds as well. However, the code may
be confusing, since it uses two seperate packets and not one large
packet to the send the url and title.


--ruaok Freezerburn! All else is only icing. -- Soul Coughing

Robert Kaye -- [EMAIL PROTECTED]  http://moon.eorbit.net/~robert