Numbers in the position of that 0 usually relate to the version number, thus allowing multiple versions to exist side-by-side (with the symlink pointing to the "default"), but LAME reports itself to be in version 3.100 so I'm not sure if that applies in this situation. Again, no idea why this change in behavior. Further, even though I selected /opt/local/lib/libmp3lame.dylib the library location now points specifically to /opt/local/lib/libmp3lame.0.dylib which means once it stopped forcing the filename to libmp3lame.dylib it could (and did) follow the symlink. Why it would have trouble now, but not before, I have no idea. So it seems that Audacity is having trouble following the symlink. Looking more closely, it seems that /opt/local/lib/libmp3lame.dylib is a symlink to /opt/local/lib/libmp3lame.0.dylib which, as noted in the logs and posted, is what actually gets loaded (the lines are the same in my log now).
Without it behavior was the same as before.
Then allow File type: Dynamic Libraries *dylibsĪnd then navigate to /opt/local/lib and select /opt/local/lib/libmp3lame.dylib 17:34:25: Attempting to load LAME from system search pathsġ7:34:25: Loading LAME from libmp3lame.dylibġ7:34:25: Error: dlopen(libmp3lame.dylib, 1): image not foundġ7:34:25: Attempting to load LAME from builtin pathġ7:34:25: Loading LAME from /Library/Application Support/audacity/libs/libmp3lame.dylibġ7:34:25: Error: dlopen(/Library/Application Support/audacity/libs/libmp3lame.dylib, 1): image not foundġ7:36:30: Attempting to load LAME from previously defined pathġ7:36:30: Loading LAME from /opt/local/lib/libmp3lame.0.dylibġ7:36:30: Actual LAME path /opt/local/lib/libmp3lame.0.dylibġ7:36:30: LAME library successfully loaded I had to manually select the LAME library from within Audacity to have it find the MacPorts' installed version (Preferences -> Libraries -> MP3 Library -> Locate -> Browse) Question is of course why that feature doesn't work for you. The mention of a "previously defined path" in my case indicates that I probably pointed Audacity to LAME once before. Or that /opt/local/lib somehow and all of a sudden disappeared from that search path. What you're seeing suggests that Audacity (all of a sudden?) started trying to load libmp3lame via the standard system library search path, which probably doesn't include /opt/local/lib. Some of the CODECS in FFmpeg are still covered by patents.14:40:38: Attempting to load LAME from system search pathsġ4:40:38: Loading LAME from libmp3lame.dylibġ4:40:38: Error: dlopen(libmp3lame.dylib, 1): image not foundġ4:40:38: Attempting to load LAME from builtin pathġ4:40:38: Loading LAME from /Library/Application Support/audacity/libs/libmp3lame.dylibġ4:40:38: Error: dlopen(/Library/Application Support/audacity/libs/libmp3lame.dylib, 1): image not foundĢ3:34:11: Attempting to load LAME from previously defined pathĢ3:34:11: Loading LAME from /opt/local/lib/libmp3lame.0.dylibĢ3:34:11: LAME library successfully loaded
AUDACITY LAME LICENSE
And, it's legal to distribute MP3s without any license (as long as you are the copyright owner of the song/program). The patents expired a couple of years ago so now it's legal to give-away LAME, and legal to include it in Audacity. You had to buy an application that included a licensed copy. As an individual you couldn't buy a single license or buy a licensed copy of LAME.
AUDACITY LAME DOWNLOAD
So, you had to compile it yourself or download from 3rd-party sites who were willing to take the risk (both still illegal and you could theoretically be sued if you distributed MP3s made this way), or you could buy an application (such as dBpowerAmp) that included a licensed copy. When LAME was created there were patents covering MP3 and it WAS illegal to distribute a complete-working MP3 encoder/decoder without paying royalties. It has to be compiled to get a usable EXE or DLL file.
AUDACITY LAME CODE
Online explanations of the program include "LAME is an educational tool to be used for learning about MP3 encoding"The official LAME website distributes the source code (raw computer code).
0 kommentar(er)
