Hello Kirk and all, Do to the generosity of one of my teachers, I have access to an echo at least for a little while since my DoubleTalk LT might be off to England or wherever to be repared. I want to add a driver for it based on either the BNS or ltlk drivers, as it displays some characteristics of both. For example, both the echo and bns use control-e as their command character, but the echo has 100 different pitch settings like the DoubleTalk LT. My questions are: 1. besides changing the appropriate .c file (either speakup_bns.c or speakup_ltlk.c), what do I need to do to put the new driver into the list of synths to compile into the kernel? 2. Is there any way to slow down how much text is sent at a time besides lowering the baud rate? The reason I ask is because the echo will often say part of something and then pause for five seconds before finishing, most often with colons, dashes, or periods involved. Needless to say, this is very annoying. 3. Would it be possible to lower the priority of speakup's speech? BC I had mplayer playing some stuff over nfs (no, bandwidth wasn't the problem) and it would stop whenever the echo would speak. I'm not talking about being in mplayer, oh no, I was in irssi and just one message would often be enough to interrupt mplayer despite the fact that it was running on another console. 4. Would anyone care, or use the driver, or would me investing the time and effort merely be an exercise for me? Okay I have a few more questions... is the synth-specific code totally separate from the common speakup code, as in there are no statements like if (synth == xyz); /*do something one way*/ ETC. Also, where are the minimum and maximum limits for things like pitch defined? I'd think in the synthesizer-specific files, but I didn't find anything obvious. Thanks for your time. Garrett
