Bugzilla – Bug 5187
Partial thumbnail cover lost when "look for new and changed music"
Last modified: 2007-07-26 22:12:44 UTC
Copy of message http://forums.slimdevices.com/showthread.php?t=37104 If the response given is right, this is a known problem but I didn't find it open here in bugzilla ========== Hi, I'm annoyed from the beginning with a little bug. From now, I was used to "clear library and rescan everything" but as my song collection is growing this is becoming more and more annoying. Here is my problem: - clear library and rescan everything" always works perfectly wether the artwork is a song artwork in a flac file, a folder.jpg in my directory and everything. - when using "loook for new and changed music", song covers are displaying in the "now playing"; album covers are displayed well when I click on the album but some² thumbnails are broken displaying the grey question mark, but the img name isn't "generic": http://<myserver>:9000/music/568/thumb_100x100_f_000000.jpg Is this a known problem? (I've look around but only found "complete artwork broken" problems, not partial like this one. Is there a workaround? Should I move this problem right now in bugzilla? ²: around 10 broken covers on 150 albums ================ I don't use itunes plugins and most of my music collection is flac with folder.jpg + cover art in flac files. A little part of my collection is MP3 with folder.jpg and cover art in mp3 files.
I forgot to mention the following facts: - This problem *seems* to occur to album whom I changed tags - This problem occur for albums that were previously working and that would work correctly with full rescan
Yes, this is a known bug. I reported it recently in bug 5159. I don't believe it's necessary to run the new/changed rescan. As soon as you modify the album's music files, causing a change to their timestamps, you lose the thumbnail image.
Yup, you're totally right, it seems like the same bug. I linked 5187 with 5159. This bug is really annoying, doesn't slimdevice took position on it? As it is well known, I wonder if it will be corrected or left alone 'til 7.0 is out?
*** This bug has been marked as a duplicate of 5159 ***