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]

xPLRioNet Beta v3.6 Released


  • Subject: xPLRioNet Beta v3.6 Released
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Sun, 8 Aug 2004 17:14:17 +0100

Hi all,

have published the latest xplrionet release at www.xplhal.com

This version has the new 'push' rio client and as such requires that all
rio's be rebooted after the update is applied as the new service and binary
file are totally incompatible with the old versions.

Mike, please can you let me know if there are any issues running this on a
wireless rio please?

For text-to-speech support, this version requires the new xPLRioNetTTS
text-to-speech service (same page of the web site) be used "in place
of"
xpl_riotts (and xpl_tts if used). Once installed it is necessary to update
the control.xml file in the applications folder to set the tcp port that it
should bind to and then start the service. You also need to obtain lame.exe
(a link and instructions are included in the download section).

It is also advisable, but not compulsory, to add the following line to
xplrionet.xml:

<tts enabled="n" url="127.0.0.1:48000" />

enabled="n" means it repsonds to audio.rio announce requests, but
not
tts.basic messages. enabled="y" means it responds to both.

url= is the default ip and port used to locate the tts server, this is a
default value and does not override the config setting for each unit.

tts no longer breaks units in synch...

I'll be publishing a new 'to do' list in the next day or so.

Many thanks
Tony



[Non-text portions of this message have been removed]




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.