Audacity Forum

thanks for your replies I have a previous install of 2.0.3 with ffmpeg, lame and few other libraries. I dragged the old Audacity (2.0.3) out of my applications and onto my Desktop, then dragged the new 2.1.1 folder into the applications folder, it looks ...

... can't find it and I can't find it if I look in /Library/Application support/audacity/ There's only a directory named "libs", containing ffmpeg. or in /Applications/Audacity/ But prefs are kept for 2.1.0 and 2.1.1... As an experiment, I moved the audacity folder from Application support ...

... enabled users to read /usr/local/ again. Other times they had to go in as root to change permissions on that folder or just not use it for LAME or FFmpeg. And yes sometimes Repair Permissions can "seemingly" fix issues with ~/Library/Application Support/audacity/ (with or without restart ...

... the new 2.1.1 release in Ubuntu but failed at dpkg-buildpackage. configure_flags := \ --disable-dynamic-loading \ --with-expat=system \ --with-ffmpeg=system \ --with-lame=system \ --with-libflac=system \ --with-libid3tag=system \ --with-libmad=system \ --without-libresample \ --without-libsamplerate ...

... only verifies and repairs ***some*** system permissions. Doesn't do a thing for user owned data... Yes - but against that, if the problem was that FFmpeg or LAME are in /usr/local and Mac is blocking read access to that location unless logged in as admin, we know from past experience that repairing ...

... only verifies and repairs ***some*** system permissions. Doesn't do a thing for user owned data... Yes - but against that, if the problem was that FFmpeg or LAME are in /usr/local and Mac is blocking read access to that location unless logged in as admin, we know from past experience that repairing ...

... if the problem was that FFmpeg or LAME are in /usr/local and Mac is blocking read access to that location unless logged in as admin, we know from past experience that repairing permissions can fix that. In my case the libraries were ...

Gale Andrews wrote:... if the problem was that FFmpeg or LAME are in /usr/local and Mac is blocking read access to that location unless logged in as admin, we know from past experience that repairing permissions can fix that.

In my case the libraries were (and stll are) unter /Library/Application Support/audacity/

... only verifies and repairs ***some*** system permissions. Doesn't do a thing for user owned data... Yes - but against that, if the problem was that FFmpeg or LAME are in /usr/local and Mac is blocking read access to that location unless logged in as admin, we know from past experience that repairing ...

... using a non-standard path for the Audacity temp folder. So it is probably good to start with factory default settings. You may have to relocate FFmpeg. There should not be any other problem. If there are any more problems please let us know. Gale