3 | | This step is what made things work. Without it behavior was the same as before. 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 log @kencu posted, is what actually gets loaded (the lines are the same in my log now). So it seems that Audacity is having trouble following the symlink. Why it would have trouble now, but not before, I have no idea. 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. Again, no idea why this change in behavior. |
| 3 | This step is what made things work. Without it behavior was the same as before. 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 @kencu and @RJVB posted, is what actually gets loaded (the lines are the same in my log now). So it seems that Audacity is having trouble following the symlink. Why it would have trouble now, but not before, I have no idea. 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. Again, no idea why this change in behavior. |