Summary: | Cover Manager functionality does not work for albums attributed to "Various Artists" | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | John Atkinson <john> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | CLOSED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.4.6 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
John Atkinson
2007-08-06 21:49:30 UTC
Update: Hmm... behaviour has now changed slightly. Now, all albums named "Misc" are affected as well as the Various artists albums. I did not think this was happening before because when I applied a cover to a Misc album it worked correctly. However, unlike the various artist albums, they did not have an image set already. It appears that while these albums can have an image set once, it cannot be removed afterward and cannot be changed. I have noticed that albums with album art stored as files with the album also display this. Note: The misc and various artist albums DO NOT have album art saved as a file. Additional info: Kubuntu Feisty (2.6.20-16-generic) XUL Remote script installed. Files mounted on an NTFS partition using the ntfs-3g driver. Files are all MP3 format And to explain a little about the whole "Misc" album thing here's an example directory structure: Music Root | |- Artist 1 |- Real Album Name #1 (MP3s tagged with album as "Real Album Name #1") |- Real Album Name #2 (MP3s tagged with album as "Real Album Name #2") |- Misc (MP3s tagged with album as "Misc") | |- Artist 2 |- Real Album Name #3 (MP3s tagged with album as "Real Album Name #3") |- Real Album Name #4 (MP3s tagged with album as "Real Album Name #4") |- Misc (MP3s tagged with album as "Misc") There has been a change in the API used by Amarok after 1.4.8 release. Version 1.4.9.1 is likely to have fixed this. Also, not all albums with mixed artists do have covers available... Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Thank you for your report though. Please don't hesitate to report new bugs should you have any problems with Amarok 2 once it is released. This bug is still present in (KUbuntu) Amarok 1.4.9.1 Sorry, but Amarok 1.4.x is not actively maintained anymore. The developers focus on Amarok 2.0, currently in alpha state and final due in a few weeks time. |