diff options
| author |   B. Watson | 2019-12-19 11:05:20 +0100 |
|---|---|---|
| committer |   Willy Sudiarto Raharjo | 2019-12-21 05:02:46 +0100 |
| commit | a399bd9fe5940198d6a9b4b205c116d44f135bdb (patch) | |
| tree | 7f93aec97d785ef0b1d9f3823d95d1dde9a3db68 /accessibility/espeak/README | |
| parent | baaff0cb3041fab20dcf6322f38b709283d1e800 (diff) | |
| download | slackbuilds-a399bd9fe5940198d6a9b4b205c116d44f135bdb.tar.gz | |
accessibility/espeak: Add pulseaudio, make portaudio optional.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'accessibility/espeak/README')
| -rw-r--r-- | accessibility/espeak/README | 32 |
1 files changed, 24 insertions, 8 deletions
diff --git a/accessibility/espeak/README b/accessibility/espeak/README index 19f50b44bc..2016c84024 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. |