From: Christian Apeltauer <christian.apeltauer@online.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] bluetooth audio
Date: Tue, 26 Oct 2010 11:23:01 +0200 [thread overview]
Message-ID: <20101026112301.3373da22@gentoo.christian.ich> (raw)
In-Reply-To: <AANLkTim+NyT6E1E0_JdTTbgf7vfLNtc5+8SEQW2Zq3aS@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Am Fri, 22 Oct 2010 01:11:35 +0000
schrieb James <jtp@nc.rr.com>:
> Also, the a2dp thing has me pulling my hair out. Is the *only* way to
> use a2dp with pulseaudio? Is there no way to simply redirect all audio
> to the bluetooth headset?
>
> Anyone who can toss some experience in my direction would be greatly
> appreciated.
>
> Thanks!
> -james
>
It is possible to setup alsa using bluetooth:
Add to ~/.asoundrc (if it doesn't exist just create it)
pcm.bluetooth {
type bluetooth
device "11:22:33:44:55:66"
}
(replace 11:22:33:44:55:66 with the actual
address of the bluetooth headset). Sound can now be directed to the
headset via the alsa device "bluetooth", e.g.:
ogg123 -d alsa -o dev:bluetooth
Some GUI application doesn't show that device in their configuration
dialogue. vlc is an example of this behaviour, but it is possible to
make vlc use it by manually editing the configuration file.
You can also make the bluetooth device the standard device by
pcm.!default {
type bluetooth
device "11:22:33:44:55:66"
}
It is a long time since I made that setup, so I can't say if it will
work out of the box. But it is possible to avoid pulseaudio. I hope it
will help.
Best regards
Christian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-10-26 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 1:11 [gentoo-user] bluetooth audio James
2010-10-24 5:07 ` [gentoo-user] " James
2010-10-26 9:23 ` Christian Apeltauer [this message]
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=20101026112301.3373da22@gentoo.christian.ich \
--to=christian.apeltauer@online.de \
--cc=gentoo-user@lists.gentoo.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