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
Dynamic library path does not change unless using "Browse..." dialog #2282
Comments
|
Audacity 3.1+ should be able to load I will check, but just one small question - do you have an Intel Mac? |
|
@crsib Yes, it is an Intel Mac. |
|
It should either be clear that the text box to input the path does nothing, or fix that functionality. Right now the only way to change the dylib path is to use the I also think there should be some documentation on how to use ffmpeg via Homebrew on the wiki. Steps to reproduce:
Expected: Workaround:
|
|
I was sure it was fixed. I will recheck |
|
Turns out that the check was very confusing (and quite wrong). It was expected that the path would be a full path to a dylib. |
The meaning of the "Location of " field became confusing after the support for multiple FFmpeg versions was added. This commit changes the way how the content of the dialog is interpreted. Both full paths to avformat and to the directory containing avformat are now valid. Additionally, it fixes the way Audacity checks that FFmpeg works. Audacity will check if it can load the library instead of checking that the file exists.
The meaning of the "Location of " field became confusing after the support for multiple FFmpeg versions was added. This commit changes the way how the content of the dialog is interpreted. Both full paths to avformat and to the directory containing avformat are now valid. Additionally, it fixes the way Audacity checks that FFmpeg works. Audacity will check if it can load the library instead of checking that the file exists.
The meaning of the "Location of " field became confusing after the support for multiple FFmpeg versions was added. This commit changes the way how the content of the dialog is interpreted. Both full paths to avformat and to the directory containing avformat are now valid. Additionally, it fixes the way Audacity checks that FFmpeg works. Audacity will check if it can load the library instead of checking that the file exists.
The meaning of the "Location of " field became confusing after the support for multiple FFmpeg versions was added. This commit changes the way how the content of the dialog is interpreted. Both full paths to avformat and to the directory containing avformat are now valid. Additionally, it fixes the way Audacity checks that FFmpeg works. Audacity will check if it can load the library instead of checking that the file exists.


wildwestrom commentedDec 13, 2021
•
edited
Is your feature request related to a problem? Please describe.
There's a link to download a
.pkgfile containing dynamic libraries required for audacity to work. These are outdated, and probably the reason why I can't import various formats supported by ffmpeg (opus for example).When I try to point to the path
$HOMEBREW_PREFIX/Cellar/ffmpeg/4.4.1/lib/*.dylibnothing happens, it uses the same path as before.Describe the solution you'd like
I'd much rather use the libraries provided by the homebrew package. This way I can use the latest stable or nightly release of ffmpeg.
Describe alternatives you've considered
I thought to try compiling the libraries myself, but I don't know how to do it in such a way that Audacity will accept the libs. It looks like it's expecting these three:
ffmpeg.55.64bit.dylib ffmpeg_utils.52.64bit.dylib ffmpeg_codecs.55.64bit.dylibHomebrew creates these:
It seems Audacity is hardcoded to only accept certain filenames:
audacity/src/FFmpeg.cpp
Lines 180 to 192 in 0b3ba4f
audacity/libraries/lib-ffmpeg-support/FFmpegFunctions.cpp
Lines 125 to 137 in b630259
Additional context
N/A, maybe later
The text was updated successfully, but these errors were encountered: