#espeak — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #espeak, aggregated by home.social.
-
Dieses Python Script trennt #Daisy Hörbücher auf mehrere Datenträger auf. Es entstand vor dem Hintergrund, dass wir einen älteren Herrn betreuen, dessen Daisy Abspielgerät lediglich CDs abspielen kann. zusätzlich synthetisiert das Script mit der #Espeak den Index des Datenträgers als MP3 an den Anfang der neuen Disk. Es kann parametrisiert werden, abhängig davon, wie groß Eure Rohlinge sind. #Hörbuch #Blinde #Hörmedien #Python #Audio https://github.com/DO9RE/daisy_splitter
-
@[email protected] Oh Hell Yeah! I'll be all over this one! Now with #ESpeak , #Eloquence and #TGSpeechBox at my ready! -
> Removing PulseAudio..continuing the shift to PipeWire
My #GoPiGo3 robot just shuddered in fear of becoming deaf and mute.
-
> Removing PulseAudio..continuing the shift to PipeWire
My #GoPiGo3 robot just shuddered in fear of becoming deaf and mute.
-
> Removing PulseAudio..continuing the shift to PipeWire
My #GoPiGo3 robot just shuddered in fear of becoming deaf and mute.
-
> Removing PulseAudio..continuing the shift to PipeWire
My #GoPiGo3 robot just shuddered in fear of becoming deaf and mute.
-
> Removing PulseAudio..continuing the shift to PipeWire
My #GoPiGo3 robot just shuddered in fear of becoming deaf and mute.
-
If the title of this one doesn't interest you, the contents sure won't! Correcting Years With #NVDA and #Espeak: stuff.interfree.ca/2025/08/28/correct-years-with-nvda-and-espeak.html #regexp #blind #screenreader #a11y #accessibility -
If the title of this one doesn't interest you, the contents sure won't! Correcting Years With #NVDA and #Espeak: stuff.interfree.ca/2025/08/28/correct-years-with-nvda-and-espeak.html #regexp #blind #screenreader #a11y #accessibility -
If the title of this one doesn't interest you, the contents sure won't! Correcting Years With #NVDA and #Espeak: stuff.interfree.ca/2025/08/28/correct-years-with-nvda-and-espeak.html #regexp #blind #screenreader #a11y #accessibility -
If the title of this one doesn't interest you, the contents sure won't! Correcting Years With #NVDA and #Espeak: stuff.interfree.ca/2025/08/28/correct-years-with-nvda-and-espeak.html #regexp #blind #screenreader #a11y #accessibility -
If the title of this one doesn't interest you, the contents sure won't! Correcting Years With #NVDA and #Espeak: stuff.interfree.ca/2025/08/28/correct-years-with-nvda-and-espeak.html #regexp #blind #screenreader #a11y #accessibility -
@argv_minus_one Oh nothing against #espeak or #BlaBlaMaker or even #MicrosoftSam, those are super fun. But they are also so terrible, that you hear they have been made procedurally. What I was referring to is the voiceovers on many YouTube videos that you initially don't even recognize as being generated, only when they stumble on a certain word they pronounce extremely weirdly.
-
@argv_minus_one Oh nothing against #espeak or #BlaBlaMaker or even #MicrosoftSam, those are super fun. But they are also so terrible, that you hear they have been made procedurally. What I was referring to is the voiceovers on many YouTube videos that you initially don't even recognize as being generated, only when they stumble on a certain word they pronounce extremely weirdly.
-
@argv_minus_one Oh nothing against #espeak or #BlaBlaMaker or even #MicrosoftSam, those are super fun. But they are also so terrible, that you hear they have been made procedurally. What I was referring to is the voiceovers on many YouTube videos that you initially don't even recognize as being generated, only when they stumble on a certain word they pronounce extremely weirdly.
-
@argv_minus_one Oh nothing against #espeak or #BlaBlaMaker or even #MicrosoftSam, those are super fun. But they are also so terrible, that you hear they have been made procedurally. What I was referring to is the voiceovers on many YouTube videos that you initially don't even recognize as being generated, only when they stumble on a certain word they pronounce extremely weirdly.
-
@argv_minus_one Oh nothing against #espeak or #BlaBlaMaker or even #MicrosoftSam, those are super fun. But they are also so terrible, that you hear they have been made procedurally. What I was referring to is the voiceovers on many YouTube videos that you initially don't even recognize as being generated, only when they stumble on a certain word they pronounce extremely weirdly.
-
Working with TTS via espeak in Ubuntu has reminded me once again how, like, bad open source can be.
Believe it or not, I don't mean that as a negative. More just an observation on the ecosystem. Defaults build up, first-movers have huge advantage, and we more often than not end up in a place where the easiest solution is the worst solution.
The default espeak voice (at least what you get if you install
espeakorespeak-ng-espeakfrom the package repo) is ear-bleedingly bad. It reminds me of state-of-the-art ca. late-90s / early-00s, except I don't think Apple ever put out anything that sounded quite so ass. No shame on the people who built the model originally: text-to-speech is a hard problem and if not for their work, there'd be nothing. But it's 2025; there are much better speech-model options now (though I haven't found anything nearly as crisp or clean as what Google is doing for special sauce yet), but of course we can't just switch to those out of the box because muh defaults.So many processes in the Linux ecosystem are like this. "Here's the command to get started. And here's the six commands to make it not suck."
Apple and Microsoft, in competition with each other, are incentivized to either not ship experiences that are inferior to the alternative or to deprecate them when they fall behind the alternative. This sucks when your thing is the thing being deprecated, but it does mean that when I do the exact same experiment on Windows (install espeak and fire some text into it without selecting a voice), the default doesn't try to claw your eyeballs out through your ear canals. There's something to that, you know?
(Credit where it's due: projects like Ubuntu improved the status quo by being an alternate platform so they weren't beholden to other distros' defaults. They went and built their own distro with blackjack and hookers Wayland and systemd and it worked.)
All of that having been said: the thing I'm trying to do right now I wouldn't try on Windows precisely because when I hit a wall I won't be able to find an alternative, even if it takes me six tries to find it. There's power in that flexibility, even when it makes some of the labor mandatory.
-
Working with TTS via espeak in Ubuntu has reminded me once again how, like, bad open source can be.
Believe it or not, I don't mean that as a negative. More just an observation on the ecosystem. Defaults build up, first-movers have huge advantage, and we more often than not end up in a place where the easiest solution is the worst solution.
The default espeak voice (at least what you get if you install
espeakorespeak-ng-espeakfrom the package repo) is ear-bleedingly bad. It reminds me of state-of-the-art ca. late-90s / early-00s, except I don't think Apple ever put out anything that sounded quite so ass. No shame on the people who built the model originally: text-to-speech is a hard problem and if not for their work, there'd be nothing. But it's 2025; there are much better speech-model options now (though I haven't found anything nearly as crisp or clean as what Google is doing for special sauce yet), but of course we can't just switch to those out of the box because muh defaults.So many processes in the Linux ecosystem are like this. "Here's the command to get started. And here's the six commands to make it not suck."
Apple and Microsoft, in competition with each other, are incentivized to either not ship experiences that are inferior to the alternative or to deprecate them when they fall behind the alternative. This sucks when your thing is the thing being deprecated, but it does mean that when I do the exact same experiment on Windows (install espeak and fire some text into it without selecting a voice), the default doesn't try to claw your eyeballs out through your ear canals. There's something to that, you know?
(Credit where it's due: projects like Ubuntu improved the status quo by being an alternate platform so they weren't beholden to other distros' defaults. They went and built their own distro with blackjack and hookers Wayland and systemd and it worked.)
All of that having been said: the thing I'm trying to do right now I wouldn't try on Windows precisely because when I hit a wall I won't be able to find an alternative, even if it takes me six tries to find it. There's power in that flexibility, even when it makes some of the labor mandatory.
-
Working with TTS via espeak in Ubuntu has reminded me once again how, like, bad open source can be.
Believe it or not, I don't mean that as a negative. More just an observation on the ecosystem. Defaults build up, first-movers have huge advantage, and we more often than not end up in a place where the easiest solution is the worst solution.
The default espeak voice (at least what you get if you install
espeakorespeak-ng-espeakfrom the package repo) is ear-bleedingly bad. It reminds me of state-of-the-art ca. late-90s / early-00s, except I don't think Apple ever put out anything that sounded quite so ass. No shame on the people who built the model originally: text-to-speech is a hard problem and if not for their work, there'd be nothing. But it's 2025; there are much better speech-model options now (though I haven't found anything nearly as crisp or clean as what Google is doing for special sauce yet), but of course we can't just switch to those out of the box because muh defaults.So many processes in the Linux ecosystem are like this. "Here's the command to get started. And here's the six commands to make it not suck."
Apple and Microsoft, in competition with each other, are incentivized to either not ship experiences that are inferior to the alternative or to deprecate them when they fall behind the alternative. This sucks when your thing is the thing being deprecated, but it does mean that when I do the exact same experiment on Windows (install espeak and fire some text into it without selecting a voice), the default doesn't try to claw your eyeballs out through your ear canals. There's something to that, you know?
(Credit where it's due: projects like Ubuntu improved the status quo by being an alternate platform so they weren't beholden to other distros' defaults. They went and built their own distro with blackjack and hookers Wayland and systemd and it worked.)
All of that having been said: the thing I'm trying to do right now I wouldn't try on Windows precisely because when I hit a wall I won't be able to find an alternative, even if it takes me six tries to find it. There's power in that flexibility, even when it makes some of the labor mandatory.
-
Working with TTS via espeak in Ubuntu has reminded me once again how, like, bad open source can be.
Believe it or not, I don't mean that as a negative. More just an observation on the ecosystem. Defaults build up, first-movers have huge advantage, and we more often than not end up in a place where the easiest solution is the worst solution.
The default espeak voice (at least what you get if you install
espeakorespeak-ng-espeakfrom the package repo) is ear-bleedingly bad. It reminds me of state-of-the-art ca. late-90s / early-00s, except I don't think Apple ever put out anything that sounded quite so ass. No shame on the people who built the model originally: text-to-speech is a hard problem and if not for their work, there'd be nothing. But it's 2025; there are much better speech-model options now (though I haven't found anything nearly as crisp or clean as what Google is doing for special sauce yet), but of course we can't just switch to those out of the box because muh defaults.So many processes in the Linux ecosystem are like this. "Here's the command to get started. And here's the six commands to make it not suck."
Apple and Microsoft, in competition with each other, are incentivized to either not ship experiences that are inferior to the alternative or to deprecate them when they fall behind the alternative. This sucks when your thing is the thing being deprecated, but it does mean that when I do the exact same experiment on Windows (install espeak and fire some text into it without selecting a voice), the default doesn't try to claw your eyeballs out through your ear canals. There's something to that, you know?
(Credit where it's due: projects like Ubuntu improved the status quo by being an alternate platform so they weren't beholden to other distros' defaults. They went and built their own distro with blackjack and hookers Wayland and systemd and it worked.)
All of that having been said: the thing I'm trying to do right now I wouldn't try on Windows precisely because when I hit a wall I won't be able to find an alternative, even if it takes me six tries to find it. There's power in that flexibility, even when it makes some of the labor mandatory.
-
Working with TTS via espeak in Ubuntu has reminded me once again how, like, bad open source can be.
Believe it or not, I don't mean that as a negative. More just an observation on the ecosystem. Defaults build up, first-movers have huge advantage, and we more often than not end up in a place where the easiest solution is the worst solution.
The default espeak voice (at least what you get if you install
espeakorespeak-ng-espeakfrom the package repo) is ear-bleedingly bad. It reminds me of state-of-the-art ca. late-90s / early-00s, except I don't think Apple ever put out anything that sounded quite so ass. No shame on the people who built the model originally: text-to-speech is a hard problem and if not for their work, there'd be nothing. But it's 2025; there are much better speech-model options now (though I haven't found anything nearly as crisp or clean as what Google is doing for special sauce yet), but of course we can't just switch to those out of the box because muh defaults.So many processes in the Linux ecosystem are like this. "Here's the command to get started. And here's the six commands to make it not suck."
Apple and Microsoft, in competition with each other, are incentivized to either not ship experiences that are inferior to the alternative or to deprecate them when they fall behind the alternative. This sucks when your thing is the thing being deprecated, but it does mean that when I do the exact same experiment on Windows (install espeak and fire some text into it without selecting a voice), the default doesn't try to claw your eyeballs out through your ear canals. There's something to that, you know?
(Credit where it's due: projects like Ubuntu improved the status quo by being an alternate platform so they weren't beholden to other distros' defaults. They went and built their own distro with blackjack and hookers Wayland and systemd and it worked.)
All of that having been said: the thing I'm trying to do right now I wouldn't try on Windows precisely because when I hit a wall I won't be able to find an alternative, even if it takes me six tries to find it. There's power in that flexibility, even when it makes some of the labor mandatory.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Working on #adacompliance by trying to integrate a #texttospeech engine into #AOSP
#espeak has been deemed too low quality, and #sherpaTTS too slow. #RHVoice silently fails on our hardware, and I'm running out of options. Does @GrapheneOS have a TTS engine that would be commercially friendly enough for us to push it via OTA update? Or would anyone recommend one?
We work with a sensitive population and lack of a screen reader can make things even more difficult for some.
-
Un projet pour jouer un son démarrage/arrêt d'un @raspberrypi RASPBERRY PI , afin de permettre aux personnes malvoyantes ou aveugles de connaître l'état de fonctionnement de leur appareil Annonce également l'état du Wi-Fi grâce au moteur de synthèse vocale #espeak. https://github.com/FrancoisLB/audio_play_startup_pi
-
Un projet pour jouer un son démarrage/arrêt d'un @raspberrypi RASPBERRY PI , afin de permettre aux personnes malvoyantes ou aveugles de connaître l'état de fonctionnement de leur appareil Annonce également l'état du Wi-Fi grâce au moteur de synthèse vocale #espeak. https://github.com/FrancoisLB/audio_play_startup_pi
-
Un projet pour jouer un son démarrage/arrêt d'un @raspberrypi RASPBERRY PI , afin de permettre aux personnes malvoyantes ou aveugles de connaître l'état de fonctionnement de leur appareil Annonce également l'état du Wi-Fi grâce au moteur de synthèse vocale #espeak. https://github.com/FrancoisLB/audio_play_startup_pi
-
Un projet pour jouer un son démarrage/arrêt d'un @raspberrypi RASPBERRY PI , afin de permettre aux personnes malvoyantes ou aveugles de connaître l'état de fonctionnement de leur appareil Annonce également l'état du Wi-Fi grâce au moteur de synthèse vocale #espeak. https://github.com/FrancoisLB/audio_play_startup_pi
-
Un projet pour jouer un son démarrage/arrêt d'un @raspberrypi RASPBERRY PI , afin de permettre aux personnes malvoyantes ou aveugles de connaître l'état de fonctionnement de leur appareil Annonce également l'état du Wi-Fi grâce au moteur de synthèse vocale #espeak. https://github.com/FrancoisLB/audio_play_startup_pi
-
You don't like the artificial sound of #espeak? May you like this better?
https://f-droid.org/de/packages/org.woheller69.ttsengine/index.html
https://github.com/woheller69/ttsEngine
#sherpatts #tts #opensource #foss #speechsynthesis #ai #android
-
You don't like the artificial sound of #espeak? May you like this better?
https://f-droid.org/de/packages/org.woheller69.ttsengine/index.html
https://github.com/woheller69/ttsEngine
#sherpatts #tts #opensource #foss #speechsynthesis #ai #android
-
You don't like the artificial sound of #espeak? May you like this better?
https://f-droid.org/de/packages/org.woheller69.ttsengine/index.html
https://github.com/woheller69/ttsEngine
#sherpatts #tts #opensource #foss #speechsynthesis #ai #android
-
You don't like the artificial sound of #espeak? May you like this better?
https://f-droid.org/de/packages/org.woheller69.ttsengine/index.html
https://github.com/woheller69/ttsEngine
#sherpatts #tts #opensource #foss #speechsynthesis #ai #android
-
You don't like the artificial sound of #espeak? May you like this better?
https://f-droid.org/de/packages/org.woheller69.ttsengine/index.html
https://github.com/woheller69/ttsEngine
#sherpatts #tts #opensource #foss #speechsynthesis #ai #android
-
Verspätetete Züge im Hbf Worms als Audio-Ausgabe . Automatisch erzeugt von einem sehr kurzen #Bashskript. #curl #espeak #ffmpeg
https://gist.github.com/dewomser/fcf6e24737e6e6a0df1a5982b7c19de7 -
Verspätetete Züge im Hbf Worms als Audio-Ausgabe . Automatisch erzeugt von einem sehr kurzen #Bashskript. #curl #espeak #ffmpeg
https://gist.github.com/dewomser/fcf6e24737e6e6a0df1a5982b7c19de7 -
eSpeak NG Text-to-Speech.
The #eSpeak NG is a compact open source software text -to- #speech #synthesizer for #Linux, #Windows, #Android and other operating systems. It supports more than 100 languages and accents. It is based on the eSpeak engine created by Jonathan Duddington.
https://github.com/espeak-ng/espeak-ng
https://f-droid.org/packages/com.reecedunn.espeak/ -
eSpeak NG Text-to-Speech.
The #eSpeak NG is a compact open source software text -to- #speech #synthesizer for #Linux, #Windows, #Android and other operating systems. It supports more than 100 languages and accents. It is based on the eSpeak engine created by Jonathan Duddington.
https://github.com/espeak-ng/espeak-ng
https://f-droid.org/packages/com.reecedunn.espeak/ -
eSpeak NG Text-to-Speech.
The #eSpeak NG is a compact open source software text -to- #speech #synthesizer for #Linux, #Windows, #Android and other operating systems. It supports more than 100 languages and accents. It is based on the eSpeak engine created by Jonathan Duddington.
https://github.com/espeak-ng/espeak-ng
https://f-droid.org/packages/com.reecedunn.espeak/ -
eSpeak NG Text-to-Speech.
The #eSpeak NG is a compact open source software text -to- #speech #synthesizer for #Linux, #Windows, #Android and other operating systems. It supports more than 100 languages and accents. It is based on the eSpeak engine created by Jonathan Duddington.
https://github.com/espeak-ng/espeak-ng
https://f-droid.org/packages/com.reecedunn.espeak/ -
eSpeak NG Text-to-Speech.
The #eSpeak NG is a compact open source software text -to- #speech #synthesizer for #Linux, #Windows, #Android and other operating systems. It supports more than 100 languages and accents. It is based on the eSpeak engine created by Jonathan Duddington.
https://github.com/espeak-ng/espeak-ng
https://f-droid.org/packages/com.reecedunn.espeak/ -
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
-
Important note for #blind users!
#CRDroid doesn't contain #gapps, there's no Talk Back available.
You have to download it manually and put it to your phone via recovery.
Also you'll need a TTS engine and this is kinda problem because I know no TTS which work out of the box without prior network access.
#Espeak needs internet to download language data on first launch;
#RHVoice needs internet for every new voice;
#Vocalizer is paid and needs the same;The only option at least for Russian people is to download #FonTTS (modern implementation of #NewFon) and use it.
If you know totally offline TTS synthesizers for other languages, please share.Also even if you put Talk Back and TTS via recovery they won't start via volume buttons.
You have to enable usb debugging via recovery and then, on welcome screen, via adb, enable Talk Back and set default TTS for speech output.After that you're good to go as an usual user.
