Better notification of duplicates when using the file organiser

[mrbenn]

I can't completely work out what conditions make "Duplicate" appear in the file organiser vs adding "_1.ext" to the filename, but my best guess is that a given file has to be a) selected and sent to file organiser and b) both files need to be moving to a new destination if you proceed for it to show "Duplicate"

If the file already exists and is not sent to file organiser, or that file would not need to move, it adds _1.ext to the one that would.






Wouldn't it be better to also show Duplicate, or File Already Exists rather than just quietly adding _1 ?

It's not easy to see unless it's a small number if files, and impossible when there are thousands in the list.

Thanks

[Mayibongwe]

Wouldn't it be better to also show Duplicate, or File Already Exists rather than just quietly adding _1 ?

I have to agree - your suggestion sounds ideal.
In both circumstances, MusicBee is detecting the duplicates, but handling them differently.
So for uniformity's sake, I would also vote that in the 1st image/scenario, it also asks users what they want do with the duplicate filename when detected.

Edit:
I support this as it has potential to be a stress factor when dealing with multiple files as mentioned by Mr Benn.
<Filename> as a field is not built into the existing Duplicates Manager.
So I'm currently just struggling to think of how one would be able to locate those duplicated filenames if they were erroneously configured in the hundreds.

Edit 2:
Oh no, there is a "more" section in the duplicates manager where somebody can easily setup a virtual tag that references the filename as the criteria.
So the aftermath can still be rectified with no biggie.

[mrbenn]

In both circumstances, MusicBee is detecting the duplicates, but handling them differently.

exactly.

So the aftermath can still be rectified with no biggie.

well, depends on the aftermath. Often its not that the *files* are the same, but the *name of the file* is. I might replace an old vinyl 192 mp3 with a web re-release 320 and depending on what beets does, it will have identical enough details to clash. Unless the bitrate/extension are different it's then a case of using the date added and/or date changed fields by eye to make sure I'm not mixing sources.

[Steven]

For manual organisation this now flags the duplicate files (thats how it was originally intended some time ago). However auto-organisation still appends _1 for conflicts

https://getmusicbee.com/patches/MusicBee36_Patched.zip
unzip and replace the existing musicbee application files

[mrbenn]

Amazing. Thank you.