View Issue Details

IDProjectCategoryView StatusLast Update
0002397MMW v4Properties/Auto-Toolspublic2007-09-16 11:57
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Fixed in Version3.0 
Summary0002397: Duplicate Content node appears not to work (hashes not generated on rescan)
DescriptionAs reported in the forum, the Duplicate Content node appears not to work. This is because:

1) Rescans of files that already exist in the library don't generate hashes.
2) Identical OGG files aren't flagged as duplicates, nor are they flagged as dups when identical but just the tags have changed (this problem doesn't occur with MP3 or FLAC files).
3) If there are 2 identical FLAC files that are flagged as identical, and then 2 identical MP3 files (having the same filename) are added, the latter 2 identical files aren't flagged as dups.

I suspect that some of this behaviour is a regression related to 0002393

Additional InformationI looked into this based on the following report: http://www.mediamonkey.com/forum/viewtopic.php?t=8449
TagsNo tags attached.
Fixed in build1075

Relationships

related to 0002393 closedjiri Falsely reported duplicates after conversion 

Activities

jiri

2006-03-01 22:09

administrator   ~0006973

I wasn't able to reproduce 2&3 and also I don't think there should be any bug there. Are you sure files were properly scanned and were really duplicates?

As far as I know there are only following issues:
1) As described above.
4) Part of 2), tags are ignored only for mp3 files, for other files it doesn't work yet.

1) could be fixed for MM 2.5.2 (although I don't find it that urgent), 4) can't be fixed easily for all formats.

rusty

2007-09-10 13:18

administrator   ~0010656

1) Should be fixed for 3.0 i.e.
When rescanning the library, MM should automatically generate hashes for tracks that are missing them if the option to generate hashes is enabled.

jiri

2007-09-16 11:57

administrator   ~0010796

Fixed in build 1075.