Quote:
Originally Posted by Aggregate
The latest LameXP release has stolen all multimedia files associations to itself (mp3, m3u, wav, etc.), however I don't remember any question about files associations during the installation. Is this normally ? What's the reason for these files associations for LameXP, if it's not an audio player, but it's formats encoder ?
|
Not quite sure what is happening.
What I can say for sure is that the
shell integration code, which would be relevant here, has
not been changed since some time around 2015:
https://github.com/lordmulder/LameXP...ntegration.cpp
What this code does: For each "supported" file extension (
.wav,
.mp3, etc. pp.), it will lookup the file type that is currently registered to that extension. Then, for each of those
existing file types, it will
add a custom command ("ConvertWithLameXP"). The standard "open" command of the file type is
not modified. Also, for file extensions that already
are registered to a file type, the file extension to file type mapping is
not changed.
If and only if one of the "supported" file extensions is
not registered to a file type at all (which rarely happens, but is possible), then a mapping to the our own "LameXP.SupportedAudioFile" file type is created for that file extension.
Works as expected for me. This is on Windows 10 v1909:
https://i.imgur.com/KpStPIe.png