WIP: Add speech-tools
and festival
ebuilds to be used by TDEAccessibility
.
#154
Draft
Chris
wants to merge 1 commits from feat/tdeaccessibility
into master
Loading…
Reference in new issue
There is no content yet.
Delete Branch 'feat/tdeaccessibility'
Deleting a branch is permanent. It CANNOT be undone. Continue?
This needs the CMake conversion to be done at TDE level by @cethyel first, which is WIP right now. 😸
Because the Gentoo developers couldn't wait until the users worked on some
festival
ebuild, they removed the whole festival engine from Portage. This engine does mostly all the magic ofkttsd
, compareable to K3b and the cdrecord. Other engines could be used in theory too.The last included version was
2.1.
anyway, which was at least working. Meanwhile2.5
is out and there is some already draft kind of ebuild for that version existing, which we will need to import to our overlay and maybe add some further changes to it. It should support a wide field of voices for different languages out of the box.But for other languages (like German) the fun begins. There has to be some USE which add patches, or some extra ebuild, to build a specific patched festival engine, which makes use of MBROLA voices.
Luckily that was updated to work with festival
2.5
too. Also newMBROLA
releases are out there. So maybe we can add that too. (Gentoo is at3.0
, but the GH of the projects shows3.3
)At least we should note here that with GCC10,
fno-common
will make problems for Festival. So we should most likely add-fcommon
to it.At least the listing of festival ebuilds should give us a good coverage of most spread languages.
30.04.2020:
It seems at least the old voices like
festival-it
, which worked with festival2.1
and2.4
are broken now for2.5
. Also,festival-ru
works only one time, after that, it starts to output crepy noises. I will try to fixfestival-ru
, but if not, I just will add it in the hope here is someone doing more investigation about that.It seems also that the Debian people found at least some fix for the language file of
festival-it
, to work with2.5
. I will look for the other languages what patches Debian is using. So we don't need to support some2.1
or2.4
version of festival at the same time.I also found possible alternatives for
kttsd
to use, because you can specify some command for TTS. One of that isespeak-ng
(Very lightweight but quality should be not as good, but is able to use MBROLA voices - Not in Portage right now). Another one would besvox
(From G00gle/Andr0id - Should have the best quality of all - Currently not in Portage and not maintained anymore, but still used). The question would be, if it makes sense to add them to the overlay. Maybe at TDE level there selection could be added tokttsd
too. To have more modern alternatives?About
en
it is to say that festival supports that out of the box, but the quality seems to be not as good. Better quality you can get, if you use the MBROLA voices. Festival and other TTS programs are using MBROLA for the voices. Again better voices, you can get withfestival-hts
. There seems to be one voice (in the festival-hts package), which seems to be the best of all. The question is, if it is working with festival2.5
and if not, what patches (if any existing) would be needed. It is also to note that most voices not got any love since 2010 around. State of the art TTS in Linux still.The download of all the included festival voices is very large and most will not need the indic voices. So maybe it would make sense to add some
cmu
and/orl10n_*
USE to the festival ebuild.Currently lacking:
References:
Signed-off-by: Chris xchrisx@uber.space
e086adfa6d
to04485e323b
3 years agoI did rebase and solve conflicts of this old PR and seem to be the only difference that is here is ebuilds for external applications – festival and speech-tools.
WIP: Live ebuilds: Add `TDEAccessibility` ebuilds and dependencies.to WIP: Add `speech-tools` and `festival` ebuilds to be used by `TDEAccessibility`. 2 years ago