How to configure Qtspeech
Gustav Degreef
gustav97 at gmail.com
Thu Sep 19 01:51:13 BST 2019
Oh, OK. Sorry I misread your post. Yes, I did use it a long time ago,
but it was around the time that jovie replaced it. I thought it was
dead. It is not in the opensuse repos for a long time. Maybe this is a
dumb question, but would it work with Qtspeech? Not sure if it makes
sense to use it going forward with the direction that accessibility is
going in KDE. Thanks, Gustav.
On 9/18/19 10:27 AM, Jeremy Whiting wrote:
> ktts is what jovie came from. It's much much older and does the same
> thing (ktts just got renamed to jovie when I refactored ktts to use
> speech-dispatcher instead of a bunch of it's own synthesizer modules).
>
> On Tue, Sep 17, 2019 at 8:24 PM Gustav Degreef <gustav97 at gmail.com
> <mailto:gustav97 at gmail.com>> wrote:
>
> Not sure what kits is. Gnome does not easily provide the
> functionality
> of Jovie. I don't want/need a screen reader, just text-to-speech
> capability from the clipboard, from selected text, etc. I've
> tried Orca
> on KDE and it's not simple. Gustav.
>
> On 9/17/19 9:31 PM, Jude DaShiell wrote:
> > Has anyone tried ktts yet? Last time I read here, orca was
> recommended
> > until whichever fully operation screen reader kde upstream
> decided to
> > support became ready for prime time.
> >
> > On Tue, 17 Sep 2019, Gustav Degreef wrote:
> >
> >> Date: Tue, 17 Sep 2019 20:52:33
> >> From: Gustav Degreef <gustav97 at gmail.com
> <mailto:gustav97 at gmail.com>>
> >> To: kde-accessibility at kde.org <mailto:kde-accessibility at kde.org>
> >> Subject: Re: How to configure Qtspeech
> >>
> >> Thanks Jeremy.
> >> I tried Kmouth and I had the same problem that I had with
> Okular.? I
> >> finally heard what the problem is.? There are two voices
> >> simultaneously.? One with an English accent which sounds like
> e-speak
> >> and the other simultaneously sounds like English with a foreign
> accent,
> >> something "Germanic". They are not perfectly in sync so I can
> hear one
> >> sort of alternating with the other.? I don't know where to
> begin to sort
> >> it out.? Thanks for taking the time, Gustav
> >>
> >> On 9/16/19 11:26 PM, Jeremy Whiting wrote:
> >>> Just did a quick check. It looks like kmouth does wrap
> QtSpeech. I'll
> >>> try it out tomorrow and see what it's lacking for your use
> case. Let
> >>> me know if you try it and find room for improvement also.
> >>>
> >>> On Mon, Sep 16, 2019 at 9:24 PM Jeremy Whiting
> <jpwhiting at kde.org <mailto:jpwhiting at kde.org>
> >>> <mailto:jpwhiting at kde.org <mailto:jpwhiting at kde.org>>> wrote:
> >>>
> >>>Â Â Â Hello Gustav,
> >>>
> >>>Â Â Â Unfortunately QtSpeech by itself isn't going to solve
> the problem
> >>>Â Â Â you're trying to solve. QtSpeech is just a library that
> wraps
> >>>Â Â Â speech sythesizers. On linux it wraps speech-dispatcher
> itself
> >>>Â Â Â (which in turn has modules for various synthesizers
> like espeak-ng
> >>>Â Â Â and festival.) In order to achieve the functionality of
> Jovie we
> >>>Â Â Â need a gui?? or at a minimum a context menu entry/thing
> in plasma
> >>>Â Â Â to send text through QtSpeech. A short term solution
> would be to
> >>>Â Â Â use a terminal with spd-say command-line or if you
> prefer a gui
> >>>Â Â Â kmouth is an option. kmouth is a gui that you can type
> into and
> >>>Â Â Â have it speak. It used to use jovie to do so, but I
> think uses
> >>>Â Â Â QtSpeech (I'll check that in the morning, I know I had
> a branch of
> >>>Â Â Â kmouth that used QtSpeech at some point, not sure if it got
> >>>Â Â Â merged/released). For configuring speech-dispatcher you
> can edit
> >>>Â Â Â the config files by hand with a text editor or use the
> terminal
> >>>Â Â Â based spd-conf command to walk through setting a default
> >>>Â Â Â synthesizer and volumes, etc. At some point in the near
> future it
> >>>Â Â Â would be good to develop a system-settings kde control
> module for
> >>>Â Â Â speech-dispatcher itself to have a gui, but that's not
> more than
> >>>Â Â Â an idea in my head so far... Hope that helps.
> >>>
> >>>Â Â Â Wow, I really need to get some of these ideas
> implemented and out
> >>>Â Â Â of my head. They've been in there far too long. I
> appologize.
> >>>
> >>>Â Â Â thanks,
> >>>Â Â Â Jeremy
> >>>
> >>>Â Â Â On Mon, Sep 16, 2019 at 8:01 PM Gustav Degreef
> <gustav97 at gmail.com <mailto:gustav97 at gmail.com>
> >>>Â Â Â <mailto:gustav97 at gmail.com
> <mailto:gustav97 at gmail.com>>> wrote:
> >>>
> >>>Â Â Â Â Â Hello,
> >>>
> >>>Â Â Â Â Â I am a regular user, visually impaired, but not
> blind.?? I
> >>>Â Â Â Â Â need to be
> >>>Â Â Â Â Â able to select text in various apps and have it
> read out, I
> >>>Â Â Â Â Â don't need a
> >>>Â Â Â Â Â screen reader.?? Qtspeech seems to be the
> replacement for
> >>>Â Â Â Â Â Jovie which did
> >>>Â Â Â Â Â the job nicely before, even with it's limitations
> and not
> >>>Â Â Â Â Â great voices.
> >>>
> >>>Â Â Â Â Â But I can not find documentation for the regular
> user.?? How
> >>>Â Â Â Â Â to configure
> >>>Â Â Â Â Â Qtspeech??? How to change voices, etc.??? Is
> there a GUI like
> >>>Â Â Â Â Â with Jovie???
> >>>Â Â Â Â Â The only app on the desktop which seems to output
> voice by
> >>>Â Â Â Â Â Qtspeech it
> >>>Â Â Â Â Â is Okular.?? But the voice is garbled and very
> difficult to
> >>>Â Â Â Â Â understand.??
> >>>Â Â Â Â Â Where do I go to change the settings to fix
> that??? I have
> >>>Â Â Â Â Â searched over
> >>>Â Â Â Â Â and over again without success.?? Most of what I
> find seems for
> >>>Â Â Â Â Â developers, is old or is only descriptive.?? Any
> pointers to
> >>>Â Â Â Â Â where I can
> >>>Â Â Â Â Â look would be very much appreciated.
> >>>
> >>>
> >>>Â Â Â Â Â I am using opensuse 15.0, kde plasma version 5.12.8,
> >>>Â Â Â Â Â frameworks 5.45.0,
> >>>Â Â Â Â Â Qt 5.9.4, kernel 4.12.14-lp150.12.70-default
> >>>
> >>>Â Â Â Â Â Thanks, Gustav
> >>>
> >>
>
More information about the kde-accessibility
mailing list