From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Setting of bluetooth address in asoundrc
Date: Mon, 18 Dec 2006 13:51:53 -0700 [thread overview]
Message-ID: <4586FF69.6010202@xmission.com> (raw)
In-Reply-To: <24a5055d0612180213j56a6a7d1s832c981bb93d4a26@mail.gmail.com>
Rahul
> i would like to know whether is it possible to automatically set
> bluetooth address in .asoundrc. Is there a way to set bluetooth address
> in .asoundrc from outside. (eg. exporting a global variable). The reason
> for this is that i have two bluetooth headsets. On switching the headset
> i have to again edit the .asoundrc file. Instead if i can update the
> .asoundrc from outside, i guess i could just write a script which finds
> bluetooth address and sets it. but is this possible ??
I feel your pain. Yes, I think it would be scriptable. If it's a2dp
you're using, the daemon can re-read the config on the fly but sco stuff
will require a client restart.
The plan of course is to have a proper gui (the "audio routing gui" in
http://bluetooth-alsa.sourceforge.net/future.html fwiw). I've been
tinkering with pulseaudio to see how things might fit together.
Brad
-------------------------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-18 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 10:13 [Bluez-devel] Setting of bluetooth address in asoundrc Rahul Tank
2006-12-18 20:51 ` Brad Midgley [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=4586FF69.6010202@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.