[Asterisk-Users] GSM compression tool

[Steven Critchfield]

On Thu, 2003-10-09 at 18:26, George Lin wrote:
> Thanks Steve.
> 
> In fact, I am looking for a ZIP tool to zip a GSM file. currently I found
> that winzip ONLY compress 10% of a WAV file.
> 
> I am wondering is there any good ZIP tool for a GSM file and or WAV file.

Don't expect to get much compression with lossless compression like zip
or any other tools like that. GSM is a lossy compression and that is the
way it gets some of the compression. GSM is probably the best you will
get for compression and still be usable on your asterisk machine. 

> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com
> [mailto:asterisk-users-admin at lists.digium.com]On Behalf Of Steven
> Critchfield
> Sent: Thursday, October 09, 2003 2:49 PM
> To: asterisk-users at lists.digium.com
> Subject: Re: [Asterisk-Users] GSM compression tool
> 
> 
> On Thu, 2003-10-09 at 15:51, George Lin wrote:
> > Hi list,
> >
> > Can anyone suggest us what kind compression tool is best to compress a GSM
> > file.
> >
> > And what kind compression ratio can be?
> 
> This is a hard message to write with out unleashing the flame thrower.
> 
> On this list it has been discussed many times that you can use sox or
> toast to convert to GSM.
> 
> At least you should have issued a apropos gsm on the command line, or
> even a man -k gsm. That alone would have pointed you to toast.
> 
> A little study of GSM information tells you that the codec produces 32.5
> bytes of data per 20ms. So compression ratio depends on the format it
> was in to begin with. Generally speaking though, you should be working
> with 8k samples a second and therefore 20ms is 160 samples. You may even
> be using 8bit samples like everything else is. At this point 160 samples
> is 160 bytes that gets compressed to 32.5 bytes. On computer platforms,
> it is a pain to deal with half bytes. So on a unix system, it has been
> standardized that 32.5 will be null padded to 33 bytes even. On Crapdos,
> they decided that this is one of the few places they would try not to
> bloat. On Crapdos, they take 2 32.5 byte frames and bit shift the second
> down into the empty half left by the first frame and produce a 65 byte
> double frame.
> 
> Oddly enough, the majority of this is all learned from reading the
> source code readily available already in the asterisk code base. It
> possibly could be even more easily been found by a simple google search.
> 
> At the minimum, please go here and read for the next 10 or so minutes.
> http://kbs.cs.tu-berlin.de/~jutta/toast.html
> --
> Steven Critchfield  <critch at basesys.com>
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
-- 
Steven Critchfield <critch at basesys.com>