[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-accessibility
Subject:    Re: [Kde-accessibility] KTTSD does not speak, no way to debug
From:       Robert Vogl <voglrobe () web ! de>
Date:       2004-07-31 14:13:57
Message-ID: 200407311613.58102.voglrobe () local ! de
[Download RAW message or body]

Am Samstag, 31. Juli 2004 01:18 schrieb Gary Cramblitt:
> On Friday 30 July 2004 02:38 pm, Robert Vogl wrote:
> > Hi Gary,
>
> Thank you Robert.
>
> I believe the following code in hadifaxspeech.cpp isn't working for you
> because the Hadifax plugin never receives the processExited signal:
>
> void HadifaxSpeech::processExited(KProcess *) {
>    }
> }

> Why it doesn't work for you, but does work for me and others is a mystery. 

I think the whole KDE-Multimedia stuff is a mystery. In particular if you try 
to run it in threads. I think most of that KDE stuff is not thread-save. I 
also had to make some modifications in KSayIt and it seems to me I found a 
reliable solution now. I can send you the code, if you are interested. 

> It probably has something to do with the plugin running from a worker
> QThread (speaker.cpp).   What version of KDE and Qt are you running?

KDE 3.2.1, QT 3.2.1.

>   1.  Plugins no longer need to audibilize the speech.  They need only
> create a wave file from the text.

How's the handling of those wave files? It should be avoided to blow up the /
tmp/-dir with terrabytes of old wave files from KTTSD. 

Greetings,

-- 
Robert Vogl
voglrobe@web.de
_______________________________________________
kde-accessibility mailing list
kde-accessibility@kde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility
[prev in list] [next in list] [prev in thread] [next in thread]