public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SBC packer done, kind of
Date: Tue, 23 Nov 2004 22:03:29 +0100	[thread overview]
Message-ID: <1101243809.27351.18.camel@pegasus> (raw)
In-Reply-To: <20041123204901.776fe240.henryk@ploetzli.ch>

Hi Henryk,

> > However it does not work as expected, but if you accept some noise you
> > will get some results. I used these commands for testing:
> 
> Yes, the values sbclib.c puts into frame.pcm_sample don't look right.

this actually reminds me again that I am not an audio expert. Can you
fix it easily?

> If you don't have any objections I'll rename sbcdec as sbcplay (that's
> more descriptive of what it does) and try to come up with an sbcenc and
> sbcdec based on the audio file library
> http://freshmeat.net/projects/audiofilelibrary

I like to keep them as sbcenc and sbcdec, because this is what they are
doing. The output to a soundcard is a nice extra feature of sbcdec and
if sbcenc can capture from a soundcard this will be also great. To have
some nice and handy names I think sbcplay and maybe sbcrec should be
symlinks to sbcdec and sbcenc. This is how this is normally done and if
we share most of the code it is also no problem to be sbcenc and sbcdec
the same program.

The choose for libao was, because mpg321 uses it and its API is very
easy. The possibility for writing to a file and playing on a soundcard
with the same set of functions was also a plus. However I don't know
what's the best audio library nowadays. So any comments about that are
welcome.

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

  reply	other threads:[~2004-11-23 21:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  0:47 [Bluez-devel] SBC packer done, kind of Henryk Plötz
2004-11-23  6:27 ` Marcel Holtmann
2004-11-23  6:48   ` Henryk Plötz
2004-11-23  9:24     ` Marcel Holtmann
2004-11-23 19:49       ` Henryk Plötz
2004-11-23 21:03         ` Marcel Holtmann [this message]
2004-11-24  3:21           ` Henryk Plötz
2004-11-24  5:01             ` Marcel Holtmann
2004-11-24  6:34               ` Marcel Holtmann
2004-11-25  4:22                 ` Marcel Holtmann
2004-11-25  5:07                 ` Henryk Plötz
2004-11-24  7:55               ` Brad Midgley
2004-11-24 14:39                 ` Marcel Holtmann
2004-11-24 17:36                   ` Brad Midgley
2004-11-24 17:44                     ` Marcel Holtmann
2004-11-24 19:33                       ` Brad Midgley
2004-11-25  6:07                         ` Marcel Holtmann
2004-11-24 20:37                   ` Henryk Plötz
2004-11-25  2:49                     ` Marcel Holtmann
2004-11-25  5:02                       ` Henryk Plötz
2004-11-25  5:30                         ` 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=1101243809.27351.18.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