Hay Chris,

>>>>> "Chris" == Chris Knadle <[EMAIL PROTECTED]> writes:


Chris>  ...  I dont know if Alsa OSS allows for simultaneous sound playing, or 
if 
Chris> playing a sound lock the sound device as OSS would.

Yep, aoss when directed to dmix is having no problem playing
simultaneous sounds.  I found the directions on the alsa wiki refered
to in my last post.

Chris> ...Debian box I have here there's a file containing a script 
Chris> in /etc/bluetooth/pin which simply contains:

Chris>       #!/bin/bash
Chris>       echo "PIN:1234"

Chris>    And there's also a default PIN code in /etc/bluetooth/hcid.conf
Chris>         ...
Chris>         options {
Chris>            ...
Chris>            # security auto = use local PIN for incoming connnections
Chris>            security auto;
Chris>            # Default PIN code for incoming connections
Chris>            passkey "1234";
Chris>         }
Chris>         ...

I have tried both these methods to no avail.  But again, not exausted
all options.

Chris>    The docs for the bluez-utils package in /usr/share/doc/bluez-utils 
might 
Chris> also give you and idea of where the PIN/passkey can be set.

Well, I gave them another look, and this time noticed this comment
in README.Debian.gz:


   The old infrastructure /etc/bluetooth/passkey has been removed
   since the agent is supposed to be started by a user session. It is
   not meant to be system-wide.

So, that is why that did not work, but a little later on it says:

   Note to the tech-savy:
   If you are stuck in console and absolutely need to pair with your
   bluetooth device have a look at
   /var/lib/bluetooth/<your_device_address>/pincodes. Please note that
   this mode of operation is _not_ _supported_. Don't mess with files in
   /var/lib/bluetooth/ unless you know what you are doing. I repeat:
   manually adding a pincode for a remote device is NOT SUPPORTED.

Well, sounded like an invitation to me...

I created a file called "pincodes" with one line in it,
the address of my bluetooth device and the pin.  That worked!

So, not supported, will probably stop working with the next release,
but for now that issue is solved.  Back to ttsynth.

Thanks for your help,

-Greg

-- 

 Greg Priest-Dorman
 [EMAIL PROTECTED]


    [this space intentionally 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

Reply via email to