Hey Greg. On Thursday 01 November 2007, Greg Priest-Dorman wrote: > > On Thursday 01 November 2007, Chris Knadle writes: > > ... I dont know if Alsa OSS allows for simultaneous sound playing, > > 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.
Cool; I was hoping that was the case. Thanks for the info. > > 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. > > 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. Ah hah. But even though that's the case, the files that aren't used anymore are still around? Agh. Seems like this area of the BlueZ stack is volatile [and annoying]. > 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... Yep! Good find; thank goodness somebody documented this. > I created a file called "pincodes" with one line in it, > the address of my bluetooth device and the pin. That worked! Excellent. > So, not supported, will probably stop working with the next release, > but for now that issue is solved. Back to ttsynth. Exactly -- you can expect it to break, but at least it works for now. Hopefully after whatever way this changes there will be a new method to supply the pincode/passkey/pin without the GUI. Or, failing that, perhaps they could at least agree on a naming convention so that the documetation can be grepped. Geez. > Thanks for your help, :-) Cheers and good luck. -- 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
