-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audacity 3.2 for Mac Silicon does not find homebrew-installed ffmpeg #3747
Comments
@M-D-M we will look into it, but for now please download and install the FFmpeg package for OS X from Buanzo's website. Once it's installed, Audacity should recognize it automatically. |
Thank you for looking into this so quickly! Following up on the ffmpeg package from Buanzo's website -- I already had the x86 libs installed, but could not find any arm libs. |
AFAIK, there's one .dmg package for both architectures. |
(I think the buanzo website was updated after this issue was made) |
The pull request for this issue is not merged. Why is it closed? |
I have this issue too with 3.3.3 |
same for me as original post a year ago, installed Audacity 3.3.3 then installed Homebrew, then home-brew installed ffmpeg, after restarts, Audacity doesn't find it, using the preferences to direct it, Audacity asks for "libavformat.dylib" but any such files that one points to in the home-brew installation don't seem to please Audacity |
I also had the same issue, but I then found out that my local installation of FFmpeg was behaving weirdly. I've reinstalled the FFmpeg from |
This was also the case for me that some update created an issue with libsodium leading to my ffmpeg woes, fix was simply to brew upgrade and then it found the lib. It might be helpful to include a verbose error instead of just not finding the library in audacity if thats possible ;) |
Okay, I tried the following:
sudo rm -rf "/Library/Application Support/audacity/libs"
sudo ln -s "/opt/homebrew/var/homebrew/linked/ffmpeg/lib" "/Library/Application Support/audacity/libs"
Given that the So I'm back at the start, but this indicates that it's not a path search problem, but a binary compatiblity problem or something similar. |
Okay, I think I figured it out:
But version 7 doesn't work:
Homebrew updated to version 7 of |
Just to summarize the best workaround for now: brew install ffmpeg@6
sudo rm -rf "/Library/Application Support/audacity/libs"
sudo ln -s "/opt/homebrew/opt/ffmpeg@6/lib" "/Library/Application Support/audacity/libs" And once the next version of Audacity is released, you can clean up with: sudo rm -rf "/Library/Application Support/audacity/libs"
brew uninstall ffmpeg@6 Since |
Bug description
Summary:
Wanted to use the new version of Audacity for Mac Silicon (thanks for making it!), but unfortunately it does not find the version of ffmpeg I have installed through homebrew.
Further Description:
Installed Mac Silicon version of Audacity via .dmg file. Selected "do not replace previous version" when prompted via MacOS, because I wanted to keep the previous x86 version handy.
When loading Audacity, it says that ffmpeg libraries aren't loaded, and when trying to direct it to the folder with ffmpeg libraries installed via Homebrew (/opt/homebrew/Cellar/ffmpeg/*/lib), it does not find the right library.
Steps to reproduce
Download Mac Silicon version of Audacity.
Install using dmg file, and select "do not replace previous version" when prompted via MacOS.
Open Audacity, and get the popup about ffmpeg libraries not found.
Expected behavior
Audacity finds the ffmpeg libraries.
Actual behavior
Audacity is saying that "ffmpeg library not found."
Audacity Version
current master / alpha / nightly build
Operating system
macOS
Additional context
I have ffmpeg installed and in my path via Homebrew -- confirmed with "ffmpeg -version" from a cli.
It looks like audacity is wanting a file named "ffmpeg.64bit.dylib", but the files in the ffmpeg folder have names like the following:
libavcodec.59.37.100.dylib
libavdevice.59.7.100.dylib
libavfilter.8.44.100.dylib
libavformat.59.27.100.dylib
The text was updated successfully, but these errors were encountered: