Audacity Forum

rezha wrote:Omg i downloaded your installer, tried to do everything, edited by hand your .cfg, and still i get "not found" without any error or clue about what is wrong. Moved everything everywhere, changed permissions... it just does not work. You should really edit the wiki at least, it would save other people's hours until you make it working. Btw, ~/Library/Application Support is the right folder, i can't see why you should tamper with system directories to install a sound editor.

Well... it work out-of-the-box with me...

Maybe you can give us some more info about your system?

OS-X version, Audacity version, Lame and FFMpeg versions, where you download it from...

@rezha. You can get the latest FFmpeg 0.6.2 as a zip and install it where you like. Not sure if you got 0.6.2 or not. The older FFmpeg 0.5 installer was called "FFmpeg_Libraries_for_Audacity_on_OSX.dmg". The newer FFmpeg is sometimes detected when the old one isn't - we don't know why. Use Audacity 1.3.13 and trash the old FFmpeg libraries if you install the new ones.

Or are you taking about LAME as well?

If FFmpeg 0.6.2 (or LAME) is not detected in 1.3.13 when you locate it in the Audacity Libraries preferences, click Help > Show Log and paste the log contents here. Also say which version of OS X.

@Bruno/Bill, does the new FFmpeg 0.6.2 installer offer /Library/Application Support/audacity/libs ? I have a feeling we didn't change it this time around because we haven't updated the LAME installer which still uses /usr/local/lib.



Gale

Gale, I haven't "upgraded" ffmpeg libs yet... I'm still using 5.2, which is located in /usr/local/lib/

I think I haven't yet imported/exported anything in the Mac since I installed 1.3.13, but it still detects the ffmpeg libs successfully...

Shall I upgrade ffmpeg and lame?

Gale Andrews wrote: @Bruno/Bill, does the new FFmpeg 0.6.2 installer offer /Library/Application Support/audacity/libs ? I have a feeling we didn't change it this time around because we haven't updated the LAME installer which still uses /usr/local/lib.

Gale:
This is a mess, and it is no wonder people can't find the FFmpeg libraries. I've sent you an email with log contents.

In summary, the current FFmpeg installer installs to the wrong location, and even if the user finds where it is installed, loading of the libraries fails unless they are installed to /usr/local/lib .

-- Bill

@Bruno
It would be interesting for you to try to install the latest FFmpeg libraries, then see if you can find and load them. I just tried it and it appears that the installer's default location is "/~/Library/Application Support/audacity". That is not a typo. On my machine at least it creates a new folder at the root level of the startup disk called "~" then creates folders inside that then installs the FFmpeg libraries in there. Even if you find them, they still fail to load.

If you try this be sure to delete the current FFmpeg libraries from /usr/local/lib - Audacity will fall back on those if loading from other locations fails, and you'll get a "false positive" in the Libraries Preferences that the libraries were successfully loaded. The only indication of the failure will be that the old version numbers will still be there.

I'm going to do more work on this in a while, installing from the zip to arbitrary locations on my computer.

-- Bill

billw58 wrote:I just tried it and it appears that the installer's default location is "/~/Library/Application Support/audacity". That is not a typo.

That sounds like a bug... There shouldn't be a leading slash in the path... If ~ was still expanded that wouldn't be a problem, but with the leading / then the ~ doesn't get expanded and is treated like a normal character... This is true for both Mac and Linux (and probably to any *nix).

I'll give it a shot and see what I get...

I downloaded the installer from audacity's download page and run it accepting all the defaults... Now I have a folder named '~' in my root... Sounds like a bug to me and one that should be fixed quickly...

billw58 wrote:@Bruno
It would be interesting for you to try to install the latest FFmpeg libraries, then see if you can find and load them. I just tried it and it appears that the installer's default location is "/~/Library/Application Support/audacity". That is not a typo. On my machine at least it creates a new folder at the root level of the startup disk called "~" then creates folders inside that then installs the FFmpeg libraries in there. Even if you find them, they still fail to load.

CRAP!!!!! That is WAY wrong! I must have uploaded the wrong one. I'll re-upload it with /usr/local/lib since that's the directory that the current Audacity will look at. Hoping that the next version will look at the (correct) /Library/... directory.

Leland

Weird thing happened...

So yesterday I deleted that ~ folder. Not at any time in the process I deleted the old 0.5.2 ffmpeg version.

Today I started audacity and it failed to locate ffmpeg...

I went to audacity download page and I downloaded ffmpeg 0.6.2 for mac again. I compared the md5sum with yesterdays download and it was different so I assume Leland has uploaded the correct version of the file.

I mounted the dmg and run the installation package. Accepted all the default values.

I checked the root dir no more ~ dir in there.

I started audacity it detected ffmpeg... but the old 0.5.2 version...

bgravato wrote:I started audacity it detected ffmpeg... but the old 0.5.2 version...

Can you post the Help -> Show Log contents? Also, could you check the dates on the /usr/local/lib/audacity contents? They should be yesterday.

Thanks,

Leland