I raised the question of Ultravox streams when the XMPlay AAC plugin was first released. The answer then was that it wasn't possible to develop the plugin to enable these streams to be played. The trouble with in_mp3.dll is that these days it works only in conjunction with another file (nscrt.dll), which XMPlay doesn't like at all. So unless someone can come up with a new idea, these streams can be played only in Winamp.
This fact made me think different way. So, I downloaded Winamp 2.95 from the archive and got an in_mp3.dll (v 2.96) from there (ultravox support for in_mp3 was added since 2.92). It still doesn't work.
The trouble (need of nscrt.dll) with Winamp 5.x in_mp3.dll can be easily solved by copying nscrt.dll to the XMPlay folder. But it still doesn't work.
Here's a 2.96 in_mp3.dll: http://flash41.narod.ru/in_mp3.dll
Please provide an example stream URL, to see if XMPlay can be made to forward them to the plugins.http://www.winamp.com/bin/om/xm/xmtune.pls?id=radio:aggregate:22317
These streams are delivered by their own protocol (uvox://). I don't know if there are any other XM streams using http:// protocol. Maybe the fact that uvox protocol is used makes these difficulties.
Update (my small investigation of uvox protocol):
An example of uvox stream: uvox://firehose-bbnm.stream.aol.com/stream/22227 (here also goes some authentication keys (like this: ?authToken=r%3D1832976%26sid%3D21727%26expires%3D1183840461847%26csum%3Da8edb9e8bb60f1329a4711e230700912&uid=&sessid=)
but we can cut them from the URL)
And here's what my proxy server showed (think that it's a sniffer
Stream URL: http://firehose-bbnm.stream.aol.com:80/stream/22227
(direct use of this link by Winamp causes "HTTP/1.1 400 Bad Request" error.
Using the above information, I can try to describe a simple uvox protocol scheme:
1. Player gets a uvox:// link with authentication parameters (that we can cut out from the URL) from the .pls file (for example, http://www.winamp.com/bin/om/xm/xmtune.pls?id=radio:aggregate:22317
2. Then it goes by this link (for example, uvox://firehose-bbnm.stream.aol.com/stream/22227) appending :80
at the end of domain name and http://
instead of uvox://
. Plus, it appends a custom content-type information - "misc/ultravox
3. After this, it begins to decode the stream.
P.S. Hope this will help.
P.P.S. Sorry for my a-bit-stupid English.