by tintmylf » Sat Jun 17, 2017 8:11 pm
I thought I'd turn on the "Analyze files for duplicates" option to see if/how many duplicate tracks were lurking about my library. I was very careful to confirm that "Update file info from Tags when rescanning files" was unchecked. After doing so, restarting (since I have it monitoring music folders to scan on startup), and letting it run for a few hours to scan everything, I discovered numerous tracks in my library where various bits of tagged information had been changed, including artist names, album names, album artists, and ratings, among others. Thankfully I had a backup of the DB.
As a test, I carefully repeated the process and the same thing happened. As it is analyzing files it is changing data in the library, presumably to match that embedded in the file, even though the explicit option to do this is turned off.
An obvious short term solution is to make sure I sync the library data back to the files prior to turning on the analyze option, but this behavior appears to be incorrect as far as I can tell. If the analyze option is supposed to update tags in and/and all circumstances this should be made more clear.
I'll run another test where I sync some, but not all, of the changing tracks prior to turning on the analyze option to confirm that these do not change when analyzed if synced in advance, but wanted to report what I'm seeing now since this test could take awhile to run properly.
Addendum: I'm using MediaMonkey 4.1.16.1836 in Win10.
I thought I'd turn on the "Analyze files for duplicates" option to see if/how many duplicate tracks were lurking about my library. I was very careful to confirm that "Update file info from Tags when rescanning files" was unchecked. After doing so, restarting (since I have it monitoring music folders to scan on startup), and letting it run for a few hours to scan everything, I discovered numerous tracks in my library where various bits of tagged information had been changed, including artist names, album names, album artists, and ratings, among others. Thankfully I had a backup of the DB.
As a test, I carefully repeated the process and the same thing happened. As it is analyzing files it is changing data in the library, presumably to match that embedded in the file, even though the explicit option to do this is turned off.
An obvious short term solution is to make sure I sync the library data back to the files prior to turning on the analyze option, but this behavior appears to be incorrect as far as I can tell. If the analyze option is supposed to update tags in and/and all circumstances this should be made more clear.
I'll run another test where I sync some, but not all, of the changing tracks prior to turning on the analyze option to confirm that these do not change when analyzed if synced in advance, but wanted to report what I'm seeing now since this test could take awhile to run properly.
Addendum: I'm using MediaMonkey 4.1.16.1836 in Win10.