On 13 Aug, Bruce Oblander wrote:
> Yes...here'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 HTTPheaders when FreeAmp connects and obtain it's receiving
>UDP port (usual
Yes...here'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 HTTPheaders when FreeAmp connects and obtain it's receiving
UDP port (usually
1 +)
3> Send the x-audiocast
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
>packets
> really are sent to FreeAmp) so me thinks you are correct but that l
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
packets
really are sent to FreeAmp) so me thinks you are correct but that leaves me at a loss.
Is the
UDP port used
On 6 Aug, Bruce Oblander wrote:
> Please excuse my ignorance but here's what my server is doingunsuccessfully:
> open a datagram socket with FreeAmp when FreeAmp connects (my server is a
>Datagram
> client)
> when stream titles change:
> send a datagram packet consisting of:
Please excuse my ignorance but here's what my server is doingunsuccessfully:
open a datagram socket with FreeAmp when FreeAmp connects (my server is a Datagram
client)
when stream titles change:
send a datagram packet consisting of: "x-audiocast-streamurl: couldBeAnything"
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 d
On 5 Aug, Ross Finlayson wrote:
> No! Please don't do this! The (RTP port)+1 is meant to be used for
> sending/receiving RTCP reports. If you send anything else on that port,
> you risk confusing receivers that listen for RTCP reports.
Oops, I'm showing my RTP ignorance again. :-) Thanks for
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 PRO
oops..
Ross Finlayson wrote:
> >In the case of RTP/multicast, the server will simply transmit the
> >titles one port number higher on the same multicast address.
>
> No! Please don't do this! The (RTP port)+1 is meant to be used for
> sending/receiving RTCP reports. If you send anything else
>In the case of RTP/multicast, the server will simply transmit the
>titles one port number higher on the same multicast address.
No! Please don't do this! The (RTP port)+1 is meant to be used for
sending/receiving RTCP reports. If you send anything else on that port,
you risk confusing receive
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
12 matches
Mail list logo
