The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: wma support?


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

xPLRioNet - Details of next release


  • Subject: xPLRioNet - Details of next release
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Thu, 12 Aug 2004 18:09:39 +0100

Hi all,

Version 3.6d of xPLRioNet will be published tomorrow evening sometime.
Fixes/Changes are as follows:

Fix for crash caused by pressing skip in quick succession

The TTS changes described in a previous post (final details of the changes
will be posted tomorrow).

Due to tts causing issues with synch/shoutcasts etc a new rio.bin will also
be published that uses double-buffering, instead of flushing the current
mp3
data.

Basically it has a buffer for the mp3 stream and a buffer for the tts
stream. As soon as sufficient tts data is available it will start playing
the tts, and then resume playing the mp3 stream with no loss of mp3 data
(so
in effect it pauses the mp3 stream).

This means synch should not be effected by tts, and shoutcast connections
will not be lost by tts usage (caused by buffer running too low).

Exstreamer and Slimp3 users should see improvements in the TTS support too.

Broadcast (i.e.  target=*) tts.basic messages will now be actioned (if
ttsenabled=y in xplrionet.xml)

xPLRioNetTTS has various improvements to support xPLRioNet and now uses the
default voice in the xpl configuration where no voice is specified.

Issues with synchronisation of the Rio's will be addressed in v3.6e,
hopefully this weekend too.

Regards
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.