public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Vasanthakumar J <j.benjamin@gdatech.co.in>
To: balaji_palaniswami@yahoo.com
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Recommended asoundrc for bluetooth headset
Date: Thu, 09 Jul 2009 20:09:57 +0530	[thread overview]
Message-ID: <4A56013D.70004@gdatech.co.in> (raw)
In-Reply-To: <6AC5A55546F64545AE996F8200E3AC4E06A50ABC@NL0105EXC01V01.eur.slb.com>

Dear Balaji,
> ----- Original Message ----
> From: John Frankish <j-frankish@slb.com>
> To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
> Sent: Thursday, 18 June, 2009 12:11:53 PM
> Subject: Recommended asoundrc for bluetooth headset
>
> Is there a recommended .asoundrc for use with a bt headset? I've seen at least three versions and would be interested to know which is the "correct" one:
>
> ------
> pcm.bluetooth {
> type bluetooth
> device "00:12:EE:A6:1D:F4"
> profile "auto"
> }
>
> ctl.bluetooth {
> type bluetooth
> }
> -----
> pcm.rawbluetooth {
>    type bluetooth
>    device 00:12:EE:A6:1D:F4
> }
>
> pcm.bluetooth {
>    type plug
>    slave {
>       pcm {
>          type bluetooth
>       }
>    }
> }
> -----
> pcm.bluetoothraw {
>    type bluetooth
>    device 00:12:EE:A6:1D:F4
>    profile auto
> }
>
> pcm.bluetooth {
>    type plug
>    slave {
>         pcm bluetoothraw
>    }
> }
> -----
> --
> John,
> Third  asoundrc is right one, this asoundrc is working for me upto bluez 4.32.
> I am upgrading kernel to 2.6.rc8, bluez 4.41  and other depnedencies whatever you mentioned.
> then i will update you result of a2dp , headset profile.Inmeanwhile please try 3rd asoundrc ,let me know your result.
>
> Thanks,
> Balaji.P
> ----
>
> Using first asoundrc
>
> $ aplay -Dbluetooth -v /usr/local/share/sounds/alsa/Noise.wav
> correct sound.
>
> $ aplay -Dplug:bluetooth -v /usr/local/share/sounds/alsa/Noise.wav
> incorrect sound.
>
> Using third asoundrc
>
> $ aplay -Dbluetooth -v /usr/local/share/sounds/alsa/Noise.wav
> incorrect sound.
>
> $ aplay -Dplug:bluetooth -v /usr/local/share/sounds/alsa/Noise.wav
> correct sound.
>
> Using first or third asoundrc
>
> $ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE
> Correct sound
>
> ..and if I could remember the aplay command switch to play an mp3, I would have tried that...
Apart from .asoundrc file what are the other configuration files that 
need to be taken care if we need to try mono and stereo headset.(HSP and 
A2DP)
What is the significance of the audio.conf file in the /etc/bluetooth? 
Whether this is required for the Bluetooth headset proper audio routing?
If you are using the audio.conf for the A2DP/HSP can you share what 
additional configurations you have made.

Also can you please share your experience with the 4.41+ on your side 
with the Bluetooth headset Mono or stereo.

Thanks & Regards,
Benjamin

  reply	other threads:[~2009-07-09 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  6:41 Recommended asoundrc for bluetooth headset John Frankish
2009-06-18  7:17 ` balaji palaniswami
2009-06-18 13:44   ` John Frankish
2009-07-09 14:39     ` Benjamin Vasanthakumar J [this message]
2009-07-12  4:18       ` John Frankish

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=4A56013D.70004@gdatech.co.in \
    --to=j.benjamin@gdatech.co.in \
    --cc=balaji_palaniswami@yahoo.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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