john doe, le ven. 08 août 2025 16:18:08 +0200, a ecrit: > On 8/8/25 4:12 PM, Samuel Thibault wrote: > > Aaron Chantrill, le ven. 08 août 2025 10:07:22 -0400, a ecrit: > > > On 8/7/25 22:31, Chime Hart wrote: > > > > Hi Aaron: I need to get some sound issues fixed on my main machine > > > > where Piper > > > > was installed with your commands. For some reason my laptop is not > > > > liking those > > > > commands. I just tried > > > > sudo talkwith piper-tts > > > > but it was unable to switch. Running spd-say -L only finds Alison 1 of > > > > my > > > > Voxin voices > > > > Chime > > > > > > Yes, speech dispatcher does not automatically find tts software when > > > installed. > > > > It does. > > > > > Some tts programs have modules for speech dispatcher, and I think > > > they get installed with speech dispatcher. > > > > And then speech-dispatcher sees them. > > > > When the tts is a library, you just need to install the > > speech-dispatcher module for that (we don't necessarily want to pull the > > library when installing speech-dispatcher, that'd clutter the disk and > > the list of synths). > > > > When the tts is a separate program, then speech-dispatcher module config > > file will detect it. > > > > > So usually I have to create a > > > custom module based on the generic module. > > > > It's another way of connecting to external synths. It's not the > > recommended way > > Which is?
The documented way: a module specific to the synth, which knows how to drive it in a more controlled way than just executing a command. Samuel
