05-21-2024, 03:32 AM
1. It calculates hashes for each file to see if there is any difference between them. If there is a difference, and the "Update songs if matching files are found" option is checked, then it will replace the existing file in the song. It matches up files based on the destination file path. If "Create Subdirectory per Song" is off, this effectively just compares filenames, as each file in the library must be uniquely named. If "Create Subdirectory per Song" is enabled, then the subdirectory name that is calculated from the filename must match as well.
2. Given that the Import->Local File option is primarily designed for a smaller number of files being imported at once, for each file, if there is a conflict you will get an option to decide how to handle the conflict. If you select "Update existing song with new file", then that is the same as the batch import "Update songs if matching files are found" option being checked.
3. I would need to know what options you selected, as something doesn't sound right there. As long as you have unchecked "Create Subdirectory per Song" and no subdirectories are currently in use in the storage location, and you are importing files whose name match files in the storage location, then you should have been prompted to update the existing song, and a new one should not have been created.
If you inspect the storage location and you see subdirectories, then you may currently have a mix of folders with no folders, which is a problem. Create a library backup under Settings->Backup and Restore->Backup Library, then restore that backup under Settings->Backup and Restore->Restore Library from Backup. That will remove all the subdirectories if "Create Subdirectory per Song" is unchecked (it is unchecked by default now and should generally be left off). Then duplicate file detection should work better.
Mike
2. Given that the Import->Local File option is primarily designed for a smaller number of files being imported at once, for each file, if there is a conflict you will get an option to decide how to handle the conflict. If you select "Update existing song with new file", then that is the same as the batch import "Update songs if matching files are found" option being checked.
3. I would need to know what options you selected, as something doesn't sound right there. As long as you have unchecked "Create Subdirectory per Song" and no subdirectories are currently in use in the storage location, and you are importing files whose name match files in the storage location, then you should have been prompted to update the existing song, and a new one should not have been created.
If you inspect the storage location and you see subdirectories, then you may currently have a mix of folders with no folders, which is a problem. Create a library backup under Settings->Backup and Restore->Backup Library, then restore that backup under Settings->Backup and Restore->Restore Library from Backup. That will remove all the subdirectories if "Create Subdirectory per Song" is unchecked (it is unchecked by default now and should generally be left off). Then duplicate file detection should work better.
Mike