|
From: Jan S. <ha...@st...> - 2012-07-27 09:51:58
|
On Jul 27 08:02:25, bat guano wrote: > > ldd `which sox` > > to see what libraries your binary is actually linked against. > > The result of "ldd `which sox`" is listed below. > It shows links to libopencore-amrnb and libopencore-amrwb. So it's not linked to vo-amrwbenc, and that's why it cannot do AMRWB encoding. So that's settled. Now, why doesn;t the build system pick vo-amrwbenc up and build sox linked against it is another question. > It seems there are 5 relevant amr packages (or more). These are not 'packages', they are individual libraries. > 1 libopencore-amrnb > 2 libopencore-amrwb These two are provided by http://sourceforge.net/projects/opencore-amr/files/opencore-amr/ > 3 amrnb (from http://ftp.penguin.cz/pub/users/utx/amr/) > 4 amrwb (from http://ftp.penguin.cz/pub/users/utx/amr/) right > 5 vo-amrwbenc http://sourceforge.net/projects/opencore-amr/files/vo-amrwbenc/ > For amr-wb ENcoding amrwb or vo-amrwbenc must be used > (because libopencore-amrwb is only a DEcoder). > In file sox/src/amr-wb.c there's no instruction to use vo-amrwbenc as the amr-wb ENcoder. > The matter was discussed before ---> http://permalink.gmane.org/gmane.comp.audio.sox/4064 > It hasn't been implemented yet. Yes. It seems that sox's build system ignores the installed vo-amrwbenc. > I will continue to use FFmpeg till then. Out of curiosity: why do you need to encode into AMR? |