The original pyttsx is py2, with a fork for p圓. I have brew-installed py2.7.13 and p圓.6.1 and using pip3 or pip, was unable to successfully install either version. At first this looked promising, but there are several fatal issues, focusing on the python methods outlined here: There are several python packages that enable TTS within a python script.Some notes to self as I continue to explore this question I'm hoping MS did their accessibility homework and deployment as well as Apple has. "Copy and paste into notepad" however is a kludge as well. I'm open their may be different but similar ways to do the above. What is the native way to have Windows 10 Narrator read selected text in a fashion as straight-forward as selecting text in any application, invoking a keyboard command, and Win10 perform TTS services?.Is there an equivalent way to pass a formatted text file on Win10 to an MS binary for processing, similar to the "say" command on Mac? I see docker images that are TTS specific, thought that seems more kludgy.Firefox has a "reader" mode which largely helps and works well under Windows.This is similar to #2, however, I might decide it's worth creating a file for podcast if the read text captures my attention, and I'll shift to a #1 process.Using TTS to read selected browser text on long articles I wish to hear while I perform non-attention-demanding tasks.Looking at Narrator's interface, I found it very difficult to figure out how to get Narrator to read selected text across applications, i.e., Outlook, Firefox, Word, and so forth. Yes, I can copy and past into Notepad, but that's clumsy.I find errors more easily when I have my Mac read my written text back to me. Live proof-reading of emails or documents I'm creating.I used ReadAloud's TTs software in the past, but was always more kludgy than the above. The last time I switched from Mac to Windows, I dearly missed having this. Thanks to bash scripts, the above takes 5 seconds of my time.Using lame, I then convert this to an mp3 and using dropcaster, push the mp3's to a static public location where my podcast client can retrieve it. After text markup is complete, I pass the formatted text through the "say" command, which creates an AIFF of the text-to-speech.For example, this script inserts a "silence" command that helps me identify paragraph markers when I listen to the read text. My current Mac workflow: I copy the source from my email, use a vim script that removes HTML, leaving the text I wish to have read.Converting reformatted text from emails that I wish to have read to me at a later time.I use it in three specific ways, though a combination of the below defines 90% of my use-cases. I've long taken advantage of Mac's Text-to-Speech integration. I perform this only with Open Source tools, too, except for the "say" command. On my Mac, I can provide an input, and get an MP3 TTS file with no user intervention in-between, for my #1 scenario, below. I also wish to emphasize that "copy and paste into a third party TTS application" is unsatisfactory. For example in this 2012 SuperUser post, the questioner has the same issue, with no satisfactory answer provided. One of my use cases is for Narrator to only read selected text, as I outline below. Granted, my use-case isn't related to being visually-impaired. I've been through the Microsoft Narrator documentation, which I've found unhelpful. This post focuses on Text-to-Speech OS integration. Switching OS's, however, has two seemingly insurmountable areas which concern me. However, Apple's recent disappointing and lackluster focus on MacOS and their hardware, and a Lenovo X1 Yoga, 2nd Generation, has caught my attention. Apple's tight integration of POSIX-compliant file paths and a command line interface, and their historically strong hardware and manufacturing standards have had me on the Mac platform for years.
0 Comments
Leave a Reply. |