Audacity can't find ffmpeg and lame files

[anette]

Hello everyone,
I'm working with itunes m4a files (voice memos), but they won't export. It did work fine after downloading the files on my mac mini, but I'm trying to install them on the laptop. They have the same operating system: Snow Leopard 10.6.4. However, after trying 11 times (yes, 11!) Audacity can't find them despite the messages saying they were successfully installed. I have tried 'locate' and 'browse'. All the info I've found says they are in usrs/local/library/audacity. I haven't got that on EITHER Mac - only me as the user and 'public', which has nothing in it - but it worked ok on the Mini. I've hunted through the entire library and can't find them.
Desperation is setting in - this is for work. So, any advice or suggestions will be very gratefully received.
Cheers
Anette

[billw58]

Start by downloading the FFmpeg installer from this page: http://manual.audacityteam.org/index.ph ... tallffmpeg

The installer will put the FFmpeg libraries in the standard location, and Audacity should find them immediately.

The "usr" directory is hidden on Mac. You shouldn't really need to go there, but if you want to check it out ...

- in the Finder, click on the Go menu, then "Go to folder" and type "/usr/local/lib" in the dialog (without the quotes, of course). Insider the "lib" folder you will see the "audacity" folder. Inside that there should be six or seven files:
libmp3lame.dylib
libavcodec.52.dylib
libavcodec.dylib
libavformat.52.dylib
libavformat.dylib
libavutil.50.dylib
libavutil.dylib

In Audacity > Preferences, the Libraries section, if you click the "Browse" button to find the FFmpeg libraries the same thing happens - you can't see the "usr" directory or anything inside it. You need to type "/usr/local/lib/audacity/" into that dialog instead of using the "Browse" button, and Audacity will find the FFmpeg libraries if they are installed there.

All the info I've found says they are in usrs/local/library/audacity

Note that is is "usr" not "usrs" in the file path.

-- Bill

[anette]

Hi Bill,
Thanks again! I'll see if they're there. I really don't understand why Audacity has failed to find the ones installed. I feel a bit like a detective ...
Cheers for now. ANd, if this is the last post before the holidays, I hope you enjoy them.
Anette

[anette]

Hi (once again)
I've just tried the 'go to' the folder. It says I don't have permission to view its contents. I'm the owner AND administrator!
Any suggestions? Because it's 'hidden', I don't know how to change the permissions.
Cheers
Anette

[anette]

Hi
FFMPEG SUCCESS!!!!!!
I found out how to show hidden files (via Terminal). They weren't in there. So I gave myself permissions. Removed all that I could find of the previous downloads (many bits and pieces must still be lurking somewhere!) Then I downloaded again, and it works, at least with the FFmpeg. I haven't tried Lame MP3 yet but now I'm very hopeful.
So, many many thanks Bill for all your effort - and happy holidays!
Cheers
Anette
Now I must just remember to 'hide' everything again.

[Chief_Engineer]

This was driving me NUTS trying to correct this on a machine after software was re-installed when its boot sector became corrupt, and this thread inspired me to press on. Here's my HOW TO document to fix what I found:

Problem: No matter how many times one tries installations or re-downloads, FFMPEG cannot be located by Audacity.

Reason: FFMPEG really wants to be loaded in a specific place, namely, the /usr/local/lib/audacity/ folder – and Audacity may not “see” the .dylib file even if you install and can find the file in an alternative location! Be aware the /usr folder is a hidden folder so one can’t normally see it in FINDER, and the /usr/local/lib/ folder may have its permissions restricted, even to an administrator, depending on the original setup. If you can’t write to the folder, you can’t install FFMPEG. Even if the admin can write to and install FFMPEG, the individual users must be able to read the folder.

Solution: Open up FINDER. Select GO on the top menu bar, then GO TO FOLDER. Type in /usr/ and hit RETURN. You should see the usr folder, but it may be greyed out (meaning it is normally hidden). Change FINDER’s display so you see columns. Click on usr: you should now see its subfolders, including /local. Click on its subfolders, and you should now see lib. If it has a red circle with a minus sign in it, you do not have permission to see the contents of that folder. Click on the lib folder to highlight it, the click on the drop down menu under settings and select GET INFO.

