From: Cyril V. <cyr...@me...> - 2004-11-15 20:51:06
|
De : mailto:st...@st... Emission : 15/11/2004 21:10:15 > Cyril VELTER wrote: > > > I have a patch for alaw support (I just reworted it from scratch, inspired by > >the ulaw codec and some sun free code). Is it possible to include this in CVS ? > >and where should I post the patch ? > > > > > > I got your patch off-list, and it's now included in CVS. I just had to > un-MSDOS-ify the files and merge new diffs. > > It compiles clean, but I haven't actually tried it, but I'm sure people > on the list will let us know how it works out.. Very nice, I just updated my local copy with cvs recompiled everthing and tested it with simpleclient/testcall (modified to force alaw usage) and it works. > > If someone wants to, you can probably make decoding much faster by > compiling a table at initialization time, and then just doing a table > lookup at run time, like we do for ulaw. There's really no downside to > this, because there are only 256 2-byte entries in the table, so it only > takes up 512 bytes. OTOH, for a client, this all doesn't make much > difference, because we're unlikely to tax anything with encoding or > decoding. > > Encoding is a bit different, because even with the method we use in > ulaw, there might still be some quantization. (and a 64K table does > take more memory, doesn't always fit in cache well, etc). You are right. I'll test to see if there is a real difference. cyril velter |