's what I've got so far:
    1> I open one socket on my side at server initialization (I let Java pick the 
local port) for
sending UDP packets
    2> Parse the GET HTTP....headers when FreeAmp connects and obtain it's receiving 
UDP port (usually
10000 +)
    3> Send the x-audiocast.... strings as two separate packets to FreeAmp on it's 
receiving (the
10000 +)
port (to be more specific: I create a datagram packet with the FreeAmp IP address and 
the UDP port it
gave me
in the GET headers, and send the packet off).
   4> I've verified that "something" has control of the passed in FreeAmp UDP port by 
trying to open
another UDP
port using that same number and something (FreeAmp I presume) always owns that port.

I'm pretty damn sure those are the correct steps. I'm also careful to create byte 
arrays for the data
of the UDP packet. Is there any way to see what FreeAmp is capturing on its UDP port? 
Could this have
anything to do with byte order (i.e. big/little endian) - java is always big endian.

Still scratching my head on this one,



> On 12 Aug, Bruce Oblander wrote:
> > Nope...this is for a "Shoutcast" type stream. I've gone so far as to capture the 
>network packets
> > passed to FreeAmp and it looks like the "x-audiocast...." commands are OK (and the 
> > really are sent to FreeAmp) so me thinks you are correct but that leaves me at a 
>loss. Is the
> > UDP port used for FreeAmp title streaming something different from java's 
>"Datagram" socket?
> > This is pretty hard to screw up but I never cease to amaze myself.
> Thanks for refreshing my memory of your project.
> FreeAmp will open the server port and then send the stream server a
> x-audiocast-udpport: header as part of the stream request. The title
> stream information should be sent to that port. Are you doing that?
> --ruaok         Freezerburn! All else is only icing. -- Soul Coughing
> Robert Kaye -- [EMAIL PROTECTED]

Reply via email to