From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SBC Decoder with /dev/dsp
Date: Mon, 02 May 2005 19:58:09 -0600 [thread overview]
Message-ID: <4276DAB1.1020601@xmission.com> (raw)
In-Reply-To: <1115059379.21785.147.camel@pegasus>
Marcel
> I think that we should move the complete AVDTP handling into a2dp.c and
> make a2play and a2recv only contain the soundcard/file setup and the
> main event loop.
agreed. The alsa-lib driver will be event-driven from the start, so I
will probably want to work on the alsa-lib driver next and once that's
done, I will have a better idea of how to implement the new model for
a2dp.c.
my headsets are "in the mail" so I'll be back on it soon. You had done
some avdtp alsa-lib work I think and if that's a good starting point, I
would like to work from that. If it's not fleshed out enough, I'll just
start from your rfcomm alsa-lib code.
> First question is if we ever wanna allow a2play and a2recv to output SBC
> files or should it always be a soundcard or a PCM file? If we skip that
> SBC part, we can integrate the SBC processing directly into the a2dp.c
> file and hide it. This will makes things a lot easier.
I don't think we will need the sbc streams. I don't think I'd use them
even for debugging. We will want a way to have the use of /dev/dsp be
optional (ie optionally read and write audio files) but that shouldn't
complicate things much.
Brad
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-03 1:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 12:43 [Bluez-devel] SBC Decoder with /dev/dsp Mayank Batra
2005-05-01 12:57 ` Marcel Holtmann
2005-05-01 16:40 ` Marcel Holtmann
2005-05-02 6:43 ` Brad Midgley
2005-05-02 9:56 ` Marcel Holtmann
2005-05-02 15:26 ` Brad Midgley
2005-05-02 18:42 ` Marcel Holtmann
2005-05-03 1:58 ` Brad Midgley [this message]
2005-05-03 15:46 ` Marcel Holtmann
2005-05-01 15:21 ` Henryk Plötz
2005-05-03 13:20 ` Mayank Batra
2005-05-03 17:32 ` Henryk Plötz
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 13:03 Mayank Batra
2005-05-03 13:12 Mayank Batra
2005-05-03 15:36 ` Marcel Holtmann
2005-05-08 13:17 Mayank Batra
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=4276DAB1.1020601@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