Another window pops up with all kinds of information about the lib folder. If necessary, click on the triangle in front of Sharing and Permissions. It now lists those that have select permissions to see this folder. The administrator should be able to “read and write;” everyone should be able to “read only.” To change this setting, click on the padlock symbol to unlock it. Now highlight the user name you wish to change, then select the proper permission by clicking on the drop-down choices by the current permission. After changing the permission(s), you MUST click on the drop-down menu next to the gear icon at the bottom of the window and select to SAVE or APPLY the settings. Click on the padlock symbol to lock the permissions and close the window.

Now that you’ve done this, install the FFMPEG from the download. If you look in FINDER, it will created a folder called Audacity in the /usr/local/lib/ path. The administrator can now check to see if Audacity can locate FFMPEG by going to the Audacity ⇒ Preferences ⇒ Libraries menu.

Now check to verify that a non-administrator user can set their preferences to locate FFMPEG. If so, you’re good to go!

[kozikowski]

I'm wondering if a non-administrator user can install lame and FFMpeg at all. It's not normal for you to have to go through all that grief to get lame and FFMpeg working. That's one reason they come with an installer instead of just dumping the files in your lap like what used to happen.

I think I just answered my own question. The installer makes an administrator log in before it succeeds. So there's something very strange with those two accounts to allow damage like that.

Did anybody go through and "Repair Permissions?"

Koz

[anette]

Hi Koz,
Sorry for the delay in replying.
Yes, I tried that first, but it didn't work. It does seem that you do have to do quite a bit of work to get them up and running.

[vinylivo]

This was driving me NUTS trying to correct this on a machine after software was re-installed when its boot sector became corrupt, and this thread inspired me to press on. Here's my HOW TO document to fix what I found:

Problem: No matter how many times one tries installations or re-downloads, FFMPEG cannot be located by Audacity.

Solution: Open up FINDER. Select GO on the top menu bar, then GO TO FOLDER. Type in /usr/ and hit RETURN. You should see the usr folder, but it may be greyed out (meaning it is normally hidden). Change FINDER’s display so you see columns. Click on usr: you should now see its subfolders, including /local. Click on its subfolders, and you should now see lib. If it has a red circle with a minus sign in it, you do not have permission to see the contents of that folder. Click on the lib folder to highlight it, the click on the drop down menu under settings and select GET INFO.

Another window pops up with all kinds of information about the lib folder. If necessary, click on the triangle in front of Sharing and Permissions. It now lists those that have select permissions to see this folder. The administrator should be able to “read and write;” everyone should be able to “read only.” To change this setting, click on the padlock symbol to unlock it. Now highlight the user name you wish to change, then select the proper permission by clicking on the drop-down choices by the current permission. After changing the permission(s), you MUST click on the drop-down menu next to the gear icon at the bottom of the window and select to SAVE or APPLY the settings. Click on the padlock symbol to lock the permissions and close the window.

Hi, by the way I had a similar problem with the ffmpeg library.
there was previous installation from an older version audacity version (2.x) and the new package installer just didn't update the older library. and new audacity just didn't work with the old library, even it was called 'libavcodec' etc as well. because the installer didn't show the version I didn't know what the problem was and was unaware that the new versions are called 'libavcodec.52.dylib', 'libavformat.52.dylib' and 'libavutil.50.dylib'. the older versions were something like .51.dylib and .49.dylib.
I was just realising this by 'installing' it the hard way. A finder search for 'libavcoded' (including system files) revealed the location mentioned, so I could open that folder. then I opend the installer package by 'show package contents' (or something similar as I'm on a german OSX) and navigated thru the files for finally finding the ffmpeg codec files. then I copied the files manually (via drag & drop) to the correct locations. of course before copying the finder asked me to type in my admin pwd because of the restricted access. after doing so the files finally landed where they belonged and luckily after a new start of audacity 1.3.12 they were recognized!

this is probably not the way an installer should be used, but for me it was the only way I managed to store the codec files in the correct location. now all ffmpeg related problems are gone and it works fine.

normally I don't need this codec, but to simplify things I wanted to import wavepack files (from my iRiver, lossless rockbox recording) directly to avoid converting the files with another tool (XLD) before.

audacity is really cool and I especially love the rms-view in the waveform display. this helps alot. thanxs & respect
jvo

[kozikowski]

Do you two that have the pages and pages of problems have two or more users on your machine? It's possible if you have an actual "administrator" user on your machine in addition to you, this install won't work.

I'm trying this out on the Snow Leopard machines at work.

Koz