From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] exports for pulseaudio
Date: Mon, 28 Apr 2008 14:46:09 -0600 [thread overview]
Message-ID: <d89ddf300804281346y5b8d41bav944ae3d32aba376@mail.gmail.com> (raw)
In-Reply-To: <1209405939.17679.157.camel@violet.holtmann.net>
Marcel
> have ipc.[ch] and these files have LGPL license so they can be copied
> out of the side bluez-utils source code and used by other libraries or
> systems. Nothing has changed here. It is the job of the external plugin
> developers to keep this in sync with bluez-utils. No API guarantee.
ok
> For SBC the same thing applies at the moment.
fortunately the codec is self-contained so api breakage won't occur.
Quality or speed improvements might need to get synchronized from time
to time.
There is one fix in the quality of the internal sbc codec that I
should push into the old libsbc, assuming we don't just kill off the
standalone libsbc altogether.
--
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-04-28 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 20:37 [Bluez-devel] exports for pulseaudio Brad Midgley
2008-04-28 18:05 ` Marcel Holtmann
2008-04-28 20:46 ` Brad Midgley [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=d89ddf300804281346y5b8d41bav944ae3d32aba376@mail.gmail.com \
--to=bmidgley@gmail.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