More on the ibmtts module trouble

[Michael Whapples]

Thanks for the response Chris, it seems to be when priority is important 
that this bug shows. Do you find the bug if you set priority to 
important before doing the test I said?

I seem to be getting the answer that text should be the server's default 
priority but for me with the default priority setting commented out in 
speechd.conf I seem to get important as the priority level.

Michael Whapples
On -10/01/37 20:59, Christopher Brannon wrote:
> Michael Whapples<mwhapples at aim.com>  writes:
>
>> This is time sensitive, the second message must be sent while speechd
>> is still speaking, so you may want to put it in a script or a
>> function. Try this for the espeak module and then try it with the
>> ibmtts module. With espeak both messages get spoken, with ibmtts only
>> the first is spoken.
> I can't reproduce it.  I did as you suggested.  Here is your example, in
> the form of a runnable script.
>
> ===CUT===
> #!/usr/bin/python2
> import speechd.client
> import time
> c = speechd.client.SSIPClient('foo')
> c.set_output_module('ibmtts')
> c.speak("hello to everyone in the ")
> c.speak("world")
> c.close()
> ===CUT===
>
> Both modules speak both messages.
>
> I haven't changed the default priority in my configuration file.
> If I remember correctly, the server's default priority is "message".
>
> -- Chris