Bug 1395 - Cover art not displayed when a folder contains an EAC cue file
: Cover art not displayed when a folder contains an EAC cue file
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 6.1.0
: PC Windows XP
: P2 normal (vote)
: Future
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-19 00:51 UTC by andy
Modified: 2008-12-15 13:06 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andy 2005-04-19 00:51:54 UTC
Cover art in folders containing an EAC cue file are not displayed, slimserver 
uses what looks like a windows default image for a folder containing music 
instead.
Cover art in folders which do not have a cue file are fine.
Comment 1 Blackketter Dean 2005-06-07 15:47:57 UTC
Kevin:  Do you know why the cover art may not be showing up?
Comment 2 KDF 2005-06-07 16:09:28 UTC
not a clue.  this isn't the first time cue sheets have caused some sort of
interference with cover art, but I never managed to figure out why the
interference was ever happening
Comment 3 Blackketter Dean 2005-06-07 16:14:19 UTC
Cool.  Thanks.
Comment 4 KDF 2005-06-07 16:24:55 UTC
I'll let you know if I come up with ideas, but I wouldn't count on me solving it
before 6.1 is all.
Comment 5 KDF 2005-06-07 16:30:56 UTC
1) is this just browse_artwork thumbnails or all cover art?
2) a sample EAC cue sheet that causes this would help.
3) d_artwork and d_parse output might help.
3) right click on the art image, select view image and refresh.  d_artwork from
that action may help too.
Comment 6 KDF 2005-08-09 09:49:48 UTC
still waiting on any new info on this.  anyone got files from a reproducable case?
Comment 7 Blackketter Dean 2005-08-19 22:15:55 UTC
Closing, due to inactivity.  Andy, if this is still an issue with the 6.2 nightly build, please reopen and add 
requested information.  Thanks.
Comment 8 James Richardson 2008-12-15 13:06:31 UTC
This bug appears to have been fixed in the latest release!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Make sure to include the version number of the software you are seeing the error with.