Linux bluetooth development
 help / color / mirror / Atom feed
From: Matt Zimmerman <mdz@ubuntu.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Plantronics 510 headset: playback partially works, but not recording
Date: Wed, 21 Mar 2007 20:18:35 -0700	[thread overview]
Message-ID: <20070322031835.GJ7472@alcor.net> (raw)
In-Reply-To: <45F58229.50403@redhat.com>

On Mon, Mar 12, 2007 at 12:39:05PM -0400, Alan Conway wrote:
> Matt Zimmerman wrote:
> > 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:

Thanks for sharing your experience.

> 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.

Interesting, so recording works for you?  I wonder what's different about
your setup.

> - 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.

I've no idea about this; I'm wanting to use Ekiga which has native ALSA
support.

> == 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

I believe I got the same when I tried to play a stereo stream for a test.
Since then, I've just been using mono files for testing, which works fine.

> 	# 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
> 	}

Haven't experimented with this; will see if it makes a difference.

-- 
 - mdz

-------------------------------------------------------------------------
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

  reply	other threads:[~2007-03-22  3:18 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
2007-03-22  3:18     ` Matt Zimmerman [this message]
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=20070322031835.GJ7472@alcor.net \
    --to=mdz@ubuntu.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