After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 566357 - ALBUMARTIST tag ignored if it equals track artist
ALBUMARTIST tag ignored if it equals track artist
Status: RESOLVED DUPLICATE of bug 557313
Product: banshee
Classification: Other
Component: Metadata
1.4.1
Other All
: Normal minor
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-02 20:31 UTC by Michel Alexandre Salim
Modified: 2009-01-02 21:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michel Alexandre Salim 2009-01-02 20:31:07 UTC
Please describe the problem:
I have an (Ogg Vorbis) album that is mostly performed by one artist, except for a track. If I edit the metadata on the tracks (from the command line, using vorbiscomment), setting the ALBUMARTIST tag, the album is still seen as two separate albums: the ALBUMARTIST tag is ignored if its value is the same as that of the ARTIST (track artist) tag.

ALBUMARTIST determines the sorting / grouping of albums, therefore it should probably be kept regardless of whether the value duplicates track artist or not.

Steps to reproduce:
1. Take an album by a single artist
2. Add (using vorbiscomment / metaflac / id3tag / etc.) the ALBUMARTIST tag, setting it to equal the artist tag
3. Change the artist tag on a single track to some random value
4. Load the album into Banshee


Actual results:
Album appears as two separate albums, as the ALBUMARTIST tag is ignored on all but the one changed track. Right-clicking on one of the other tracks show that the "Compilation Artist" field is not set

Expected results:
Album appears as a single album; all tracks have their Compilation Artist field.

Does this happen every time?
Yes

Other information:
Comment 1 Bertrand Lorentz 2009-01-02 21:29:01 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version.

*** This bug has been marked as a duplicate of 557313 ***