gwiner
Board Newbie
Group: Members
Posts: 9
Joined: Jan. 2003 |
 |
Posted: Feb. 04 2003,17:53 |
 |
| Quote (Magnus Brading @ Feb. 03 2003,18:02) | | Well, please consider that the "first" file might be of worse quality than the other (or even cut off or whatever), and therefore it might not be a good idea just to skip the other ones automatically. Also, what would be done with the failed files? The default with failed files is to leave them as is, and this would only make it even harder to find the duplicates, wouldn't it? |
All excellent points, Magnus...
Here's an idea:
I would leave the duplicate in place in the source path, and allow the user to manually act on it. As far as confusion as to why a file was not renamed, you could post a status in the "Warnings" dialog like: "File n.n was not renamed - a file of this name already exists" and Point users at an option to disable the feature in Prefs. I would assume that it would not be "on" by default anyway though...I think this would be easier to identify duplicates, as the status window would clearly say.
I agree though, for points you mention, there may be reasons to want to get duplicates. Which gets me thinking...Perhaps this is less of a file-renaming function than a list-generation function.
Basically, the issue I'm having now is that there is little I can do to remove duplicates from my library. I have tried "renaming" all files with "#" in them to a new directory for analysis, but then I can't also compare them to the "originals" w/o manually searching. This method also pulls out songs like "Love Potion #9", which kind of stinks. Anyway, my optimal solution would allow me some comparison criterea (tag contents) between files of duplicate names, and perform some operation on the results.
I know it's asking a lot, but I think it could be very helpful. Perhaps it could work as part of the "Create Custom Lists" function?
Anyway, I still love the program - Looking forward to that command-line stuff!
Regards,
gwiner
|
