aboutsummaryrefslogtreecommitdiff
path: root/accessibility/espeak/README
diff options
context:
space:
mode:
Diffstat (limited to 'accessibility/espeak/README')
-rw-r--r--accessibility/espeak/README32
1 files changed, 24 insertions, 8 deletions
diff --git a/accessibility/espeak/README b/accessibility/espeak/README
index 19f50b44bc08f..2016c84024ef7 100644
--- a/accessibility/espeak/README
+++ b/accessibility/espeak/README
@@ -6,14 +6,30 @@ quite different. It's perhaps not as natural or "smooth", but some find
the articulation clearer and easier to listen to for long periods. It
can run as a command line program to speak text from a file or from stdin.
-To build without portaudio support, set WAVONLY=yes in the script's
-environment.
+Build options (environment variables):
-If you get errors like this:
+PULSE Build PulseAudio output support (yes/no)? Default is "yes".
-bt_audio_service_open: connect() failed: Connection refused (111)
+PORTAUDIO Build PortAudio output support (yes/no/auto)? Default is "auto",
+ which will build in PortAudio support if it's installed.
-...either ignore them (if espeak produces audio anyway), or comment out
-the 'pcm.headset' and 'ctl.headset' stanzas in /etc/asound.conf. This
-should only happen if your Slackware system was upgraded from an older
-version.
+Use PortAudio[1] for plain ALSA[2] audio output, if you don't want to use
+PulseAudio. However, if you're happy with PulseAudio, it's recommended NOT
+to build PortAudio support into espeak (you won't need it anyway).
+
+Note that if both options are "no" (or if PULSE=no and portaudio isn't
+autodetected), the resulting binary will not be able to make sound
+(it will only produce .wav files).
+
+The slack-desc will be updated to let you know which audio drivers
+(if any) were included.
+
+[1] Using PortAudio with espeak results in a lot of scary-looking
+ warnings from espeak, but you can ignore them so long as you
+ can hear its speech.
+
+[2] Or JACK audio, if your portaudio package was built with jack2 or
+ jack-audio-connection-kit installed. Or... PortAudio can also feed
+ audio to PulseAudio, if its daemon is running. Or, if you have OSS
+ modules loaded, PortAudio can use that, too. The Linux audio driver
+ ecosystem is a really weird place.