Digital Mode Text-To-Speech
This article is for blind and vision-impaired amateur radio operators who want to hear spoken text from a digital mode decoder. It describes features in MultiPSK and TrueTTY that make text-to-speech operation possible. cocoaModem for Mac OS X is described in a separate article.
Software
MultiPSK freeware by F6CTE decodes an impressive number of ham digital modes. The registered version adds some Professional modes and other capabilities. MultiPSK has a long list of features, including integrated logging and automatic mode recognition & switching using Reed-Solomon codes.
TrueTTY by UA9OSV works with a number of the most popular digital modes. There is a free version and a registered version that saves configuration settings. With fewer integrated features than MultiPSK, the user interface and documentation of TrueTTY are less complicated.
MultiPSK Text-to-Speech
MultiPSK has two voice options for speaking decoded words:
• the Microsoft voices built into Windows, and
• the DigiTalk voice customized for hams by KH6TY.
In addition, two modes can be spoken, one character at a time,
using a MultiPSK English or French voice file:
• JT65, a weak signal digital mode by K1JT, and
• VOICE, a digital mode created by F6CTE for blind and
vision-impaired hams.
Both of these are error-correcting modes designed to work well in very low signal-to-noise conditions. VOICE is derived from an Olivia mode. In JT65 mode, MultiPSK opens a "Functions for blind or partially sighted Hams or SWL" subpanel for turning vocalization on/off, selecting the language, and displaying received text using a larger font.
The DigiTalk add-on to MultiPSK now works with all versions of Windows. (Windows 7 users must install MSAgent via a Microsoft hotfix.) It adds another very useful option—automated search for signals on the waterfall—which is described in the article on MultiPSK accessibility.
Text-to-Speech With TrueTTY
TrueTTY does not have a built-in speech function, but it can be used with any screen reader software. Readers are not designed to work in a text window with streaming characters and scrolling lines, but TrueTTY can transfer decoded text to Windows Notepad, where a screen reader can be used. From the DXSoft website:
"The menu command 'File / Open Buffer in Notepad' saves the visible part of the receiving buffer (about the last 20 KB) in a temporary file and opens this file by a text editor. Then you can view this file or print it. The hotkey of this command is CTRL-N."
In 2008, Brian Semmel, W1BLS, reported in his blog (no longer available) that he used this feature of TrueTTY to operate with PSK31 and other digital modes.
A printed example of a QSO is here.
Text-to-Speech Quality
The DigiTalk voice is an improvement over MicroSoft Windows voices because it spells out most call signs and Q signals. It is more convenient than typing keyboard shortcuts for a screen reader with TrueTTY.
The tradeoff is an increased number of pronunciation errors, compared with a dedicated screen reader like JAWS. KH6TY commmented, "Digitalk will translate 'hamspeak' fairly well—well enough to have a meaningful QSO, but will pronounce 'OK' as in 'Oklahoma'—nothing I can do about that except by incorporating a very powerful program..." Call signs may require clarification. For example, "Y" might be spoken as "E" and can be resolved by requesting the phonetic word (Yankee).
The text-to-speech options described here are major advances in accessibility, and they are all worthy of consideration.
Sound Card Connections
Two sound cards are used for text-to-speech—one for signal processing and one for the speech synthesizer.
MultiPSK automatically makes the connections and lists them in sound card configuration menus on the Configuration screen. The card or chipset used by MultiPSK for signal processing is called the "Sound Card," and the card/chipset for optional speech synthesis is the "Auxiliary Sound Card." By default, the "Sound Card" is the one designated in Windows Sound Control Panel as the default recording device. The "Auxiliary Sound Card (to speaker)" menu choice in MultiPSK should always be the PC Speaker sound card, so spoken text is not transmitted on the band.
In the TrueTTY "Input Sound Card" menu (Setup→Interface Tab) select the sound card for signal processing (eg, USB audio CODEC). Select the same card in the "Output Sound Card" menu. For screen reader output: In Windows Sound Control Panel select the computer's primary sound device as the default playback device (eg, Realtek High Definition Audio) so spoken text goes to the PC speaker.
For More Information
MultiPSK is described in English here and French here. The developer, F6CTE, participates in the MultiPSK User Group.
An overview of TrueTTY is here. The developer, UA9OSV, participates in discussions about TrueTTY on the DXSoft User Group.
MultiPSK accessibility and TrueTTY accessibility are described in separate articles.
Summary
MultiPSK includes integrated text-to-speech options. The DigiTalk voice add-on is customized to spell most call signs and Q signals. The weak signal JT65 and VOICE modes use error-correction, and the characters are spoken one at a time.
TrueTTY has a standard user interface that includes keyboard shortcuts. It can be used with any screen reader program.
Acknowledgments
Special thanks to Patrick, F6CTE, for the accessibility features in MultiPSK and to Skip, KH6TY, for developing DigiTalk. Thanks to Brian, W1BLS, for his blog about TrueTTY for blind operators, and to Kathy, KB1OLH, for her comments on the blog. Patrick, F6CTE, and Sergei, UA9OSV, answered my questions. Franco, 3A2MW, recommended MultiPSK.
Author Information
Peter DeNeef, AE7PD, is an Extra Class amateur radio operator in the U.S. This Web site has no ads or conflicts of interest.
Email: HamRadioAndVision "at" gmail "dot" com.
rev. 2/15/2012