Page 1 of 3

Audacity and FFMPEG on Mac

Posted: Sat Nov 15, 2008 12:36 am
by zerolight
Hi,

I've compiled and installed FFMPEG on my Intel iMac. When I try to config Audacity to use it, it asks for the location of the avformat-52.dll. Anyone have any clue where that is? I'm going mad trying to find it.

Thanks.

Graham

Re: Audacity and FFMPEG on Mac

Posted: Sat Nov 15, 2008 1:57 am
by kozikowski
<<<anyone have any clue where that is?>>>

On a PC? a DLL is a Dynamic Link Library which is a Microsoft Windows information file. That's not to say that other programs can't use them, but I'd be surprised.

So wires got crossed somewhere.

Koz

Re: Audacity and FFMPEG on Mac

Posted: Sat Nov 15, 2008 7:10 am
by zerolight
On a Mac...

Does ffmpeg feature not work on Mac?

Posted: Sun Nov 16, 2008 12:05 am
by sfatula
I asks in preferences for a location for avformat.dll, of course, there are no dll's. So, put in the location for libavformat.a, and, it doesn't recognize it.

Seems like Audacity is only set up for Windows???

Re: Audacity and FFMPEG on Mac

Posted: Sun Nov 16, 2008 1:01 am
by kozikowski
<<<On a Mac...>>>

Oh, I believe you. But it's still a Windows file. Audacity can't find it and you won't be able to find it, either.

Search this page for that filename...

http://www.gooli.org/blog/building-ffmp ... and-mingw/

Koz

Re: Does ffmpeg feature not work on Mac?

Posted: Sun Nov 16, 2008 1:07 am
by kozikowski
Someone else posted this in another segment of the forum. I have no idea why it's doing this...

http://audacityteam.org/forum/viewtopic ... 231#p28537

Koz

Re: Audacity and FFMPEG on Mac

Posted: Sun Nov 16, 2008 2:25 am
by sfatula
It is named something else on a Mac, it is most likely a bug or feature of Audacity. ffmpeg, of course, runs fine on Mac as does libavformat.

Re: Does ffmpeg feature not work on Mac?

Posted: Tue Nov 18, 2008 9:25 pm
by steve
the ffmpeg feature is new to Audacity 1.3.6
I've not got it to work on Linux yet either. There is certainly some problems with it since Linux doesn't use dll's either.

Re: Does ffmpeg feature not work on Mac?

Posted: Wed Nov 19, 2008 10:28 pm
by Gale Andrews
We've changed the filters in source code so that on Mac, the file filter looks for the correct libavformat.*.dylib, so correctly asks to be directed to "libavformat.52.dylib". Similarly on Linux, the Audacity filter is now "libavformat.so". Those filters should now be correct in the nightly Mac build of 19 November2008, but I don't know if that build is FFmpeg-enabled (I believe so but have not been able to find out). "FFmpeg-enabled" means that when you export you will see "Save-as types" for WMA, AC3 and so on. Would someone on Mac be able to confirm that?

Audacity does now build on Mac --with -ffmpeg=system, if FFmpeg libraries are properly installed in the system, and does detect the libraries if FFmpeg is fully built from the FFmpeg source code:
http://n2.nabble.com/FFMpeg-in-1.3.6-Ma ... 19110.html

What we don't have yet is a packaged binary of FFmpeg that Mac users can download.

Similarly, FFmpeg does work on Linux using these instructions (scroll down), though everyone I know has similarly built FFmpeg from source as a system library. I don't know of a prebuilt .so binary for FFmpeg. If someone does, please let me know.

I'll merge
http://audacityteam.org/forum/viewtopic ... 231#p28537

into here.

P.S. Even if the filters are wrong, if the library you're selecting really is compatible, then you should be able to select it and have it work using the "All Files" filter. For example I'm running the FFmpeg .dll on Windows now, named with .dylib extension.




Gale

Re: Does ffmpeg feature not work on Mac?

Posted: Fri Nov 21, 2008 8:51 pm
by foobar
This is painful. First I grabbed the binary of FFmpegX, but it doesn't have libraries. Then I built the libraries from MPlayerHQ, but it doesn't have avformat. Finally I built FFmpeg from the export snapshot at ffmpeg.org. It installed avformat version 52, but as the static library libavformat.a instead of *.dylib, and Audacity won't link to that.

So if someone who succeeded at getting m4a support into Audacity could post a step-by-step of what they did, it would be greatly appreciated.

UPDATE: OK, I found one code repository that definitely contains libavformat.52.dylib: the ffmpeg package in Fink. However, in order to install it, Fink requires that I also install the following dependencies:

a52dec a52dec-dev a52dec-shlibs amrnb amrnb-dev amrnb-shlibs appleotffonts applesystemfonts atk1 atk1-shlibs audiofile audiofile-bin audiofile-shlibs autoconf automake1.9 cairo cairo-shlibs daemonic docbook-dsssl-nwalsh docbook-dtd docbook-utils docbook-xsl esound esound-bin esound-common esound-shlibs faac faac-dev faac-shlibs faad fondu fontconfig2-dev fontconfig2-shlibs freeglut freeglut-shlibs gd2 gd2-shlibs gdbm3 gdbm3-shlibs gettext-dev ghostscript ghostscript-fonts glitz glitz-shlibs gsm gtk+ gtk+-data gtk+-shlibs gtk+2 gtk+2-dev gtk+2-shlibs gtk-doc id3lib4-dev id3lib4-shlibs imlib2 imlib2-shlibs jadetex lame-dev libavcodec51-shlibs libavutil49-shlibs libdatrie libdatrie-shlibs libfaad1-dev libfaad1-shlibs libgnugetopt libgnugetopt-shlibs libid3tag libid3tag-shlibs libjasper.1 libjasper.1-shlibs libkpathsea4 libkpathsea4-shlibs libmikmod3 libmikmod3-shlibs libmp4v21-shlibs libogg libogg-shlibs librarian.08-shlibs libthai libthai-dev libthai-shlibs libtheora0 libtheora0-shlibs libtheoradec1-shlibs libtheoraenc1-shlibs libtool14 libtool14-shlibs libvorbis0 libvorbis0-shlibs libwww libwww-bin libwww-shlibs libx264-57-shlibs libx264-dev libxml libxml-shlibs libxslt libxslt-bin libxslt-shlibs lynx m4 nkf openjade openmotif3 openmotif3-shlibs opensp4 opensp4-dev opensp4-shlibs pango1-xft2-ft219 pango1-xft2-ft219-dev pango1-xft2-ft219-shlibs pixman pixman-shlibs ptex-base ptex-texmf ptexenc ptexenc-shlibs rarian rarian-compat sdl sdl-shlibs sgml-entities-iso8879 sgmls-pm system-openssl-dev t1lib5-x11 t1lib5-x11-shlibs tetex-texmf texi2html texinfo xfontpath xft2-dev xinitrc xmkmf xmms xmms-bin xmms-shlibs xvidcore xvidcore-shlibs

That's a whole lot of gigabytes and an unknown (large) number of compile hours, just to get one freaking library. There's got to be a better way to do this.