home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.compression
- Path: sparky!uunet!snorkelwacker.mit.edu!ira.uka.de!fauern!fauna!mskuhn
- From: mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn)
- Subject: Re: U-Law Encoding....HELP!!!!
- References: <1992Nov10.163040.27563@rmece49.upr.clu.edu>
- Message-ID: <BxnoxF.C72@immd4.informatik.uni-erlangen.de>
- Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
- Organization: CSD., University of Erlangen, Germany
- Date: Fri, 13 Nov 1992 13:17:38 GMT
- Lines: 30
-
- julior@rmece02.upr.clu.edu (Julio A. Rodriguez) writes:
-
- > I've been working with the program PLAY and RECORD. RECORD produces a
- >file with a .au extension and is supposse to use the U-LAW encoding method.
- >I need to decode this data to be able to process this information usign FFT.
- >If you got any ideas on how to do so please send me your ideas. Thanks.
-
- The mu-law coding method (it's the greek letter mu, not a U) is defined in
- CCITT recommendation G.711. You should find this in the CCITT Blue Book
- or CCITT Red Book (old version) in a good library or perhaps an unofficial
- version in some ftp cites.
-
- The mu-law encoding is just a table (defining a funktion) that transforms
- a linear 12-bit sample value in a 8-bit value. This is obviously a
- lossy 3:2 (= 1:(2/3)) compression method. The table comes from a
- logarithmic quantization function.
-
- The decoder has a smaller table that gives a 12 bit value for every
- of the 256 possible 8-bit input value.
-
- G.711 defines also the a-law coder.
-
- Hope this helped.
-
- Markus
-
- --
- Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
- Internet: mskuhn@immd4.informatik.uni-erlangen.de | X.500 entry available
- --- Wer, wie, was? Wieso, weshalb, warum? Wer nichts fragt bleibt dumm. ---
-