Thank you, very much, Samuel!
I have included a .cc in this reply... A very good suggestion! Thank you, Samuel! !
Samuel's response to my original query and my subsequent queryes, are interleaved below...
On Thu, Jul 11, 2024 at 01:29:18AM +0200, Samuel Thibault wrote:
--> Hello,
-->
--> Please always keep a mailing list in Cc, so that I am not the only
--> recipient of the mail. Writing to me only means risking falling in the
--> middle of my vacations and thus not getting an answer for weeks, or that
--> I just don't have the time to answer and thus you would at best get a
--> terse answer, or worse, no answer at all... Conversely, keeping a list
--> in Cc means avoiding all these issues completely, you'll involve all the
--> community to help you, make the answers you get available to everyone,
--> and even archived for web crawlers to find them whenever somebody has
--> the same issue.
-->
--> Terry D. Cudney wrote:
--> > It seems that somethings have changed in the Debian/Ubuntu/etc boot process. On examining /etc/grub.d/ there are two files 10_linux and 10_linux_zfs, each with a variable, "quiet_boot" initialized to "1". I may be "barking up the wrong tree" so to speak, but is this where speakup is silenced during the boot process?
-->
--> No, that just silences the kernel messages.
OK, I'd like to be able to see those too...
-->
--> The expected way to get speakup auto-start on Debian is just
--> to have espeakup installed. The espeakup systemd unit in
--> /lib/systemd/system/espeakup.service is then in charge of loading
--> speakup_soft before starting espeakup.
Even though I installed Ubuntu 22.04 using the "s" option with the installer, (speakup was active during the installation) there was no speech after the initial reboot. I manually installed espeakup with apt but still no speech. lsmod showed speakup and speakup_soft to be loaded. as expected (not sure if they were loaded before I manually installed espeakup), but stillno speech output.
-->
--> If it's not working, you'd have to check systemctl status espeakup
Again, this was after manually installing espeakup, systemctl status shows espeakup to be loaded, enabled and active still no speech.
-->
--> > Ideally, one should be able to confurrently run speakup in the cli and orca in the gui (in a separate console, perhaps via startx).
-->
--> The problem will them be concurrent access to the audio card between
--> espeakup and speech-dispatcher. If in the desktop you use alsa and the
--> dmix module, that should work fine.
Ah! That seems to be where the problem lies! The desktop is using pipewire/pulseaudio.
**--**> *** Key question:
What is the best way to disable pulseaudio/pipewire/wireplumber/whatever and force the desktop to use alsa, dmix?
-->If you use pulseaudio or pipewire
--> you'll get a conflict. This is a concern that I've never found time
--> to tackle, and I have hoped for years that somebody else would have
--> a look at it since it won't involve coding, but discussing properly
--> with pulseaudio/pipewire people to work out a proper solution. In the
--> meanwhile people have rather looked at workarounds and stay half-happy
--> with that...
-->
--> Samuel
I'm happy to lose pulseaudio/pipewire et al and use alsa/dmix.
Question out of curiosity: What does pulseaudio add; why are distributions seeming to abandon alsa in favour of pulseaudio?
My naive observation is that pulseaudio just adds a lot of complexity...
--terry
--
Name: Terry D. Cudney
Telephone: 289-488-4882 ext 1
E-mail: terry@xxxxxxxxxx
