From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] encoding delay, librarifying a2play
Date: Mon, 29 Nov 2004 22:45:08 +0100 [thread overview]
Message-ID: <1101764708.7562.41.camel@pegasus> (raw)
In-Reply-To: <41AB9132.10609@xmission.com>
Hi Brad,
> > I propose a generic AVDTP library that will handle all AVDTP related
> > things. I checked in some basic code into the avdtp directory. My idea
> > is to make the library look like a socket interface so we can later move
> > things very easy to a kernel AVDTP implementation.
>
> ok, the avdtp skeleton gives me a good starting point
I have done some more work on it, but not yet comitted.
> > However the final goal should be an ALSA library extension like their
> > JACK plugin. But from my first tests I realized that it is impossible to
> > create such an extension outside the ALSA PCM directory. I must talk
> > with the ALSA developers about that issue.
>
> I am going to ask at alsa-devel about the userspace plugin. It's hard to
> tell what is going on in alsa-lib.
it is not that hard, because the initial stuff already works. My problem
is that we must develop inside the ALSA tree.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-11-29 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 2:24 [Bluez-devel] encoding delay, librarifying a2play Brad Midgley
2004-11-28 6:56 ` Marcel Holtmann
2004-11-29 21:14 ` Brad Midgley
2004-11-29 21:45 ` Marcel Holtmann [this message]
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=1101764708.7562.41.camel@pegasus \
--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