[Kde-accessibility] Current state of KTTS / KSpeech Interface
jeremy at scitools.com
Fri Feb 29 22:08:27 CET 2008
On Tuesday 26 February 2008 11:42:43 Jeremy wrote:
> On Tuesday 26 February 2008 04:05:04 Conrad Hoffmann wrote:
> > Hi folks!
> > I was trying to port my Kopete KTTS plugin  to KDE4, thus trying to
> > get things "spoken" by KTTS. At first, I followed Instructions given at
> > . The jobs showed up in the KTTSMgr config, and it was even indicating
> > that they were beein spoken. I just couldn't hear anthing. I immediately
> > figured my backend just didn't work properly. I can currently only try
> > festival, und it does not work on the command line because of sound
> > driver issues.
> > Unfortunately, in a fit of curiosity, I tried KMouth. And to my dismay,
> > it talked to me, crisp and clear.
> > I tried in all possible ways (qdbus cli, generic QDBusInterface, KSpeech
> > Interface) to reproduce, what KMouth does (e.g, I noticed it uses job
> > priority warning). In the end, I used _the exact same code_ as KMouth.
> > But it still won't speak my messages.
> > Does anyone have some clues for me? Is KTTS even considered to work,
> > currently? If not, how does KMouth work? If so, how do I get my stuff to
> > work?
> > For reference:
> > I last compiled trunk like 12 hours ago, but the problem was there
> > before. KMouth does use the kde4 speech subsystem (at least the jobs show
> > in KTTSMgr). All other jobs show up there, too. They just don't get
> > spoken (i.e. I can't hear anything)
> > Any ideas would be greatly appreciated!
> > Please CC me off list, I am not subscribed.
> > Regards, conrausch
> >  http://www.kde-apps.org/content/show.php?content=30900
> > 
> > http://api.kde.org/4.x-api/kdelibs-apidocs/interfaces/kspeech/html/index.
> >ht ml
> I've always wondered about the purpose of that plugin. (I've used it
> before) C ouldn't the same functionality be added by fixing kopete's
> notifications to se nd the contents of the incoming/outgoing message in the
> notification? It work s fine for konversation (in kde3) this way, but not
> for kopete for some reason ...
> I just tried in kopete in kde4 also, and it has the same problem. (Just
> insta ll kdeaccessibility, and try to set any kopete notification to speak
> the notif ication message, or name, and you'll see what I mean.
Weird, after either a reboot, or a rebuild of kde it works somewhat. Though
the notification messages are still not very helpful ("Incoming message") is
less usefull than the text of the message itself ;)
> kde-accessibility mailing list
> kde-accessibility at kde.org
More information about the kde-accessibility