At some point (maybe due to a new media player not supporting wma), you change this to
alternatives:
myexternal:
formats: m4a
On the next update, this will happen:
>/path/to/track 1.wma -> /path/to/track 1.m4a
While it's not feasible to detect every kind of format change (which might be minor such as modified target bitrates), beets-alternatives should not rename files to incorrect extensions, but actually reencode in these cases. Hence this PR.
Consider the following scenario:
Initial configuration:
add a file:
At some point (maybe due to a new media player not supporting wma), you change this to
On the next update, this will happen:
While it's not feasible to detect every kind of format change (which might be minor such as modified target bitrates),
beets-alternatives
should not rename files to incorrect extensions, but actually reencode in these cases. Hence this PR.(The PR is relative to #26)