From: 1 <it.had.even@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Possible insignificant bug in pcm_bluetooth.c (bluez-utils)
Date: Sun, 06 Jan 2008 00:31:24 +1000 [thread overview]
Message-ID: <477F94BC.3040509@gmail.com> (raw)
Hello,
here is question raised while digging thru bluez-utils source.
Piece from /audio/pcm_bluetooth.c (function bluetooth_parse_config) :
if (strcmp(id, "mode") == 0) {
if (snd_config_get_string(n, &mode) < 0) {
SNDERR("Invalid type for %s", id);
return -EINVAL;
}
if (strcmp(pref, "auto") == 0) {
bt_config->channel_mode = BT_A2DP_CHANNEL_MODE_AUTO;
bt_config->has_channel_mode = 1;
} else if (strcmp(pref, "mono") == 0) {
bt_config->channel_mode = BT_A2DP_CHANNEL_MODE_MONO;
bt_config->has_channel_mode = 1;
} else if (strcmp(pref, "dual") == 0) {
bt_config->channel_mode = BT_A2DP_CHANNEL_MODE_DUAL_CHANNEL;
bt_config->has_channel_mode = 1;
} else if (strcmp(pref, "stereo") == 0) {
bt_config->channel_mode = BT_A2DP_CHANNEL_MODE_STEREO;
bt_config->has_channel_mode = 1;
} else if (strcmp(pref, "joint") == 0) {
bt_config->channel_mode = BT_A2DP_CHANNEL_MODE_JOINT_STEREO;
bt_config->has_channel_mode = 1;
}
continue;
}
if (strcmp(id, "allocation") == 0) {
if (snd_config_get_string(n, &allocation) < 0) {
SNDERR("Invalid type for %s", id);
return -EINVAL;
}
if (strcmp(pref, "auto") == 0) {
bt_config->allocation_method = BT_A2DP_ALLOCATION_AUTO;
bt_config->has_allocation_method = 1;
} else if (strcmp(pref, "loudness") == 0) {
bt_config->allocation_method = BT_A2DP_ALLOCATION_LOUDNESS;
bt_config->has_allocation_method = 1;
} else if (strcmp(pref, "snr") == 0) {
bt_config->allocation_method = BT_A2DP_ALLOCATION_SNR;
bt_config->has_allocation_method = 1;
}
continue;
}
As I understood, bt_config->channel_mode and
bt_config->allocation_method will never be set properly, because of
wrong variable in strcmp : strcmp(pref,"auto").
If I am right, there must be strcmp(mode,"auto") and
strcmp(allocation,"auto") respectively.
Further, if it is bug, it is insignificant for now the configuration of
A2DP (~/.asoundrc) is not fully implemented.
Found this in above file:
/* FIXME: this needs to be really implemented (take into account
real asoundrc settings + ALSA hw settings ) once server side sends us
more than one possible configuration */
And something else: I got choppy sound (it chops every 2 sec) when
listening my A2DP stereo headset Southwing SA505 (BT dongle ASUS WL-BTD-202,
Ubuntu Gutsy, bluez-3.24). Tried to:
- change configuration in ~/.asoundrc but unfortunately settings for
A2DP unimplemented .
- changed hcid.conf -> lm accept,master and removed lp rswitch. with no use
Anybody knows what can it be?
Now waiting for new release in hope that A2DP settings will be
implemented :)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-01-05 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 14:31 1 [this message]
2008-01-05 14:57 ` [Bluez-users] Possible insignificant bug in pcm_bluetooth.c (bluez-utils) Brad Midgley
[not found] <mailman.378267.1199593295.26582.bluez-users@lists.sourceforge.net>
2008-01-08 1:52 ` [Bluez-users] Possible insignificant bug in, " Eugene
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=477F94BC.3040509@gmail.com \
--to=it.had.even@gmail.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