-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Jonathan Duddington: # Does the problem only happen in the interactive mode where you start by # typing # speak # followed immediately by Return ? Actually no. It occurs anywhere that a line of text starts with a punctuation such as a : or , by itself, only that line is to be spoken and portaudio19 is being used. In other words, the problem doesn't occur when reading a text file either using speak -f or via a pipe such as cat file|speak. It also doesn't occur if portaudio19 isn't being used, such as when a wav file is created or speech output is sent to stdout. Here are some test lines that will reproduce the problem both on the speak command line as well as via its standard input: : hello ? How are you? , testing eSpeak ! eSpeak rocks! Just put any of these lines in quotes on the command line or run speak and type the line. Either way, eSpeak returns to the command prompt without speaking when using portaudio19. HTH, Lorenzo - -- I've always found anomalies to be very relaxing. It's a curse. - --Jadzia Dax: Star Trek Deep Space Nine (The Assignment) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFI6/DG9IpekrhBfIRAogkAKDJ1e5VUWbH3FaLunQyJINkxt+RJgCaAqtO PmOmZvw9F2qp+SOFFTEcPmo= =br6N -----END PGP SIGNATURE-----
