RE: TTS append / queueing

I could imagine a situation in which a page invoked multiple distinct TTS engines (expertise in different languages being one common use case), so I wouldn't want the TTS object to be unique, but I think it would make sense to have a single TTS object for each engine and then have a method like  'addUtterance' with the kind of behavior that Dominic mentioned (queue vs abort, plus the possibility for different voices/parameters for each utterance.)

- Jim

-----Original Message-----
From: Hans Wennborg [mailto:hwennborg@google.com] 
Sent: Wednesday, April 25, 2012 9:59 AM
To: Dominic Mazzoni
Cc: Jim Barnett; public-speech-api@w3.org
Subject: Re: TTS append / queueing

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?

Thanks,
Hans

Received on Wednesday, 25 April 2012 14:32:50 UTC