There is a patch in the tracker to allow the AMR libraries to be found and loaded at runtime. If the OpenCORE libraries truly are compatible with the existing libraries, then all that would be needed would be to add the names of the OpenCORE shared libraries to the list of library names that SoX should try when searching for the library at runtime. I'll try to find an OpenCORE package and compare the function signatures.
 
The patch also removes the need to have the AMR header files present at compile time. So SoX can be built with AMR support (DL_AMR) without any AMR package present on the system at build time. At runtime, only the shared library is needed. If statically loading AMR, only the linker option (i.e. -lamrnb) would need to change to switch between the two libraries.
 
A similar approach could be taken for LAME without much effort (making it possible to build SoX with DL_LAME without needing lame.h or libmp3lame.a to be present during the build process).
 
Unfortunately, doing the same for MAD would be less practical since MAD uses a lot of macros.
On Thu, Oct 15, 2009 at 11:32 AM, Pascal Giard <evilynux@gmail.com> wrote:
Guys, on Debian (and Ubuntu i guess), OpenCORE's implementation of AMR
is now included.
I haven't done many tests, but their implementation seems compatible
with the one by Stanislav Babec.

Interestingly, it's part of main (not non-free!).
I haven't taken the time to go into the details, but it seems to me
that that implementation is no better (legal-wise) than the other one.
However, it seems like it WILL replace the other one as it has
Google's weight on its side (it's part of the Android project).

Official description from Debian:

This library contains an implementation of the 3GPP TS 26.073
specification for the Adaptive Multi Rate (AMR) speech codec. The
implementation is derived from the OpenCORE framework, part of the
Google Android project.

In any case, i thought you should know.

Cheers,

-Pascal

On Thu, Oct 15, 2009 at 11:48 AM, robs <aquegg@yahoo.co.uk> wrote:
> There's a link here:
>
> http://sox.sourceforge.net/Main/Links
>
> In fact, this is a portability wrapper around the 3GPP reference implementation so will be probably be similar to what you already have.
>
> HTH,
> Rob
>
> --- On Thu, 15/10/09, Anil Jangam <anil_jangam@persistent.co.in> wrote:
>
>> From: Anil Jangam <anil_jangam@persistent.co.in>
>> Subject: Re: [SoX-users] Division error.
>> To: "sox-users@lists.sourceforge.net" <sox-users@lists.sourceforge.net>
>> Date: Thursday, 15 October, 2009, 3:48 PM
>>
>> Hi Rob,
>>
>> Can you tell me what third part library is used to handle
>> the AMR conversion?
>>
>> /anil.
>
>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Sox-users mailing list
> Sox-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-users
>



--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel