The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: xPLRio.net Current Situation


  • Subject: RE: xPLRio.net Current Situation
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Sat, 10 Jul 2004 13:05:08 +0100

Yet another update...

Just tidying up a few loose ends, and the first shoutcast release should be
available shortly (will post when it's ready).

The update zip will include a new streams.xml as the layout has changed
(also has a new rio.bin). Once the service has been restarted it's
necessary
to do a scan to update the shoutcasts (don't need to do a clear, so it's a
quick scan). If you have some specific shoutcasts you want to add to (or
replace with) the defaults then you can edit streams.xml in notepad before
the scan.

One limitation (that will be revisited later) is that only shoutcasts that
can be accessed directly via an ip:port (or domain:port) can be used, you
cant use one's that need a url due to an issue converting char to byte data
types in vb.net).

So 213.83.45.23:8080 is ok

Music.xplhal.co.uk:2110 is ok

But something like http://radio.myshout.com:1200/1030/eng
is not usable.

Most shoutcast stations seem to have a direct ip:url combination available
though.

Where you have more than one ip:port combination available for a shoutcast
you can enter it multiple times in streams.xml. Where the title is the same
xplrionet assumes it is the same station and if it fails to connect on the
first ip:port it will try the next until the list is exhausted.

If anyone has some good shoutcast stations please let me know and I'll add
them to the default list...

Looking forward to the bug reports ;-)

Regards
Tony





xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.