Hi Chris, Thanks for the responce, I should have writen a follow up as I have figured some of this out but I had not had a chance yet. As I have fixed some things and have a better understanding of others, let me give a summery of where things are in which I will hopfully cover your questions rather than doing a point by point.
Changes and what I have learned Well the 2 big things are that I have it working with the dectalk software and the remaining problem is not due to bluetooth, but just with Alsa as it happens even with a coventional headset. dectalk software is working if wrapped by aoss and appropriate .asoundrc file. I am redirecting it to dmixer which allows sounds and speech to occur at the same time. I am still working on the asound file and don't want to post it 'till I have it right, but I found much of what helped at the alsa wiki: http://alsa.opensrc.org/index.php/.asoundrc http://alsa.opensrc.org/index.php/Dmix and from there many other pages on that site. this site held the answer to the "buffer" and other asound questions and it seems you found it as well. When I was using the /dev/dsp directly the sound was not clear. Passing it through plughw alsa device did the needed transformations but I did not see how to have any sound sent to /dev/dsp be sent to this location. I still have only found a partial solution, but I think I may be on to the full solution. The ttsynth (was IBM outloud) text to speech is much more natural sounding than the dectalk. I am still unable to use ttsynth with alsa but I am trying to systematically work through the options and then I will write the folks at ttsynth. Let me clear up the "pin" question as I have not explored that yet though I am sure there is an answer. When you first connect to the bluetooth headset you have to give a pin or security code, usually "0000" for headsets. I am looking for a way to either have that entred automatic or at the command line. Currently I am using a gui to do it and I don't like that as a long term solution as I do much of my computer work without video. It looks like there are several ways to accomplish this task but as I have been more intersted in trying to clean up the sound I have been using the gui for now to give the pin. If someone has had success with a particular non gui method of feeding the pin to the system please let me know. Short of that I will figure it out if and when I get outloud working over the headset. If I don't I will likly return the headset and will therefore not need an answer until I get my keyboard moved to bluetooth, and that is a little ways off. I hope I have answerd the questions I raised. I will post a more through solution once I have it. Thanks again for responding, -Greg -- Greg Priest-Dorman [EMAIL PROTECTED] THIS SPACE INTENSIONALLY LEFT BLANK _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Oct 3 - Security and Privacy Nov 7 - Django Python Application Framework
