Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jmbailey2000]

I noticed this in MC17 and now MC18. Maybe I'm missing a setting somewhere, but when I rename/move files and the file already exists in the destination folder, MC renumbers that file (so now I have duplicates). In MC14 (had forgone a couple of upgrades), it would warn me that the file already existed and let me choose to overwrite the file if desired.

Does this feature still exist in MC? I didn't realize it and now have a bunch of duplicate files in the library and on the drive because there was no warning of any kind.

Thanks!

[MrC]

I don't know of any option to avoid this.

If you need help quickly identifying the dups so you can eliminate them, ask for more help...

[jmbailey2000]

Identifying the dups is not an issue. Have/know that ability.

It is the curiosity why a feature that forewarned you that files already existed (and let you choose your path) was removed in favor of automatically renaming files without telling you (thereby unwittingly allowing the user to create potentially massive quantities of duplicate files) was removed from the system.

Just seemed odd, thought maybe I missed something somewhere.

[MrC]

Rename changed substantially in the past couple of versions. And I don't recall how it used to behave wrt renaming a file to a file that exists in MC.

MC now handles more bundled files when a single MC entry is renamed (artwork, sidecar files, etc.).

I believe MC calls out to Explorer to perform the move, so overwrites are detected at the Explorer level.  It may be that when a file exists in MC, it can just rename that file uniquely by asking Explorer to use a safe rename (adds prefix), and then MC can use the new you're asking for.

Bug alert ahead...

When I rename over an existing file (not in the MC library), I get a confirmation dialog asking about overwriting.  Its the standard Explorer confirmation asking to Replace, Don't Replace, or Copy.  I've found that if I deny overwriting, MC has already moved sidecar and artwork files, so has broken the "atomicity" of a library entry (hence losing cover art, sidecar data).  This seems a bug.