Summary: | Amarok doesn't recognize changes of cover.jpg images in folders | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Jan Hofmann <elusive> |
Component: | Tools/Cover Manager | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | samuel.brack, stuffcorpse |
Priority: | NOR | ||
Version: | 2.2.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.4 |
Description
Jan Hofmann
2010-02-07 21:05:23 UTC
Not sure this is still a problem in current git, there has been extensive work in the CoverManager since Amarok 2.2.2 was released. Rick, any input about this? Sorry, I must have missed this somehow. The cover manager/fetcher atm doesn't look at images on disk; the collection scanner does that. I wrote in BUG:232849 Comment #2 how the current system works. Currently it's a pain to do what the Jan wants, mostly due to BUG: 223222. I'm going to fix that, then unsetting album covers would be easy. Once that's done, a collection rescan should get those cover.jpg on disk set for the albums. I also want to add the ability to look in the music folder for images to the cover fetcher so that should take care of this use case as well. The problem seems to be fixed in 2.4-GIT, since I reproduced the conditions when this bug appeared (I added a cover from the internet in a folder where an album without a cover was, deactivated the download of new covers, deleted the caches and restarted amarok). After restarting amarok the new cover and all old covers that are saved on the hard disk were shown by amarok. Only one time (I tested the bug against several albums) I had to do a re-scan of the collection, but after doing that amarok worked like expected. Closing as fixed, thanks for testing |