TTS VS tortoise-tts

Fast or good, choose one

Mozilla's TTS is a python package installable with pip and uses cpu or gpu resources to render a choice of voices, they mostly sound natural and this is the good. https://github.com/mozilla/TTS

Mycroft's mimic3 is the default voice renderer for the Mycroft project that runs on pi hardware and sounds ok-ish, that is the fast. https://github.com/MycroftAI/mimic3

There are many others but these are the two I use according to if it needs to run on limited hardware or if the cycles fall freely from the sky.

Coqui-ai was a commercial continuation of Mozilla TTS and STT (https://github.com/mozilla/TTS).

At the time (2018-ish), it was really impressive for on-device voice synthesis (with a quality approaching the Google and Azure cloud-based voice synthesis options) and open source, so a lot of people in the FOSS community were hoping it could be used for a privacy-respecting home assistant, Linux speech synthesis that doesn't suck, etc.

After Mozilla abandoned the project, Coqui continued development and had some really impressive one-shot voice cloning, but pivoted to marketing speech synthesis for game developers. They were probably having trouble monetizing it, and it doesn't surprise me that they shut down.

An equivalent project that's still in active development and doing really well is Piper TTS (https://github.com/rhasspy/piper).

An RSS reader that integrates TTS (or TTS)

My solution would be to use a speech synthesis library, maybe eSpeak or Festival, just for ease of use; I think they each provide a library that you could use from C or C++ easily. This one from Mozilla is a more modern system with better-quality output, but it looks like it's set up to run through Python, and I haven't looked at it closely enough to see how much work it would be to get it working for you.

There is a lot of TTS and SST development going on (https://github.com/mozilla/TTS; https://github.com/mozilla/DeepSpeech; https://github.com/common-voice/common-voice). That is the only way they work: Contributions from the wild.

unfortunately not yet. I need to expand the library of languages and voices. looking around, it seems only Coqui had some traction re Brazilian Portuguese: https://github.com/mozilla/TTS/issues/160. If you foresee wide adoption of the tech for this locale, hit me up with DM

I haven't used it, but there's also mozilla/TTS.

Mozilla TTS

Instead, just use Firefox's open-source TTS model: https://github.com/mozilla/TTS

The quality also depends on the type of model. I'm not really sure what ESpeak-ng actually uses? The classical TTS approaches often use some statistical model (e.g. HMM) + some vocoder. You can get to intelligible speech pretty easily but the quality is bad (w.r.t. how natural it sounds).

There are better open source TTS models. E.g. check https://github.com/neonbjb/tortoise-tts or https://github.com/NVIDIA/tacotron2. Or here for more: https://www.reddit.com/r/MachineLearning/comments/12kjof5/d_...

I use Tortoise TTS. It's slow, a little clunky, and sometimes the output gets downright weird. But it's the best quality-oriented TTS I've found that I can run locally.

https://github.com/neonbjb/tortoise-tts

neonbjb/tortoise-tts

EDIT: It appears to be the exact same issue as this

It was primarily being used to train TTS models (see https://github.com/neonbjb/tortoise-tts), which largely fit into a single GPUs memory. So, for data parallelism, x8 PCIe isn't that much of a concern.

Previously TortoiseTTS was associated with PlayHT in some way, although the exact connection is a bit vague [0].

From the descriptions here it sounds a lot like AudioLM / SPEAR TTS / some of Meta's recent multilingual TTS approaches, although those models are not open source, sounds like PlayHT's approach is in a similar spirit. The discussion of "mel tokens" is closer to what I would call the classic TTS pipeline in many ways... PlayHT has generally been kind of closed about what they used, would be interesting to know more.

I assume the key factor here is high quality, emotive audio with good data cleaning processes. Probably not even a lot of data, at least in the scale of "a lot" in speech, e.g. ASR (millions of hours) or TTS (hundreds to thousands). As opposed to some radically new architectural piece never before seen in the literature, there are lots of really nice tools for emotive and expressive TTS buried in recent years of publications.

Tacotron 2 is perfectly capable of this type of stuff as well, as shown by Dessa [1] a few years ago (this writeup is a nice intro to TTS concepts). With the limit largely being, at some point you haven't heard certain phonetic sounds before in a voice, and need to do something to get plausible outcomes for new voices.

[0] Discussion here https://github.com/neonbjb/tortoise-tts/issues/182#issuecomm...

[1] https://medium.com/dessa-news/realtalk-how-it-works-94c1afda...

Tortoise GitHub repo - Source code, documentation, and usage guide