Linux bluetooth development
 help / color / mirror / Atom feed
From: Mayank Batra <mayankbatra@yahoo.co.in>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SBC Decoder with /dev/dsp
Date: Tue, 3 May 2005 14:03:25 +0100 (BST)	[thread overview]
Message-ID: <20050503130325.36986.qmail@web8306.mail.in.yahoo.com> (raw)
In-Reply-To: 6667

Brad,

> Is a2snk working now then? Can I factor out the
> common stuff in 
> a2snk/a2play without messing up changes anyone is
> holding onto?

Thanks for creating a2dp.h file

And yes, now it is final that a2snk (now a2recv) is
functioning.

I have tested it by using a2play as well as BlueSoleil
as the source. And it is working perfectly alright.

But the problem is again the sequential nature of
a2recv as Marcel pointed out.

But one thing:
a2recv functions in the following scenario:

1) I use a PCM file (.snd), encoded in little-endian
format.

2) I use a2play, which encodes it into sbc.

3) I decode the sbc stream with a2recv, open my
soundcard in little-endian format (My soundcard does
not support big-endian format). But for this I have to
patch the sbc.c to produce output in little endian
format.

After the above steps output is crystal clear.
And when I say clear, it means absolutely clear.
 
> Any suggestions for the name of the new header file
> that a2snk/a2play 
> will include? avdtp.h seems like a poor choice...

a2dp.h is great.
 

Mayank

________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony


-------------------------------------------------------
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

             reply	other threads:[~2005-05-03 13:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 13:03 Mayank Batra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-08 13:17 [Bluez-devel] SBC Decoder with /dev/dsp Mayank Batra
2005-05-03 13:12 Mayank Batra
2005-05-03 15:36 ` Marcel Holtmann
2005-05-01 12:43 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
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

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=20050503130325.36986.qmail@web8306.mail.in.yahoo.com \
    --to=mayankbatra@yahoo.co.in \
    --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