Re: [Emacspeak] Pipewire v 1.0.2 broken

["T.V Raman" <raman@xxxxxxxxxx>]

All this is accurate, have verified all of this while I came up to
speedh with pipewire on my laptop -- pipewire 0.38 on a debian system.

Only other bit I have to add:

1. No sound system on Linux can work without alsa -- so pipewire or
   pulse or jack, the sound card is ultimately managed/driven through
   alsa.
   

Tim Cross writes:
 > 
 > To keep things together for future reference
 > 
 > - The software dectalk package will build against either pulseaudio or
 >   alsa. To link against pulseaudio, you must have the pulseaudio library
 >   development package. For example, on Fedora 39, this is
 >   pulseaudio-libs-devel. I did not have this devel package installed as
 >   it hasn't been required for anything else and it is easy to miss the
 >   fact that the dectalk has built against alsa. 
 > 
 > - Note that Fedora 39 is a fully pipewire enabled distribution. However,
 >   as I understand it, pipewire is reallyh a layer on top of pulseaudio
 >   and alsa, not a replacement for them. So you sitll need the alsa libs
 >   to build IBM ViaVoice and you should install the pulseuadio library
 >   development files to have the software dectalk built against pulse
 >   rather htan alsa.
 > 
 > - Prior to the update of pipewire which broke alsa, I had been using the
 >   software dectalk and the dtk-soft server with no problems linked
 >   against alsa. Seems the software dectalk can work equally as well
 >   against either pulse or alsa and will default to pulse if it can and
 >   fall back to alsa if it cannot. 
 >   
 > 
 > "T.V Raman" <raman@xxxxxxxxxx> writes:
 > 
 > > Tim,
 > >
 > > Following up to myself:
 > >
 > > 1. Verified that tcldtk.so does not link in lasound2 (alsa lib) --
 > >    confirm using ldd on the .so file.
 > > 2. Similarly -- the Dectalk libs --  do not link in alsa libs.
 > > 3. This is why say works, but then dtk-soft should too ...
 > > 4. Unless you perhaps didn't have the optional pipewire-pulse
 > >    installed -- since the Dectalk  engine does use pulse for output.
 > > 5. But then the mystery -- how did the say binary work?
 > > 6. Treat this  more as a curious puzzle that might increase our
 > >    understanding rather than something to solve.

--