[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: xAP Speech 1.4 Released
- Subject: RE: xAP Speech 1.4 Released
- From: "Paul Gale" <groups@xxxxxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 14:16:41 -0000
Hey Gregg,
Yes - this delay is caused by the voice loading into ram etc and
initialising.
I used to have a really long delay - 30-40 seconds, but with a faster
machine it's a lot quicker - however, I tend to stick with one voice.
The NeoSpeech voices are a lot quicker loading that the AT&T Natural
Voices BTW.
Paul.
> -----Original Message-----
> From: xap_automation@xxxxxxx
> [mailto:xap_automation@xxxxxxx] On
Behalf Of Gregg Liming
> Sent: 12 December 2006 13:40
> To: xap_automation@xxxxxxx
> Subject: Re: [xap_automation] xAP Speech 1.4 Released
>
> Hi James,
>
> Quoting James Traynor (12/11/06 9:10 PM):
> > A new update with three new features, especially suited to
multi-zone
> > sound routing
>
> This app is exceptional! I now have it controlling an xAP
NetIOM--which
> in turn controls a set of relays for switching speakers using a
constant
> voltage PA system.
>
> One nuance that can be problematic, however, is a noticeably delay
> whenever switching between voices. Once the switch occurs, successive
> TTS using the same voice incurs no obvious delay. But, switching to a
> new voice always does. Is this an artifact of SAPI that is outside of
> your control? FWIW: I'm using two NeoSpeech voices (Kate and Paul).
>
> Gregg
>
>
>
> Yahoo! Groups Links
>
>
>
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|