All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SBC encoding Wav files
Date: Fri, 09 Sep 2005 16:32:44 -0600	[thread overview]
Message-ID: <43220D8C.2040103@xmission.com> (raw)
In-Reply-To: <000a01c5b571$377ba870$0201a8c0@NBVICTOR>

hey

we just have a reference encoder. use another tool to convert to .au 
first. i'm not sure it's worth the effort to add more formats to the 
encoder when it's just for development.

to reiterate: we want the encoder to work transparently as a plugin 
inside alsa. maybe i'll be able to get back to that now.

brad

Victor Shcherbatyuk wrote:
> Joe,
> 
> If .pcm works and .wav doesn't, must be something with audio parameters 
> extracted from wav header? I've never tried wav's and the earliest I can 
> is the week after the next week... May be Brad has some ideas?
> 
> Regards,
>    Victor.
> 
> ----- Original Message ----- From: "Joe Samuel" <sjoe2@yahoo.com>
> To: <Bluez-devel@lists.sourceforge.net>
> Sent: Friday, September 09, 2005 20:08
> Subject: [Bluez-devel] SBC encoding Wav files
> 
> 
>> Hi,
>> Why is the sbc code accepting only au?
>> I tried a PCM wav file, changed the endianness here:
>> for (ch = 0; ch < sbc->channels; ch++) {
>> int16_t s = *((short *)ptr);
>> ptr += 2;
>> priv->frame.pcm_sample[ch][i] = s;
>> }
>>
>> And of course, changed the header reading part; but it
>> looks like things are not as simple as that. The
>> encoded file sounds horrible (rather I would say, it
>> had nothing in it that sounds like the original).
>> Did I miss out something?
>>
>> regards,
>> Joe
>>
>>
>>
>>
>>
>>
>>
>>
>> ___________________________________________________________
>> Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with 
>> voicemail http://uk.messenger.yahoo.com
>>
>>
>> -------------------------------------------------------
>> SF.Net email is Sponsored by the Better Software Conference & EXPO
>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
>> Practices
>> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
>> & QA
>> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>> _______________________________________________
>> Bluez-devel mailing list
>> Bluez-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-devel 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-09-09 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 18:08 [Bluez-devel] SBC encoding Wav files Joe Samuel
2005-09-09 19:03 ` Victor Shcherbatyuk
2005-09-09 22:32   ` 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=43220D8C.2040103@xmission.com \
    --to=bmidgley@xmission.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 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.