by Kupuna » Sun Jun 25, 2017 11:34 pm
I mistakenly scanned in a backup copy of my major MM database. I now have nearly 800 duplicate files. I've used the find duplicates command but problem is (for example) that some of my current db entries have been converted from m3p to m3a. They properly show up as duplicates, but I have to wade through choosing the "best" track in each case.
My plan is to delete the entire current database and then re-scan the most current stored db containing the tracks. I've read that I will lose certain data details, but compared to handling 800 duplicates one by one, this seems the cleanest way to go. Does anyone agree or have alternate tactics?
SECOND QUESTION:
Once I get the db back in shape, is there any command or add-on that would flag or prevent adding a duplicate track? Not after I've done it, but as I'm trying to load the track? Probably not, but it would be a great idea.
I mistakenly scanned in a backup copy of my major MM database. I now have nearly 800 duplicate files. I've used the find duplicates command but problem is (for example) that some of my current db entries have been converted from m3p to m3a. They properly show up as duplicates, but I have to wade through choosing the "best" track in each case.
My plan is to delete the entire current database and then re-scan the most current stored db containing the tracks. I've read that I will lose certain data details, but compared to handling 800 duplicates one by one, this seems the cleanest way to go. Does anyone agree or have alternate tactics?
SECOND QUESTION:
Once I get the db back in shape, is there any command or add-on that would flag or prevent adding a duplicate track? Not after I've done it, but [i]as[/i] I'm trying to load the track? Probably not, but it would be a great idea.
