More on the ibmtts module trouble
mwhapples at aim.com
Wed Dec 8 15:57:16 CET 2010
Firstly I will get logging output showing this, I guess its only the
ibmtts module log file your interested in. What logging level would you
like, shall I set it to the highest?
Now on the initial priority level, that seems to be a separate bug. I
have sent another message on this, but a quick summary leads to:
* If the setting for default priority is not defined in speechd.conf (I
include in this where the definition may be there but is commented out),
then priority seems to get set to important.
* If I define the default priority level to be text in speechd.conf then
text is correctly set as the default level.
* No other application is causing this difference on my system, orca
speech output changes according to the two above situations and orca is
the only other application using speech-dispatcher on my system.
* It seems like others expect what I observe, orca output isn't good
when I explicitly set default priority to be text, this means all others
using orca with speech-dispatcher must not have text as the default level.
On -10/01/37 20:59, Hynek Hanke wrote:
> On 8.12.2010 13:50, Michael Whapples wrote:
>> 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 do not have an explanation for this except that you could
> have DefaultPriority set in your speechd.conf to something else.
>> 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).
> Also note that the old deprecated Client.say() method uses
> priority MESSAGE by default and we keep it for backward
> compatibility, so it is important to make sure you are using
> the correct SSIPClient.speak() .
> If neither of these is the reason, it would be useful to try to
> find out what happens. Pririties should not be affected
> by other connections/applications.
>> 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.
> Yes, that would be a bug.
>> Can you reproduce this bug now? Would you appreciate the ibmtts
>> module logging output?
> I personally can't reproduce ibmtts :-) but if you send logging
> output from the module, we should be able to understand
> something more.
> Best regards,
> Hynek Hanke
More information about the Speechd