Bummer! :-(
I just spent hours combing through my library getting rid of the many duplicate files that have accumulated.
Apparently when a second file was named the same as an already existing file, it was named with a "(1)" or a "(2)" after it so that windows would allow it.
To make matters worse, it has ALSO occurred when I changed my file/directory criteria within MC to eliminate the Album folder, and went from: Artist/Album/Artist - Album - Track - Name to
Artist/Artist - Album - Track - Name. When I did this MC apparently decided to leave many of the original files in their "Artist/Album" folders and simply copy them to their new locations, thus creating additional duplicates.
Thirdly, when I selected these duplicates in MC's file list and hit 'Shift-Delete' chosing to send them to my recycle bin . . . . only to finish up and find the Recycle Bin empty!!
Where did these files go?? Did MC merely ignore my request to place them in the recycle bin and 'flush' them? Or did it decide not to delete them at all?? I hate to even look.
Now when I reported the first problem listed above, Jim had said this was a Windows issue, or due to read-only files . . . . however, I do not believe this is not the case (and they are NOT read-only). The first situation I describe I imagine could be some windows issue, but unlikely (this is a technique usually used by software, I do not recall having seen windows do this). However, since the second situation I described was all a result of an MC operation, performed by MC, and within MC, thus appearing to be an MC issue.
Has anyone else found such a situation to have occurred?