RE: MSVC++6.0 STL Appears to work fine now
Does creating a Relatable profile/signaturing your music work with the MS STL? Isaac On 06-Feb-2001 Gary R. Van Sickle wrote: I've been building from CVS using the STL that comes with MSVC++6.0 for quite a while now, and everything seems to be working fine (particularly now that somebody fixed the MusicBrowser crashing bug). Would the Powers That Be accept a patch removing NOMINMAX from the makefiles? Gary R. Van Sickle ([EMAIL PROTECTED]) Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
sigapp now available
I've created a standalone audio signature generation program that will take in an MP3 file and kick out the ASCII signature for that track. To build this app, do this after the configure in freeamp: make -f Makefile.towav sigapp This creates the sigapp application. Right now it has no ID3 support -- it just generates the signature from the audio track. I'll work to include ID3 support soon. If you'd like to use this, make sure you have the latest and greatest musicbrainz client lib installed. --ruaok Freezerburn! All else is only icing. -- Soul Coughing Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
[ANNOUNCE] 2.0.1 for AlphaNT now available
Once again Michael Rich has created an installer for AlphaNT. It is now available on the website! elrod ___ [EMAIL PROTECTED] http://www.freeamp.org/mailman/listinfo/freeamp-dev
Re: And now...
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 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] http://moon.eorbit.net/~robert
Re: And now...
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 strings as two separate packets to FreeAmp on it's receiving (the 1 +) 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 payload 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, Bruce [EMAIL PROTECTED] wrote: 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 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] http://moon.eorbit.net/~robert
Re: And now...
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...
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
