Take file mtime's into account when calculating freshness hashes during scanning.
Bug #905669 reported by
Ilkka Tuohela
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Triaged
|
Low
|
Unassigned |
Bug Description
I noticed library rescan takes quite long time even for files which have not been modified.
Did not check the code, but I checked the database schema and couldn't find any place where the file modification timestamp would be stored. I would suggest modifying the schema and default file scanner to store it to database, and only checking files which have more recent st_mtime on linux/osx (don't remember how this works in windows!).
Just remember the common gotcha that modifying a file in a directory on unix does NOT update directory mtime unless filename is changed, so you need to check file mtimes not album directory mtimes ...
To post a comment you must log in.
This could be achieved like mentioned in bug #898487, together with bug #893242.
"Add configuration path command-line option" + "(Relative) Library Path"