opentts VS espeak-ng

I think using something like openTTS might be safer. Though I'm pretty sure no one will ever find out you used their online tts.

The most exciting thing about Home Assistant's "Year of the Voice", for me, is that it is apparently enabling/supporting @synesthesiam's continued phenomenal contributions to the FLOSS off-line voice synthesis space.

The quality, variety & diversity of voices that synesthesiam's "Larynx" TTS project (https://github.com/rhasspy/larynx/) made available, completely transformed the Free/Open Source Text To Speech landscape.

In addition "OpenTTS" (https://github.com/synesthesiam/opentts) provided a common API for interacting with multiple FLOSS TTS projects which showed great promise for actually enabling "standing on the shoulders of" rather than re-inventing the same basic functionality every time.

The new "Piper" TTS project mentioned in the article is the apparent successor to Larynx and, along with the accompanying LibriTTS/LibriVox-based voice models, brings to FLOSS TTS something it's never had before:

* Too many voices! :)

Seriously, the current LibriTTS voice model version has 900+ voices (of varying quality levels), how do you even navigate that many?![0]

And that's not even considering the even higher quality single speaker models based on other audio recording sources.

Offline TTS while immensely valuable for individuals, doesn't seem to be attractive domain for most commercial entities due to lack of lock-in/telemetry opportunities so I was concerned that we might end up missing out on further valuable contributions from synesthesiam's specialised skills & experience due to financial realities & the human need for food. :)

I'm glad we instead get to see what happens next.

[0] See my follow-up comment about this.

Yes, if you scroll down on the github page you can read the extensive README.md file on its setup.

I was wondering if there was a way to use a private OpenTTS server for the Android Text-To-Speech engine.

If your use case allows for a web API, I've had good experience running OpenTTS[0].

It packages several models, including Coqui AI's TTS which I tend to use the most. There's a handy Docker image, too.

[0] https://github.com/synesthesiam/opentts

https://github.com/synesthesiam/opentts is run through Docker, which is pretty simple, and provides a GUI in the browser. There is a good selection of voice engines and voices, and the local Web server has API endpoints. I've been using this on Linux Mint lately.

If you've not already encountered them I'd definitely encourage you to check out these Free/Open Source projects too:

* Larynx: https://github.com/rhasspy/larynx/

* OpenTTS: https://github.com/synesthesiam/opentts

* Likely Mimic3 in the near future: https://mycroft.ai/blog/mimic-3-preview/

Larynx in particular has a focus on "faster than real-time" while OpenTTS is an attempt to package & provide common REST API to all Free/Open Source Text To Speech systems so the FLOSS ecosystem can build on previous work supported by short-lived business interests, rather than start from scratch every time.

AIUI the developer of the first two projects now works for Mycroft AI & is involved in the development of Mimic3 which seems very promising given how much of an impact on quality his solo work has had in just the past couple of years or so.

I haven't personally dealt with Docker much, but am trying to make use of some open source stuff that seems to require Docker to run (https://github.com/synesthesiam/opentts).

After some brief research it seems the issue you're seeing may be a known bug in at least some versions/release of espeak-ng.

Here's some potentially related links if you'd like to dig deeper:

* "questions about mandarin data packet #1044": https://github.com/espeak-ng/espeak-ng/issues/1044

* "ESpeak NJ-1.51’s Mandarin pronunciation is corrupted #12952": https://github.com/nvaccess/nvda/issues/12952

* "The pronunciation of Mandarin Chinese using ESpeak NJ in NVDA is not normal #1028": https://github.com/espeak-ng/espeak-ng/issues/1028

* "When espeak-ng translates Chinese (cmn), IPA tone symbols are not output correctly #305": https://github.com/rhasspy/piper/issues/305

* "Please default ESpeak NG's voice role to 'Chinese (Mandarin, latin as Pinyin)' for Chinese to fix #12952 #13572": https://github.com/nvaccess/nvda/issues/13572

* "Cmn voice not correctly translated #1370": https://github.com/espeak-ng/espeak-ng/issues/1370

I'm skeptical about a senior JavaScript developer claiming to be bored. Nonetheless, let's see. How would you go about modifying [this](ng/blob/master/emscripten/espeakng_glue.idl) IDL file, this C++ glue code, and the relevant Make file to compile eSpeak NG to JavaScript with Emscripten with SSML support enabled?

eSpeak NG supports running on Linux, BSD, Mac, Android, Windows, has been compiled to WASM with Emscripten. See also espeak and meSpeak.js.

I may have a solution, BUT I'm at an airport right now, so... Perhaps tonight I can give you some ideas. There is a program I used to make a few presets for myself. https://github.com/espeak-ng/espeak-ng/blob/master/docs/languages.md

For this one, I used espeak (https://github.com/espeak-ng/espeak-ng) as a text processor. It is almost 17 years old software and is pretty lacking, unfortunately. On the other hand, it's super fast and supports tens of languages. Long story short, punctuation introduces phrase break with a pause of fixed length, and capitalization is ignored.

I didnt not release trainy parts to build voices. I am considering, but there is so many packages already (coqui, espnet, piper, nemo, fairseq to name a few) that i focused on usability for now. Support for new languages is a different question. Everyone wants to train fancy neural nets. But support for new language is about writing rules and having language expertise. I did it for English (https://github.com/balacoon/en_us_normalization/tree/c1019cf878aa6baf25d6fff719cf418cca5a3107/production/classify). Doing it for all the other languages would probably take me a lifetime. Other speech synthesis solutions use 17-years old espeak for this purpose (https://github.com/espeak-ng/espeak-ng/blob/master/docs/languages.md). I introduced the fallback to it in Balacoon too. But generally, it is outdated technology and I believe we should do better.

espeak-ng works by first converting text to IPA and then pronouncing that. But im not sure im aware of a way to input arbitrary IPA, and also the quality is probably too low for you.

There are espeak-ng https://github.com/espeak-ng/espeak-ng and pocketsphinx https://github.com/cmusphinx/pocketsphinx which can be used locally without making external requests.

There are automatic tools to convert a written form of a language to IPA, I'm personally aware of espeak-ng, which supports* a lot of languages.

I've had good luck with https://github.com/espeak-ng/espeak-ng (for very specific purposes, and I was willing to wrangle IPA)