From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: a2play code that is working
Date: Tue, 26 Apr 2005 18:57:24 +0200 [thread overview]
Message-ID: <1114534644.10706.316.camel@pegasus> (raw)
In-Reply-To: <426E70F6.4060700@xmission.com>
Hi Brad,
> How about if I move the declaration for struct sbc_frame into sbc.h and
> change that last argument to sbc_encode to be an sbc_frame *
>
> We wouldn't expose the data in the private struct, but just reuse the
> struct for communicating sbc info back to the caller...
this is a bad idea, because then we can never change the internals of
the decoder/encoder. One of the goals should be to get a SBC codec that
uses only integer operation.
The sbc_struct already contains "rate" and "channels" and we should
simply add the rest of them. I was do lazy to do in the first place and
actually because I had no use for them.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-26 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <426C05D9.6090100@xmission.com>
2005-04-26 12:21 ` [Bluez-devel] Re: a2play code that is working Mayank Batra
2005-04-26 14:56 ` Marcel Holtmann
2005-04-26 16:12 ` Brad Midgley
2005-04-26 16:48 ` Brad Midgley
2005-04-26 16:57 ` Marcel Holtmann [this message]
2005-04-26 17:02 ` 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=1114534644.10706.316.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 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.