Re: pulseaudio and espeakup
- To: firstname.lastname@example.org
- Subject: Re: pulseaudio and espeakup
- From: email@example.com
- Date: Tue, 17 Jul 2018 12:17:41 +0200
- Message-id: <[🔎] 20180717121741.Horde.ydANzIp3If-k8Xy3SKMQWg5@webmail.df.eu>
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <firstname.lastname@example.org> <CAAfdZj-agFTPvL=cd5QbGBNwQtspV+9y5YpynjfGJMgNnZU5KA@mail.gmail.com> <email@example.com> <firstname.lastname@example.org> <email@example.com> <20180504082503.frtcqivmd65rz3ab@Kraftkrust> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
maybe this is the same issue i had with fenrir.
fenrir outputs its sound to a pulse instance as root and orca fires
the sound via the pulse instance of the user.
i wired up a small setup script that configures the root pulseaudio
instance to stream its sound to the user instance.
so both can talk at same time without locking a hardware.
it needs to be run once as user and once as root to configure both
parts. then a restart is requred to bring all pulse intances on pair
with the new config.
maybe this helps in anyway
Zitat von Samuel Thibault <firstname.lastname@example.org>:
Michael A Ray, le ven. 04 mai 2018 13:18:08 +0100, a ecrit:
Perhaps a way to try is to run speech-dispatcher in TCP socket mode in a
Well, I don't think a container is needed, you can just run
speech-dispatcher as a system service.
And the problem is not there, but rather: how will it be able to
access the sound card? Unless it is running as the same user as other
pulseaudio sources, there will be a conflict on the grabbing of the
But one problem I anticipate is the way to persuade Orca that SD is
there and does not need to be launched by it.
That is already handled by speech-dispatcher when configure