Reviews for Read Aloud: A Text to Speech Voice Reader
Read Aloud: A Text to Speech Voice Reader by LSD Software
1,073 reviews
- Rated 5 out of 5by Андрей, 7 months ago
- Rated 5 out of 5by Firefox user 14400720, 8 months ago
- Rated 4 out of 5by Carlisle Mike Wick, 8 months ago
- Rated 1 out of 5by Jan, 8 months agoBABABABABABABABABABABA
it just simply ridiculous guys. Is this a joke or somehting? It's probably my fault, but this sounds 10 times worse as stephen hawking. Or maybe like one of Edison's first phonograph recordings Mawawary hawawad alala liwiwiwttle lawawawam. Come on.. - Rated 1 out of 5by honza1616, 8 months agoIn my language (Czech), it's like listening to a robot. Try the Edge browser, it has the reader already installed and it's perfect.
- Rated 4 out of 5by Firefox user 12210722, 8 months ago
- Rated 1 out of 5by Fulmer, 8 months agoEvery time I start it, it wants me to grant additional permissions. Additional? I gave it the permissions it needed when I ran it the first time so why do I have to give it additional permissions every day I run it? I want it to be given all the permissions it needs to run and make that permanent. Instead, you have to go through a tedious rigmerole of opening a webpage, scrolling down and clicking on a speak button, then tick a box saying you are not a robot EVERY TIME you use it! No! I won't do that.
- Rated 4 out of 5by Firefox user 13604038, 8 months ago
- Rated 5 out of 5by WalterHo, 8 months ago
- Rated 4 out of 5by whalemonster, 8 months ago
- Rated 3 out of 5by big boom, 8 months agoI've noticed an issue with the way the Google Translate Bengali voice feature pronounces numerical values in English. Specifically, when the Bengali voice reads out English phrases containing numbers, the pronunciation of those numerical values is inaccurate.
For example, when the Bengali voice reads '24 hours', it pronounces it as 'chabbish (২৪) hours', where 'chabbish' is the direct Bengali pronunciation of the number '24', rather than the proper English pronunciation.
This problem seems to occur consistently across all numerical values when using the Google Translate Bengali voice. I was hoping you could provide guidance on how this numerical pronunciation accuracy could be improved within the Bengali voice feature. Having the Bengali voice deliver the correct English pronunciations for numbers would greatly help me. - Rated 5 out of 5by jjpatricio, 8 months ago¡Muy buen trabajo! Desde Ubuntu 24.04, funcionando perfectamente en Firefox. Algunas páginas no se pueden leer, por lo que copio la información en la página https://www.editpad.org/ y activo 'Formatting'.
Para Chrome también existe este complemento y, desde Chrome, Herramientas> Escribir por voz... el 'pack' es completo.
Voz: GoogleTranslate Spanish y velocidad a 1,8.
Gracias - Rated 5 out of 5by sxravan, 8 months ago
- Rated 5 out of 5by Kevin, 8 months ago
- Rated 5 out of 5by D_rose.444, 8 months ago
- Rated 5 out of 5by Firefox user 16177882, 8 months ago
- Rated 1 out of 5by sfny, 8 months agoConstantly asking to change permissions on Android. It became so annoying I had to remove it altogether.
- Rated 4 out of 5by hunsai, 8 months ago
- Rated 5 out of 5by Michael J, 8 months ago
- Rated 2 out of 5by max.tela, 9 months agoIt is a cool idea and helps a lot with my dyslexia. But it works properly less than half of the time.
1. Detecting the text correctly, especially on websites where text is separated by other content or when there are multiple columns.
2. Often the reading out does not stop when click pause or stop, I have to close all Firefox windows to make the reading out stop. - Rated 5 out of 5by Federico Calzoni, 9 months agoPiper's voices are really good. I really appreciate the automatic language selection.
- Rated 5 out of 5by Firefox user 13284157, 9 months ago
- Rated 5 out of 5by LuisFer, 9 months ago
- Rated 2 out of 5by Firefox user 15621291, 9 months agoThe voice is good, but the controls don't do jack. The pause button does absolutely nothing ever, and the second time I tried the add on the highlighted text didn't match what was being read (no idea where in the document it was reading from) and this time I had to close the browser entirely to make it stop reading.