W3C home > Mailing lists > Public > public-speech-api@w3.org > April 2012

Re: TTS append / queueing

From: Dominic Mazzoni <dmazzoni@google.com>
Date: Tue, 24 Apr 2012 15:32:43 -0700
Message-ID: <CAFz-FYxaPGF0rzKn6xnQ39AA_miv8xhyye7FJC3LDiCiJ1dweg@mail.gmail.com>
To: Jim Barnett <Jim.Barnett@genesyslab.com>
Cc: public-speech-api@w3.org
On Tue, Apr 24, 2012 at 3:27 PM, Jim Barnett <Jim.Barnett@genesyslab.com>wrote:

> So, just to be clear,  when you create multiple instances of the TTS
> object, they all represent the same underlying synthesis resource.  If so,
> then your proposal looks  reasonable to me.  I was thinking that the TTS
> object represented the underlying synthesizer, so I didn’t think of
> creating a separate one.  It might  be good to make this explicit in the
> name of the object, but I don’t have a good suggestion – maybe ‘utterance’
> or something like that?

I agree, it's a little funny to me for each instance to be called TTS.

I think there may be a need for some global / static methods later, like
TTS.IsAnythingSpeaking or TTS.getVoices, so how about something more like:

var tts = new TTS.Utterance();

- Dominic
Received on Tuesday, 24 April 2012 22:33:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:27:22 UTC