From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] What endian type is supported by audio device ?
Date: Thu, 05 May 2005 15:05:31 +0200 [thread overview]
Message-ID: <1115298331.8496.149.camel@pegasus> (raw)
In-Reply-To: <20050505123708.92329.qmail@web8307.mail.in.yahoo.com>
Hi Mayank,
> > I think that if you use ALSA it can change the
> > endian format on demand
> > inside the library, but for the a2play and a2recv
> > with OSS support we
> > can do that inside our own code. It is only byte
> > swapping. And from my
> > understand it should be done inside the SBC codec.
> > We simpy tell it what
> > input or output endian format we expect and then it
> > should obey to it.
>
> But this means that we will have to add a flag bit to
> indicate the endian type.
>
> This is ok between a2play and a2recv. But do you mean
> that we are gonna be limited to these two applications
> only?
>
> For instance, I tested a2recv with BlueSoleil and it
> was working perfectly alright, i.e. if I opened the
> audio device in little-endian format, did the byte
> swapping in sbc.c file.
>
> But we can't reprogram a third party s/w to incoporate
> a bit for endian type.
actually I have no idea what problem do you see here. We have a PCM
stream in big endian or little endian and we tell our SBC encode what
this endian format is. On the decoding side we tell it what endian
format we gonna need for the PCM stream it is creating. That's it. So
why should we worry about third party software. They can choose and if
they wanna use the SBC library they have to do it our way.
Regards
Marcel
-------------------------------------------------------
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-05 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 12:37 [Bluez-devel] What endian type is supported by audio device ? Mayank Batra
2005-05-05 13:05 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 13:28 Mayank Batra
2005-05-03 15:33 ` Marcel Holtmann
2005-05-01 12:22 Mayank Batra
2005-05-01 12:49 ` Marcel Holtmann
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=1115298331.8496.149.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.