From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] alsa plugin progress
Date: Thu, 26 Jan 2006 11:13:03 +0100 [thread overview]
Message-ID: <1138270383.5901.25.camel@localhost> (raw)
In-Reply-To: <43D7270C.5020805@xmission.com>
Hi Brad,
> 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.
it was working somehow and sometimes I totally messed it up. The ALSA
plugins are really designed for sound cards and for some options I
actually have no idea how to translate them correctly into A2DP. Maybe
you should simply play with different options and then might ask the
gurus from the ALSA mailing list.
Regards
Marcel
-------------------------------------------------------
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 prev parent reply other threads:[~2006-01-26 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 7:21 [Bluez-devel] alsa plugin progress Brad Midgley
2006-01-26 10:13 ` Marcel Holtmann [this message]
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=1138270383.5901.25.camel@localhost \
--to=marcel@holtmann.org \
--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).