[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 213573] broken search or corrupted databese
From:       Jeff Mitchell <mitchell () kde ! org>
Date:       2010-10-01 3:36:02
Message-ID: 20101001033602.D1D686EFE1 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=213573





--- Comment #20 from Jeff Mitchell <mitchell kde org>  2010-10-01 05:35:58 ---
(In reply to comment #18)
> changed metadata using vlc (song title and artist)
> click update collection
> artist changed but not the album name

FWIW, I don't actually know why that action would cause the artist to change --
I would expect it under most conditions not to change at all.

The reason is that the collection scanner works based on directory, not file,
mtimes (otherwise it would be far, far slower when determining whether or not
it needs to scan anything, and for some users could take so long to check all
files that it would be in a neverending scanloop). The file size would in most
cases not even change since ID3v2 tags can have padding.

So, the changes you made above would cause the file mtime to change but not the
directory.

The only reasons that this would not be the case are: if the file was rewritten
to add extra padding (I don't remember if this would cause the dir mtime to be
changed or not) or if the file were written into a temporary location and then
moved in place of the original.

Just something to be aware of, because some taggers will definitely write
in-place and will not cause the directory mtime to change.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]