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

Re: TTS append / queueing

From: Hans Wennborg <hwennborg@google.com>
Date: Wed, 25 Apr 2012 14:59:15 +0100
Message-ID: <CAB8jPheJoD8Nu8DFS05zBs5pV6YjJqk6cUqCepg+wjfd+WBn+Q@mail.gmail.com>
To: Dominic Mazzoni <dmazzoni@google.com>
Cc: Jim Barnett <Jim.Barnett@genesyslab.com>, public-speech-api@w3.org
On Tue, Apr 24, 2012 at 23:32, Dominic Mazzoni <dmazzoni@google.com> wrote:
> 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();

Yeah, it feels a little weird to create a bunch of different TTS
instances if they're going to be referring to the same thing anyway.
Maybe we should just have a global TTS interface, and pass in
TTSUtterance objects or something like that to it?

Received on Wednesday, 25 April 2012 14:00:13 UTC

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