On Tuesday 30 October 2007, Greg Priest-Dorman wrote: > I am able to redirect /dev/dsp to the headset. > > I am able to do all my sound except text to speech in alsa and as such > have it use the plughw:Headset alsa device which does a nice job of > converting the sound for the headset so it does not sound choppy. > > The big problem is this: > I rely on text to speech.
I had a look at your website that you pointed to and spent some time trying
to read this and figure out what's going on, but I'm still confused. If
you've redirected /dev/dsp and that works, then where is the audio from the
text-to-speech software going instead?
> I am not able to get either of the text to speech packages I use to
> use the plughw:Headset device. They send to /dev/dsp. I have tried
> various things including aoss, renaming, moving /dev/dsp, asoundconf
> and such, but while I am able to get speech sent to /dev/dsp to come
> out the bluetooth headset, it is clearly going right to the hw:Headset
> and not passing through the rate conversions that plughw:Headset
> offers so it sounds hidious.
I assume you've also tried making /dev/dsp a soft link to the associated
bluetooth device in /dev/ -- I remember doing something like that to
redirect /dev/sequencer long ago which I remember working. If by chance this
works you'll probably have to figure out how to make that link at boot time
if you're using udev.
> On a more minor side, does anyone know the asoundrc lines for buffer
> time and period time? I am seeing how to set it on a per program
> basis, but would like the defaults set differently than they are.
Until now I had never even known about .asoundrc files, so this is kind of
an eye-opener. This page at the ALSA project [that you've probably looked at
already] is the best thing I've found on these so far:
http://www.alsa-project.org/main/index.php/Asoundrc
I've never had to play with these, and the Debian system I'm using doesn't
seem to use these by default, nor is there much mention of them in the
installed docs from ALSA related packages.
> Speech is from either ttsynth (the current comercial version IBM
> outloud aka viavoice ) or fonix dectalk (software dectalk).
Any idea what these packages are using as the output device? Is that
something configurable? [Yeah, I realize these are stupid questions, but I'm
pulling at straws.]
> On the much less critical side, I am looking for a non gui way to get
> the pin into this thing so I can automate paring.
I didn't understand this. Does this relate to how to get the BT headset
connected or set up?
-- 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
