From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] alsa plugin progress
Date: Wed, 25 Jan 2006 00:21:48 -0700 [thread overview]
Message-ID: <43D7270C.5020805@xmission.com> (raw)
Marcel,
I've been tweaking the alsa plugin. How close was it when you had it?
For now, I am setting the socket to nonblocking and polling until the
connect succeeds (I keep trying when errno is EAGAIN). I can connect and
things seem to be working but there is no audio. It looks like there's a
mismatch with audio settings but I'm not sure where that's happening.
Brad
DEBUG: _snd_pcm_a2dp_open: name pcm.headphone mode 0
DEBUG: _snd_pcm_a2dp_open: bdaddr/dest is 00:08:F4:46:03:1C
DEBUG: a2dp_alloc: init
DEBUG: a2dp_connect: a2dp 0x805ac80
DEBUG: connect_l2cap: Can't connect to 1C:03:46:F4:08:00 on psm 25.
Resource temporarily unavailable(11)
DEBUG: connect_l2cap: Can't connect to 1C:03:46:F4:08:00 on psm 25.
Resource temporarily unavailable(11)
DEBUG: connect_l2cap: Can't connect to 1C:03:46:F4:08:00 on psm 25.
Resource temporarily unavailable(11)
DEBUG: connect_l2cap: Connected [imtu 672, omtu 672, flush_to 65535]
DEBUG: connect_stream: Sent the Stream End Point Discovery Command
DEBUG: connect_stream: retrying discover response read...
DEBUG: connect_stream: Got a Stream End Point Discovery Response
DEBUG: connect_stream: received 1 capabilities
DEBUG: process_seid: SEID = 1
DEBUG: process_seid: Requested Capabilities for SEID = 1
DEBUG: process_seid: Got capabilities response
DEBUG: process_seid: headset does not support this channel mode
DEBUG: process_seid: headset does not support this frequency
DEBUG: process_seid: headset does not support this allocation_method
DEBUG: process_seid: headset does not support this subbands setting
DEBUG: process_seid: Sent set configurations command
DEBUG: process_seid: Set configurations command rejected
DEBUG: process_seid: Sent open stream command
DEBUG: process_seid: Got open stream confirm
DEBUG: connect_l2cap: Can't connect to 1C:03:46:F4:08:00 on psm 25.
Resource temporarily unavailable(11)
DEBUG: connect_l2cap: Connected [imtu 672, omtu 0, flush_to 65535]
DEBUG: connect_stream: Sent stream start
DEBUG: connect_stream: Got start stream confirm
DEBUG: a2dp_constraint: a2dp 0x805ac80
Playing WAVE '/usr/lib/openoffice2/share/gallery/sounds/pluck.wav' :
Signed 16 bit Little Endian, Rate 11025 Hz, Mono
Warning: rate is not accurate (requested = 11025Hz, got = 44100Hz)
please, try the plug plugin (-Dplug:pcm.headphone)
DEBUG: a2dp_params: a2dp 0x805ac80
DEBUG: a2dp_params: format S16_LE rate 44100 channels 1
DEBUG: a2dp_params: frame_bytes 2 period_bytes 8192 period_size 4096
buffer_size 8192
DEBUG: a2dp_prepare: a2dp 0x805ac80
DEBUG: a2dp_drain: a2dp 0x805ac80
DEBUG: a2dp_stop: a2dp 0x805ac80
DEBUG: a2dp_stop: a2dp 0x805ac80
DEBUG: a2dp_close: a2dp 0x805ac80
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-01-25 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 7:21 Brad Midgley [this message]
2006-01-26 10:13 ` [Bluez-devel] alsa plugin progress Marcel Holtmann
2006-01-26 15:32 ` Brad Midgley
2006-01-26 17:39 ` Brad Midgley
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=43D7270C.5020805@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).