Package Details: speech-dispatcher-git 0.12.0.rc3.r52.g7a04f7f9-1

Git Clone URL: https://aur.archlinux.org/speech-dispatcher-git.git (read-only, click to copy)
Package Base: speech-dispatcher-git
Description: High-level device independent layer for speech synthesis interface (development version)
Upstream URL: http://www.freebsoft.org/speechd
Licenses: GPL2, FDL
Conflicts: speech-dispatcher
Provides: speech-dispatcher
Submitter: sholmes88
Maintainer: stormdragon2976 (alex19EP, kyle, lilmike)
Last Packager: alex19EP
Votes: 10
Popularity: 0.000000
First Submitted: 2010-10-14 19:35 (UTC)
Last Updated: 2024-10-11 09:48 (UTC)

Dependencies (19)

Required by (183)

Sources (1)

Latest Comments

1 2 3 Next › Last »

stormdragon2976 commented on 2023-12-23 00:37 (UTC)

@cirlo I am glad you got it working. I tried to get here yesterday to help, but the universe conspired against me lol.

cirlo commented on 2023-12-22 18:13 (UTC)

my bad... I don't know why I was so stubborn on that, but I was so sure I hade to run speech-dispatcher's service through systemd 🙄

Just disabling it and running spd-say executes the daemon locally and manages to access output devices just fine!

cirlo commented on 2023-12-21 16:13 (UTC)

i get a similar error with AudioOutputMethod "alsa":

speechd:    Trying to make output module use audio output through server.
speechd:    Module set parameters.

speechd:  Error: Module reported error in request from speechd (code 3xx): 300-Opening sound device failed. Reason: server audio is not supported.
300 MODULE ERROR
.
speechd:    Output module does not support audio output through server, making it open audio by itself.
speechd:    Module set parameters.
ALSA ERROR: Cannot open audio device default (Host is down)
ALSA ERROR: Cannot initialize Alsa device 'default': Can't open.
speechd:  Error: Module reported error in request from speechd (code 3xx): 300-Opening sound device failed. Reason: Couldn't open alsa plugin.
300 MODULE ERROR
.
speechd: ERROR: Can't initialize audio in output module, see reason above.
speechd: Speech Dispatcher 0.12.0-rc1 log start
speechd: Error [speechd.c:682]:No speech output modules were loaded - aborting...

The strange thing is that with spd-conf --test-alsa and spd-conf --test-pulse I verified that both ALSA and PulseAudio (or PipeWire in my case) work.

cirlo commented on 2023-12-21 15:31 (UTC) (edited on 2023-12-21 15:32 (UTC) by cirlo)

Hi again! Do models using sd_generic (i tried both with epos-generic and piper) work on your system?

I seem to always have a problem with pulseaudio:

speechd:    Trying to make output module use audio output through server.
speechd:    Module set parameters.
speechd:  Error: Module reported error in request from speechd (code 3xx): 300-Opening sound device failed. Reason: server audio is not supported
300 MODULE ERROR
.
speechd:    Output module does not support audio output through server, making it open audio by itself.
speechd:    Module set parameters.
pulse.c: pa_simple_new() failed: Connection refused
speechd:  Error: Module reported error in request from speechd (code 3xx): 300-Opening sound device failed. Reason: Couldn't open pulse plugin.
300 MODULE ERROR
.
speechd: ERROR: Can't initialize audio in output module, see reason above.
speechd: Speech Dispatcher 0.12.0-rc1 log start
speechd: Error [speechd.c:682]:No speech output modules were loaded - aborting...

if i try to use spd-say anyway, i get:

Failed to connect to Speech Dispatcher:
Error: Can't connect to unix socket /run/user/1000/speech-dispatcher/speechd.sock: Connection refused. Autospawn: Server successfully autospawned

i use pipewire-pulse run by user through systemd

cirlo commented on 2021-08-03 19:58 (UTC)

@alex19EP thank you very much for your speed in listening to my request! ^^ The same cannot be said about my reply :{

alex19EP commented on 2021-07-14 12:45 (UTC)

@cirlo no need to be sorry for asking anything. I added pico support.

cirlo commented on 2021-07-14 07:02 (UTC)

I am sorry for asking, but why was pico support removed? It did work fine for me and I found it working the best in my mother tongue...

alex19EP commented on 2021-07-11 19:29 (UTC)

@ph34rb0t

You can do what you want in your PKGBUILD, stormdragon does what he/she wants in his/hers.

one of the nice things about arch in general, and aur in particular, is that we are working together to make the ecosystem better and more convenient for everyone.

@stormdragon2976 pleas apply my patch at: https://gist.github.com/alex19EP/077a8a30e89f0f06ddc4221a9e6ccfd0

ph34rb0t commented on 2021-05-20 15:27 (UTC)

You can do what you want in your PKGBUILD, stormdragon does what he/she wants in his/hers.

alex19EP commented on 2021-05-20 10:45 (UTC)

@ph34rb0t sorry but i don't agree.

  1. I try to make my pkgbuilds look good and conform to arch standards.
  2. as I already said, to compile a package, you need components from the base-devel group, if someone does not have it installed, or is not fully installed - you should warn him about this, and not bypass this error.

1 2 3 Next › Last »