I suspect, like some other tools I've used that use the lame_enc.dll, they are somehow hard-coded to the one used specifically for Audacity. I don't like this either as this version is not the latest. I suspect that Lasconic will fill us in on why it is this specific version. I certainly tried others and all I got was an error message and MS crashed.
For legal reason, lame_enc.dll cannot be shipped with MuseScore (or any other open source tool). So I implemented the same trick than in Audacity, i.e. loading the library dynamically. When you do, you will call specific functions in the library and you expect them to be there. I tested with the library provided by the lame project for audacity (version 3.98.2) and it works ok meaning you can export as MP3.
If you installed one of these files, a key is added in the windows registry or a specific file is added on MacOSX. The code is looking for this to automatically use this file. It's easier for users like this. I agree that a preference entry would be good as well and I will try to add this.
@schepers Why would you want to use a more recent version of Lame? Which one did you tried ? I would like to at least don't crash and give you an error message.
"@schepers Why would you want to use a more recent version of Lame? Which one did you tried ? I would like to at least don't crash and give you an error message."
Simply because this is _not_ the official general release version, and the Audacity version is older. Lame development continue to improve the quality and accuracy of MP3 encoding. The Audacity version is 3.98.3, the latest release is 3.98.4, with 4.00 alphas/betas available, but I wouldn't trust them. I tried 3.98.4
"When you do, you will call specific functions in the library and you expect them to be there."
If this is true, the library calling functions should not change and so other versions should work. The front-end I use for Lame encoding (RazorLame) doesn't seem to care what version of Lame I use (and I update it occasionally), so there's something not implemented correctly.
Comments
I suspect, like some other tools I've used that use the lame_enc.dll, they are somehow hard-coded to the one used specifically for Audacity. I don't like this either as this version is not the latest. I suspect that Lasconic will fill us in on why it is this specific version. I certainly tried others and all I got was an error message and MS crashed.
For legal reason, lame_enc.dll cannot be shipped with MuseScore (or any other open source tool). So I implemented the same trick than in Audacity, i.e. loading the library dynamically. When you do, you will call specific functions in the library and you expect them to be there. I tested with the library provided by the lame project for audacity (version 3.98.2) and it works ok meaning you can export as MP3.
If you installed one of these files, a key is added in the windows registry or a specific file is added on MacOSX. The code is looking for this to automatically use this file. It's easier for users like this. I agree that a preference entry would be good as well and I will try to add this.
@schepers Why would you want to use a more recent version of Lame? Which one did you tried ? I would like to at least don't crash and give you an error message.
"@schepers Why would you want to use a more recent version of Lame? Which one did you tried ? I would like to at least don't crash and give you an error message."
Simply because this is _not_ the official general release version, and the Audacity version is older. Lame development continue to improve the quality and accuracy of MP3 encoding. The Audacity version is 3.98.3, the latest release is 3.98.4, with 4.00 alphas/betas available, but I wouldn't trust them. I tried 3.98.4
"When you do, you will call specific functions in the library and you expect them to be there."
If this is true, the library calling functions should not change and so other versions should work. The front-end I use for Lame encoding (RazorLame) doesn't seem to care what version of Lame I use (and I update it occasionally), so there's something not implemented correctly.
Fixed long ago.
It wasn't fixed.
#208006: Embed MP3 support by default - even if this is implemented, what if a better one becomes available?