More on the ibmtts module trouble

[Michael Whapples]

Hello,
A little further digging around on reproducing this bug actually reveals 
that for some reason my python code is not using the TEXT priority 
level. I will need to try and work this out or may be you might know the 
reason (eg. might another python application such as orca affect the 
priority level).

Anyway by explicitly setting the priority level before running the two 
speak commands I mention reveals that this bug stands for priority 
IMPORTANT, ibmtts does not say the second message, so this means the 
ibmtts module is deviating from the documented behaviour.

Can you reproduce this bug now? Would you appreciate the ibmtts module 
logging output?

Michael Whapples
On -10/01/37 20:59, Hynek Hanke wrote:
> On 7.12.2010 23:02, Michael Whapples wrote:
>> c.speak("hello to everyone in the ")
>> time.sleep(0.1)
>> c.speak("world")
>> This is using the default priority.
>
> This is Priority.TEXT, so the first message is supposed to be
> interrupted and discarded and you should start hearing the
> second message ("world") after 0.1 seconds.
>
> Of course in practice, the delay can be longer than 0.1
> seconds considering the latencies of stop and new
> playback, which depends on the synthesizer,
> audio system used etc.
>
> If IBMTTS doesn't do this, it it can have quite bad
> effects for the end user experience.
>
> The next step would be to enable module debugging
> and try to see where the delay is. Does the module
> get a STOP command from the server? Does it react
> on it quickly enough?
>
> Best regards,
> Hynek
>
>
>