Possible bug? (duplicate management)

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Possible bug? (duplicate management)

Re: Possible bug? (duplicate management)

by Peke » Fri Oct 24, 2025 4:27 am

christopher.wanko wrote: ↑Thu Oct 23, 2025 7:22 pm I don't see how manually clicking 500 items is better than setting up some rules and have them flagged by rule. But I do like your method for using metadata to mark things. I do a similar thing to make Plex pickup my songs.
It is not problem making things automatic, but from my personal opinion to really know which one is duplicate or not you need to listen tracks and decide :( So best is not to add something to MM that can prove working faulty than not having that at all. Example I have 200k of tracks and if I trust that MM devs created automation correctly it can lead to deletion of 20k tracks that are collected over the years with single click.

Re: Possible bug? (duplicate management)

by christopher.wanko » Thu Oct 23, 2025 7:22 pm

I don't see how manually clicking 500 items is better than setting up some rules and have them flagged by rule. But I do like your method for using metadata to mark things. I do a similar thing to make Plex pickup my songs.

Re: Possible bug?

by Peke » Thu Oct 02, 2025 3:47 pm

christopher.wanko wrote: ↑Thu Oct 02, 2025 3:22 pm ... I can easily find them, but I can't easily group them for batch deletion, can I?

No, no I can't. We used to have rules we could apply to tag the items for deletion... I had to export the results, write a function to identify the "group" such as it was, then apply rules. It was a little fun but more tedious than fun.

Guess it's extensions time.
Hmmm, May I suggest better approach?
1. Select Files you want to mark for deletion.
2. Use ALT+0 to mark Them as 0 Stars
3. Repeat 2
3a. (Only one time) Create Auto-Playlist with 0 Stars
4. Go to Auto Playlist -> Review track listed -> Delete All tracks :)

or

1. Add MOOD to toolbar
1a. (only first time) Select one duplicate file -> Properties -> Classification -> Mood = !DUPLICATE -> OK
2. Select rest Files you want to mark for deletion.
3. Use ALT+0 to mark Them as 0 Stars + Toolbar: Mood -> !DUPLICATE
4. Repeat 2-3
4a. (Only one time) Create Auto-Playlist with 0 Stars + Mood = !DUPLICATE
5. Go to Auto Playlist -> Review track listed -> Delete All tracks :)

Re: Possible bug?

by christopher.wanko » Thu Oct 02, 2025 3:22 pm

... I can easily find them, but I can't easily group them for batch deletion, can I?

No, no I can't. We used to have rules we could apply to tag the items for deletion... I had to export the results, write a function to identify the "group" such as it was, then apply rules. It was a little fun but more tedious than fun.

Guess it's extensions time.

Re: Possible bug?

by Peke » Sun Sep 07, 2025 8:34 pm

christopher.wanko wrote: ↑Sun Sep 07, 2025 7:52 am Now I have to ask for a feature that will tag those matches with a unique ID, so I can batch locate and delete them, kind of like the MM4 days.
If you have enabled Analyze for duplicates in Options -> Library and tracks are analyzed then you can easily find them.
Image

Re: Possible bug?

by christopher.wanko » Sun Sep 07, 2025 7:52 am

Peke wrote: ↑Thu Sep 04, 2025 4:21 am When analyzing MM Hash Check only Audio Data from files and create fingerprinting. That means Tag changes will not influence fingerprinting and that is why two files with different size and tags can have same fingerprint because only Audio if calculated.
Oh that is excellent news, thank you very much.

Now I have to ask for a feature that will tag those matches with a unique ID, so I can batch locate and delete them, kind of like the MM4 days.

-C

Re: Possible bug?

by Peke » Thu Sep 04, 2025 4:21 am

Hi,
christopher.wanko wrote: ↑Thu Aug 28, 2025 12:42 pm Can you answer my question about audio fingerprinting? How is it derived?
When analyzing MM Hash Check only Audio Data from files and create fingerprinting. That means Tag changes will not influence fingerprinting and that is why two files with different size and tags can have same fingerprint because only Audio if calculated.

Re: Possible bug?

by christopher.wanko » Thu Aug 28, 2025 12:42 pm

I'll do that and report back. Can you answer my question about audio fingerprinting? How is it derived?

Re: Possible bug?

by Lowlander » Thu Aug 28, 2025 11:53 am

Have you listened to the files to see if the seem to be the same or different audio files?

Possible bug? (duplicate management)

by christopher.wanko » Thu Aug 28, 2025 11:41 am

I have been assiduously clearing out duplicates from my library, but MM duplicate finder (on content) is flagging many, many files.

Just as a spot check, I took three files it has flagged as duplicate content. When using certutil -hashile <filename> SHA256 I get different hash values.

How is it that a hashing function shows me these aren't duplicate content, but "audio fingerprints" say they are identical? How is the "audio fingerprint" derived? What should I trust here?

--#

Top