linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivy <ivy@cashette.com>
To: bluez-devel@lists.sourceforge.net, bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Voice setting for U-law and A-law.
Date: Sat, 24 Sep 2005 04:21:28 -0700 (PDT)	[thread overview]
Message-ID: <10232381.1127560888625.JavaMail.Administrator@appsrv> (raw)

--- Andreas Beck <becka-bzdvl@bedatec.de> wrote:
> Ivy <ivy@cashette.com> wrote:
> 
> >    xxxxxx01xxxxxxxx Input Coding: u-law 
> >    xxxxxxxx01xxxxxx Input Data Format: 2"s complement 
> > ( what is the advantage of 2's complement that 1's com ?).
> 
> Actually I don't think this makes sense for ulaw/alaw, as AFAIK these
> are always 8 bit, as they were designed for telephony channels (ISDN)
> that operate at 64kbit, thus giving 8kSamples/s at 8 bit.
> 
> The alaw/ulaw encoding gives a somewhat logarithmic scale which gives
> better dynamic range at the expense of small details the human ear
> doesn't recognize well anyway.
> 
> For linear, the difference is in the coding of negative numbers.
> 1s complement will code negative numbers as their positive equivalent 
> XOR 0xffff (i.e. a word with all-one bits). This is a rater uncommon
> coding scheme. It has the odditiy of having a +0 (0x0000) and a 
> -0 (0xffff). 2s complement will add 1 after the above step, which 
> has the advantage of simple handling of arithmetic operations with
> common ALUs designed for unsigned numbers. It just works - only thing
> you have to adjust is handling of overflow flags.
> Another advantage is a slightly increased range of values (-32768 to
> 32767 at 16 bit as compared to -32767 to 32767 at 1s complement)
> at the expense of an asymmetric value range.
> 
> >  xxxxxxxxxx1xxxxx Input Sample Size: 16 bit   (Can i use 8 bit ?) 
> 
> IMHO you should, if you want alaw/ulaw.

              You meant to use 16 Bit or 8 bit ?..

> 
> >  (what does it  mean "ONly FOR Linear PCM in Documentation ?).  
> 
> I suppose these bits get ignored for formats other than linear PCM, as
> ulaw/alaw are inherently 8 bits.

> 
> > xxxxxxxxxxx010xx # of bits padding at MSB: 2 (if i use 16 Bit, 
> > 2bit's of MSB is needed for padding, coz only 14bits are enough 
> > for u-law) 
> 
> AFAIK 8 bits are enough - could you explain?

              U-LAW takes 14bits of linear PCM data as input and generates 8 bit compressed data. Am i correct ?.. Please correct me if i m wrong !!.. Thatswhy i assume that it needs 16 bits for INPUT Sample size and 2 bit offset in MSB position. 

> 
> 
> CU, Andy

-ivy 

> 
> -- 
> = Andreas Beck                    |  Email :  <becka-sig@bedatec.de>         =
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. 
> Download it for free - -and be entered to win a 42" plasma tv or your very
> own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

__________________________
Free 3000MB email. Stops spam 100%. No banner ads. No popup ads. http://www.cashette.com


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-09-24 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 11:21 Ivy [this message]
2005-09-24 11:32 ` [Bluez-devel] Voice setting for U-law and A-law Andreas Beck
  -- strict thread matches above, loose matches on Subject: below --
2005-09-25 10:38 Ivy
2005-09-24 11:52 Ivy
2005-09-24 10:20 Ivy
2005-09-24 11:03 ` Andreas Beck
2005-09-23 14:43 Ivy
2005-09-23 14:48 ` 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=10232381.1127560888625.JavaMail.Administrator@appsrv \
    --to=ivy@cashette.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).