From: Alan Conway <aconway@redhat.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Plantronics 510 headset: playback partially works, but not recording
Date: Mon, 12 Mar 2007 12:39:05 -0400 [thread overview]
Message-ID: <45F58229.50403@redhat.com> (raw)
In-Reply-To: <20070311205548.GQ8187@alcor.net>
Matt Zimmerman wrote:
> On Sun, Mar 11, 2007 at 01:32:23PM -0700, Matt Zimmerman wrote:
>
>> Playback seems to be mostly working. I can play short sounds to the headset
>> using aplay. I tried playing a song (resampled to 8kHz mono) as a test, but
>> it cuts out periodically, approximately once per second. I hear about 0.25
>> seconds of audio followed by 0.75 seconds of silence, etc. I'm not sure
>> whether this is due to aplay or a problem with the bluetooth setup; is this
>> expected to work?
>>
>
> I found an example which used aplay -B 1000000, and that fixes the
> stuttering. Still no luck yet on recording.
I'm trying to get a similar setup to work, here's my previos post with
my status so far, would love to hear of any breakthroughs you make:
Trying to use a plantronics 510s with skype.
Update on my attempts, I've established the setup that almost works. By
almost works I mean:
- aplay, arecord -D headset work, quality is fine for telephone use.
- aoss skype almost works: I can hear the test call clearly, I can
record a message but when it is played back my voice is garbled beyond
recognition.
My next step is to fiddle with pcm settings - I've seen .asoundrc
scripts for skype and dmix that do conversions between 8 and 16 bit
formats and other stuff I know nothing about (but am afraid I'm gonna
learn). Here are the details of how I got this far:
== DETAILS: based on btsco/docs/build.html from CVS, slightly modified.
install libsbc:
Note: When asking for a password simply press Enter.
cvs -d:pserver:anonymous@sbc.cvs.sourceforge.net:/cvsroot/sbc login
cvs -d:pserver:anonymous@sbc.cvs.sourceforge.net:/cvsroot/sbc co sbc
cd sbc
./bootstrap
./configure --prefix=/usr
make
sudo make install
install bstco:
cvs
-d:pserver:anonymous@bluetooth-alsa.cvs.sourceforge.net:/cvsroot/bluetooth-alsa
login
cvs
-d:pserver:anonymous@bluetooth-alsa.cvs.sourceforge.net:/cvsroot/bluetooth-alsa
co btsco
cd btsco
./bootstrap
# Note I added CFLAGS in ./configure. Without them the plugin emits
# a torrent of debug messages that slow it down and ruin the sound quality.
# -NDEBUG is essential, -03 is just for good luck.
./configure --prefix=/usr --enable-alsaplugin CFLAGS="-NDEBUG -03"
make
sudo make install
** Using from skype
My .asoundrc is copied from btsco/alsa-plugins/asound.conf with the
headset address replaced by my own and the following addition for aoss:
# Use headset via aoss emulation for skype.
pcm.dsp0 {
type plug
slave.pcm "hw_headset" }
Full .asoundrc attached. Run skype as "aoss skype" (you need alsa-oss
package installed.)
== NOTES
The instructions at http://bluetooth-alsa.sourceforge.net/build.html did
*not* work for me. The plugz version of the plugin requires a different
.asoundrc (based on plugz/asound.conf) but aplay -D headset gave me:
[aconway@scooter plugz]$ aplay -D headset /usr/share/sounds/startup3.wav
Playing WAVE '/usr/share/sounds/startup3.wav' : Signed 16 bit Little
Endian, Rate 44100 Hz, Stereo
aplay: set_params:909: Channels count non available
Cheers,
Alan.
------------------------------------------------------------------------
pcm.headset {
type plug;
slave.pcm "hw_headset";
}
pcm.hw_headset {
@args [BDADDR TIMEOUT MAX_PERIODS]
# The Bluetooth device address for target headset, used for Audio Gateway (PC) initiated connections
# Please note that this value is ignored when the connection is Headset initiated
@args.BDADDR {
type string
default "00:03:89:95:9C:83" # Put your HS address here
}
# This value represents how long we will try to reach the headset, until we give up.
# Value is in milliseconds
@args.TIMEOUT {
type integer
default 6000
}
# This is the size of the buffer used to queue Voice packets. Value must be between
# 2 and 334 (~ 1 second). Default value is 2 buffers, which works well most of the
# time, and has the advantage of giving us an ultra low delay
@args.MAX_PERIODS {
type integer
default 334
}
type sco
bdaddr $BDADDR
timeout $TIMEOUT
max_periods $MAX_PERIODS
}
ctl.headset {
type sco
}
pcm.a2dpd {
type a2dpd
}
# Use headset via aoss emulation for skype.
pcm.dsp0 {
type plug
slave.pcm "hw_headset"
}
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-03-12 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 20:32 [Bluez-users] Plantronics 510 headset: playback partially works, but not recording Matt Zimmerman
2007-03-11 20:55 ` Matt Zimmerman
2007-03-12 16:39 ` Alan Conway [this message]
2007-03-22 3:18 ` Matt Zimmerman
2007-03-22 4:57 ` Matt Zimmerman
2007-04-03 1:55 ` Alan Conway
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45F58229.50403@redhat.com \
--to=aconway@redhat.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox