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]

Details of next xPLRioNet Release - for comment


  • Subject: Details of next xPLRioNet Release - for comment
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Fri, 30 Jul 2004 11:56:18 +0100

Hi all,

This weekend (hopefully) will see the release of beta v3.6.

This release will allow the injection of text-to-speech into Exstreamer's
&
SliMP3's as well as Rio's (currently only Rio can TTS).

It will also allow synch'd rio's to stay in synch when passed TTS (though
maybe not in this release).

For those who are not aware - the MS SAPI5 speech library, when used with
.net, doesnt like it when another app tries to use the library.

To get around this a new xPLRioNet 'helper' application will be released
(xPLRioNetTTS) which replaces BOTH the existing xPL_TTS (vb6 and vb.net)
and
xPL_RioTTS (vb6).

This application will be a windows service, as per xPLRioNet.

The part of xPLRioNetTTS that replaces xPL_TTS will also allow soundcard
selection (as per the vb6 version).

The web server side (the replacement part for xPL_RioTTS) will allow the
text to have .mp3 appended, and where this is detected the software will
use
LAME to encode the TTS to mp3 before returning the stream.

Eventually speech recognition will also be included.

xPLRioNet will use the new program by way of a setting in xplrionet.xml, to
allow Rio's to use the old software if necessary for some users who have
other TTS app's that won't function with a .net app using the library.

Any thoughts/comments/worries etc please?

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.