[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-accessibility
Subject: Re: Is there a project that is jovie successor? (fwd)
From: Nickolay Shmyrev <nshmyrev () gmail ! com>
Date: 2021-10-29 17:46:57
Message-ID: 40912768-9DDC-4486-A609-5BD6300D93A7 () gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello guys.
You need to checkout this modern technology one day:
https://github.com/rhasspy/larynx <https://github.com/rhasspy/larynx>
> 29 окт. 2021 г., в 20:12, Gustav Degreef <gustav97@gmail.com> \
> написал(а):
> No problem about not replying sooner. That West Indies voice is exactly what I \
> hear also. It is output at the same time the regular espeak English voice, so the \
> output is incomprehensible . I had said Scottish sounding, but you are more \
> correct.
> No I was not able to get the "hello_speak example" to work. I can't get the program \
> to build. I have been trying to figure out why my test opensuse 15.3 system does \
> not have the problem of the duplicate voices and the 15.3 system which I need for \
> work does have the problem. It seems that when I was able to install Jovie on the \
> 15.3 test system it was because it came from an unsupported repo which installed \
> some Qt5 Frameworks packages, but I can't figure out which ones. And now that I \
> look again that unsupported repo no longer has Jovie available. Not sure where to \
> go from here.
> Jeremy, thank you for all your patient efforts and for undertaking to improve the \
> situation. I will keep an eye out for the improved Kmouth. Gustav
> On 10/29/21 5:48 PM, Jeremy Whiting wrote:
> > Gustav,
> >
> > Sorry, I didn't respond yesterday. The espeak.log you sent looks like espeak is \
> > getting text fine from kmouth and okular. I'm betting that since kmouth and \
> > okular do not tell QtSpeech which voice to use it's using some default that isn't \
> > ideal. Were you ever able to get hello_speak example to work? With it you can \
> > select each voice that QtSpeech knows about and probably see what default it's \
> > using for a given language. Here when I open it on my opensuse 15.2 vm it starts \
> > with English, but has some west indies voice as the default which pronounces \
> > everything strangely. If I change it to another english voice it all sounds the \
> > same as spd-say.
> > So it won't be in the next release since feature freeze will be soon or has \
> > already happened, but I'll get voice selection in at least okular's settings \
> > window where you can already select between flite and speechd. And do likewise \
> > for KMouth with the other improvements I'll do to KMouth. I think once you're \
> > able to select a voice (and language) in those just like in hello_speak it should \
> > be pretty straight forward to make it sound the way you want.
> > BR,
> > Jeremy
[Attachment #5 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html \
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space;" class="">Hello guys.<div class=""><br \
class=""></div><div class="">You need to checkout this modern technology one \
day:</div><div class=""><br class=""></div><div class=""><a \
href="https://github.com/rhasspy/larynx" \
class="">https://github.com/rhasspy/larynx</a></div><div class=""><br \
class=""><div><blockquote type="cite" class=""><div class="">29 окт. 2021 г., в \
20:12, Gustav Degreef <<a href="mailto:gustav97@gmail.com" \
class="">gustav97@gmail.com</a>> написал(а):</div><br \
class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; \
display: inline !important;" class="">No problem about not replying \
sooner. That West Indies voice is exactly what I hear also. \
It is output at the same time the regular espeak English voice, so the output is \
incomprehensible . I had said Scottish sounding, but you are more \
correct.</span><br style="font-family: Helvetica; font-size: 12px; font-style: \
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; \
text-align: start; text-indent: 0px; text-transform: none; white-space: normal; \
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: \
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; \
font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; \
text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; \
display: inline !important;" class="">No I was not able to get the "hello_speak \
example" to work. I can't get the program to build. I have been trying to \
figure out why my test opensuse 15.3 system does not have the problem of the \
duplicate voices and the 15.3 system which I need for work does have the \
problem. It seems that when I was able to install Jovie on the 15.3 test system \
it was because it came from an unsupported repo which installed some Qt5 Frameworks \
packages, but I can't figure out which ones. And now that I look again that \
unsupported repo no longer has Jovie available. Not sure where to go from \
here.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: \
start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: \
0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" \
class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: \
start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: \
0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" \
class="">Jeremy, thank you for all your patient efforts and for undertaking to \
improve the situation. I will keep an eye out for the improved Kmouth. \
Gustav</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: \
start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: \
0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" \
class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; \
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: \
start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: \
0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" \
class="">On 10/29/21 5:48 PM, Jeremy Whiting wrote:</span><br style="font-family: \
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; \
font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; \
text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" style="font-family: \
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; \
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; \
text-indent: 0px; text-transform: none; white-space: normal; widows: auto; \
word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" \
class="">Gustav,<br class=""><br class="">Sorry, I didn't respond yesterday. The \
espeak.log you sent looks like espeak is getting text fine from kmouth and okular. \
I'm betting that since kmouth and okular do not tell QtSpeech which voice to use it's \
using some default that isn't ideal. Were you ever able to get hello_speak example to \
work? With it you can select each voice that QtSpeech knows about and probably see \
what default it's using for a given language. Here when I open it on my opensuse 15.2 \
vm it starts with English, but has some west indies voice as the default which \
pronounces everything strangely. If I change it to another english voice it all \
sounds the same as spd-say.<br class=""><br class="">So it won't be in the next \
release since feature freeze will be soon or has already happened, but I'll get voice \
selection in at least okular's settings window where you can already select between \
flite and speechd. And do likewise for KMouth with the other improvements I'll do to \
KMouth. I think once you're able to select a voice (and language) in those just like \
in hello_speak it should be pretty straight forward to make it sound the way you \
want.<br class=""><br class="">BR,<br class="">Jeremy<br \
class=""></blockquote></div></blockquote><br class=""></div></div></body></html>
["signature.asc" (signature.asc)]
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iEYEARECAAYFAmF8M5MACgkQLCDh4YwOt9n/JgCeJTL6DpWYPkQfLOFx+qYInAqD
WroAn0ApVz8YPuHyiHURXQ0E52bQsAWL
=HsOl
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic