User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
4mo
The State of Modern AI Text To Speech Systems for Screen Reader Users: The past year has seen an explosion in new text to speech engines based on neural networks, large language models, and machine learning. But has any of this advancement offered anything to those using screen readers? stuff.interfree.ca/2026/01/05/ai-tts-for-screenreaders.html
12
41
15
0
User avatar
Amir @amir@dragonscave.space
4mo
@fastfinge What an interesting read! Needless to say, I read it with Eloquence - LOL!
1
0
1
0
User avatar
Sean Randall @cachondo@defcon.social
4mo
@amir @fastfinge It's crazy that everyone is layering it in wrappers nowadays.
Do you know if codefactory are doing the same with their new android build?
2
0
0
0
User avatar
Andre Louis @FreakyFwoof@universeodon.com
4mo
@cachondo @amir @fastfinge I sincerely hope someone will do the same for Orpheus. I'd even pay for it.
5
0
0
0
User avatar
Luis Carlos @luiscarlosgonzalez@mastodon.social
4mo
@FreakyFwoof @cachondo @amir @fastfinge And also for Kokoro and other speech synths.
1
0
0
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
4mo
@luiscarlosgonzalez @cachondo @FreakyFwoof @amir I didn't try Kokoro, because it cannot achieve a real time factor of 1 on CPU. By that I mean, to be fit for consideration with a screen reader, a text to speech voice must be able to generate one second of speech in one second or faster. In general, Kokoro takes two seconds to generate one second of speech. So it's not suitable.
0
0
0
0