Hey, Greg. On Thursday 01 November 2007, Greg Priest-Dorman wrote: > 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.
Okay. Sounds like you're making good headway on this.
> 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.
Ah. I dont know if Alsa OSS allows for simultaneous sound playing, or if
playing a sound lock the sound device as OSS would.
Anyway -- I think I understand what you're trying to deal with on this.
> 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.
Ah okay. I remember this coming up when I was doing some work with the
BlueZ Bluetooth stack. I believe the bluez-utils package handles that. On a
Debian box I have here there's a file containing a script
in /etc/bluetooth/pin which simply contains:
#!/bin/bash
echo "PIN:1234"
And there's also a default PIN code in /etc/bluetooth/hcid.conf
...
options {
...
# security auto = use local PIN for incoming connnections
security auto;
# Default PIN code for incoming connections
passkey "1234";
}
...
The docs for the bluez-utils package in /usr/share/doc/bluez-utils might
also give you and idea of where the PIN/passkey can be set.
> 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.
I'm sure there's a way to do it without the GUI, it's just a little
confusing. But I have figured out that the bluez-pin package isn't required
to do it from the command line.
Hope this helps some.
> Thanks again for responding,
Likewise.
-- Chris
--
Chris Knadle
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
