Bug 1442 - "New Music" artist display not accurate with various artist disc
: "New Music" artist display not accurate with various artist disc
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 6.1.0
: All All
: P2 minor with 1 vote (vote)
: ---
Assigned To: Dan Sully
:
Depends on: 1463
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-26 10:01 UTC by Ben Sandee
Modified: 2008-12-15 11:57 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Sandee 2005-04-26 10:01:01 UTC
I love having the artists listed in the "new music" display!  This is a huge
improvement.

A minor issue is that when it is a various artist disc it takes the simple route
and just uses the artist(s) from the first track.

It would be nice if the artist name were changed to a localized "various
artists" in this case.
Comment 1 KDF 2005-04-26 10:39:06 UTC
This might be an argument for adding a "cd artist" field to the album table.
might this speed up grabbing artist data (as opposed to grabbing a track, then
its artist) and would build during scan, using "various" when the server finds
more that one 'artist' for an album.  Of course, the problem is then to split
artist from the other contributor types.

Comment 2 Dan Sully 2005-04-26 11:17:20 UTC
Vidur - what do you think of this?
Comment 3 KDF 2005-04-28 23:40:07 UTC
linking to 1463 since the ALBUMARTIST tag in vorbis will be part of fixing this.
Comment 4 Dan Sully 2005-08-02 23:17:43 UTC
I've added this feature as part of the 6.2/trunk tree - subversion change 3849.

Please see the link for details & file any future enhancements as a new bug.

Thanks.
Comment 5 Ben Sandee 2005-08-03 08:56:50 UTC
looks great Dan, thanks!
Comment 6 James Richardson 2008-12-15 11:57:30 UTC
This bug has been fixed in the latest release of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

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