View Issue Details

IDProjectCategoryView StatusLast Update
0003004MMW v4DB/FileMonitorpublic2022-04-29 01:31
Reporterrusty Assigned To 
PriorityimmediateSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Fixed in Version3.1 
Summary0003004: Locate Moved Missing Tracks: always fails when track timestamp doesn't match
DescriptionThis functionality often doesn't work because it relies on filesize AND an unchanged timestamp, and very often, a tracks timestamp will change.

Instead we should have a multistep process that checks for:
1) filesize/timestamp
2) for tracks still not found: filesize/filename OR hash OR unique audio fingerprint
Additional Informationhttp://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=2135&departmentid=2&ticketstatusid=1#
Tagstodoc-help
Fixed in build1197

Relationships

related to 0000863 closedpetr MMW v4 Missing tracks should be deleted during a scan 
related to 0002920 closedrusty MMW v4 Automated metadata lookup for tracks already in the DB 
related to 0017070 closedLudek MMW 5 Locate Moved/Missing files performance is slow 

Activities

jiri

2008-11-29 17:44

administrator   ~0015257

Fixed in build 1197.

The algorithm currently works as follows:
Step 1: Scan all tracks as in MM 3.0, i.e. use filesize and timestamp and also filename in case of multiple matches.
Step 2: In case there aren't some tracks found yet, start 2nd pass of all tracks and also read tags and then compare particularly track length (in seconds) and also Artist, Album and Title fields.

This way there's only pretty low chance that a track will remain not found.

peke

2008-12-04 03:37

developer   ~0015356

Verified 1199