From: Matt C. <mat...@cs...> - 2003-10-10 01:39:31
|
On Thu, Oct 09, 2003 at 05:36:14AM -0400, Chris Gianelloni wrote: > On Wed, 2003-10-08 at 23:55, Matt Chapman wrote: > > Huh?! > > > > As far as I remember the MS RDP client uses (MS) ADPCM. I was thinking > > of pulling the code out of sox. > > Why? Why not just have sox as a requirement and pass the sounds off to > it? I think this would save some time and effort, not to mention reduce > code size since there's no duplication of code from an already working > and mature product. Just to let you know, calling to sox is exactly how > LinRDP and Winconnect do it. I'd considered this, but as far as I can tell sox doesn't work on a number of the platforms that rdesktop has been ported to (e.g. Windows, OS/2, VMS). Plus if you've got an embedded or single floppy image then you'd have to include sox as well, and sox is a no small program (230K here). It looks pretty trivial to pull adpcm.c/adpcm.h out of sox. Matt |