From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] A2DP and Alsa Plugin
Date: Wed, 17 May 2006 10:40:41 -0700 [thread overview]
Message-ID: <446B6019.9030806@xmission.com> (raw)
In-Reply-To: <446B54AF.5040302@palmsource.com>
Frédéric
> How about a daemon that uses gstreamer with one or more ipc gstreamer
> source, a mixmatrix, volume control (if not done by mixmatrix),
> (alsa sink or (sbcfilter and a2dp sink)) to finish... An alsa plugin
> and/or a gstreamer ipc plugin would just send ipc to the daemon.
I will ask on the gstreamer list. When reading the gstreamer docs it
seems like the "sky's the limit." I wish I could understand the
limitations better.
> Why not sharing code between a2play and alsa-plugin? There are some
> variables that are shared among instances (bufe,lenbufe,tsend,...)
> why are they globals? There is a snd_pcm_a2dp_t structure that would
> (IMHO) embed them very well. Is this alsa related limitation? This
> forbid using multiple headsets at a time...
Marcel wanted to leave this stuff out of bluez for now but avrcp/a2dp
signaling would best fit there if they are to be shared.
alsa-plugin is a little messier than our typical bluetooth-alsa
component. yes, a bunch of those should not be global variables and some
further cleanup is in line. An even bigger problem is we essentially
ignore the return value from write(). I want to figure out how things
can fail there and what we should do to recover.
> Now that cvs works, how to propose patches? on the list? By creating
> a sf developper account?
please submit patches here to the list for now.
brad
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&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-05-17 17:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 9:15 [Bluez-devel] A2DP and Alsa Plugin Frederic Dalleau
2006-05-12 17:10 ` Brad Midgley
2006-05-17 16:51 ` Frédéric DALLEAU
2006-05-17 17:40 ` Brad Midgley [this message]
2006-05-29 7:02 ` Brad Midgley
2006-05-30 10:20 ` Frédéric DALLEAU
2006-05-30 16:38 ` Brad Midgley
2006-05-30 20:28 ` Brad Midgley
2006-08-02 14:08 ` Brad Midgley
2006-08-02 14:54 ` Frédéric DALLEAU
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 8:17 Frederic Dalleau
2006-05-10 17:49 ` Brad Midgley
2006-05-05 12:38 Frederic Dalleau
2006-05-05 17:24 ` Brad Midgley
2006-05-04 15:58 Frederic Dalleau
2006-05-04 17:19 ` Brad Midgley
2006-05-04 15:34 Frederic Dalleau
2006-05-04 13:30 Frederic Dalleau
2006-05-04 14:36 ` Brad Midgley
2006-05-04 14:50 ` Brad Midgley
2006-05-04 15:20 ` 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=446B6019.9030806@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.