Linux bluetooth development
 help / color / mirror / Atom feed
From: Alan Conway <aconway@redhat.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Headsetd, skype and bluetooth headsets.
Date: Thu, 08 Mar 2007 03:05:27 -0500	[thread overview]
Message-ID: <45EFC3C7.2060802@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]

Trying to get a plantronics 510s headset working with skype (among other 
things) and I'm tantalizingly close. Hopefully someone can help close 
the gap.

I go the headset working for input and output with headsetd and headset 
plug-in: aplay and arecord -D headset working A-OK - my .asoundrc 
attached. Then I tried aoss skype - it *almost* worked. I could hear OK 
thru the headset but my voice was weirdly distorted and unrecognizable. 
I decided to recompile off the CVS head and now nothing works I get
  ALSA lib pcm_sco.c:532:(_snd_pcm_sco_open) Unknown field max_periods

Probably I have some mish-mash of versions installed, it's too late at 
night.

So what I'd like to know to speed my quest tomorrow:
 * In CVS there are multiple headsetd and alsa-plugins under plugz, 
btsco and alsa-plugin-sco. Which is the right one?
 * Maybe the distortion indicates some transformation of sound formats 
is needed - any hints as to what it might be?
 * Is there a better way than aoss for skype? It only shows alsa 
hardware devices in it's menus, I haven't found a way to make it use a PCM.
 * Any other  tips on what might be going wrong, or better ways to 
approach this?

I'll be happy to post my solution to the list if that's useful.

Thanks,
Alan.

[-- Attachment #2: .asoundrc --]
[-- Type: text/plain, Size: 1106 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 345 bytes --]

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

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-03-08  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  8:05 Alan Conway [this message]
2007-03-08 20:25 ` [Bluez-users] Headsetd, skype and bluetooth headsets Gerhard Killesreiter
2007-03-09  3:01 ` Alan Conway
  -- strict thread matches above, loose matches on Subject: below --
2007-04-26 17:41 Ma Begaj

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=45EFC3C7.2060802@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