From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] A2DP alsa no sound
Date: Mon, 27 Feb 2006 01:28:02 -0700 [thread overview]
Message-ID: <4402B812.40204@xmission.com> (raw)
In-Reply-To: <4400F1DE.5070804@cs.bgu.ac.il>
Niv
> I am attaching the whole diff between the mpg123 pipe to a2play that
> works and the dump from xmms that doesnt.
> also attaching the xmms output (23M open)
> 11c11
> < L2CAP(s): Connect req: psm 1 scid 0x0040
> ---
>
>> L2CAP(s): Connect req: psm 25 scid 0x0040
I haven't been able to dig in but something looks wrong already... isn't
the correct code going to connect on psm 25 first for the commands and
then on the detected psm (usually 1) later for the stream? Yet from what
you've sent it looks like the working version connects to psm 1 first?
If I read your diff wrong, then maybe it's just that the plugin
incorrectly tries to go right to streaming without setting it up
properly using the l2cap connection on psm 25.
Brad
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-02-27 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 16:22 [Bluez-users] A2DP alsa no sound Niv
2006-02-23 18:17 ` Brad Midgley
2006-02-25 23:59 ` Niv
[not found] ` <4400F1DE.5070804@cs.bgu.ac.il>
2006-02-27 8:28 ` Brad Midgley [this message]
2006-03-03 2:54 ` Niv
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=4402B812.40204@xmission.com \
--to=bmidgley@xmission.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;
as well as URLs for NNTP newsgroup(s).