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: xPLMediaNet Beta v2.1 Released


  • Subject: RE: xPLMediaNet Beta v2.1 Released
  • From: "Neil Frost" <neil@xxxxxxxxxxxxx>
  • Date: Tue, 23 Aug 2005 23:01:33 +0100

Hi Tony,

Got it working straight off, will play over the next few days...

Just a quick one, how do I change the name of the units?

Thanks
Neil

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On Behalf =
Of Tony Tofts
Sent: 23 August 2005 17:46
To: ukha_xpl@xxxxxxx
Subject: [ukha_xpl] xPLMediaNet Beta v2.1 Released

Hi all,

Have just made the first public beta release of xPLMediaNet at http://www.x=
plhal.com

The website (hopefully) explains how to install

Existing xPLRioNet users who are going to continue using it for MVP
support=
need to disable Rio/ExStreamer/SliMP3 support in xPLRioNet and pay particu=
lar attention in xPLMediaNet to choose a client port range and other ports
=
(like web server) that do not clash with any still being used by xPLRioNet

I'd like to say a big thanks to the xPLMediaNet testers (and also those
who=
helped with xPLRioNet both testing and on code development as xPLMediaNet =
borrows heavily on the xPLRioNet code)

As time allows the next device to be supported in xPLMediaNet will be the
M=
VP, along with new source modules for Pictures and Videos. Hopefully the
me=
nu's will be much improved too.

Once MVP support is complete I'll be preparing a developer package so
other=
developers can create modules and add sources and devices etc So hopefully=
we'll also see improved replacements for existing modules too...

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.