[fixed] [MP2-813] Album artist filter wrong display (1 Viewer)

[ge2301]

I'm also not able to follow the discussion any more. I checked the tags by myself and all tags were correct. But I could not see ID tags anywhere. Perhaps there are some hidden infos I do not see with MP3tag

 

[azzuro]

I'm also not able to follow the discussion any more. I checked the tags by myself and all tags were correct. But I could not see ID tags anywhere. Perhaps there are some hidden infos I do not see with MP3tag
View attachment 202883

Yes, on my tagging file, you can found propper musicbrainz id, not related to standard tag.

Envoyé de mon LG-H870S en utilisant Tapatalk

 

[HTPCSourcer]

on my tagging file, you can found propper musicbrainz id, not related to standard tag.

What tagging file? I only looked at the music files themselves where I checked the artist info. Is there more?

 

[azzuro]

Mp3tag show only standard tag, if you use other software of tagging you can found more entry.
But i checked this before posting my issue, except proper musicbrainz tag.
Bit for me, MP will not use it. So I'm wrong

Envoyé de mon LG-H870S en utilisant Tapatalk

 

[henso]

In the below screenshot (Mp3tag via Extended tags dialog) you can see the tags for the "Come home" track. As you can see MUSICBRAINZ_ARTISTID tag lists multiple ID's (separated by ";") but only one name in the ARTIST tag. According to this documentation, that should be the relation stored in the tags. It seems then that Picard is not following its own documentation and is instead using the MUSICBRAINZ_ARTISTID tag with relation to the ARTISTS tag (which is new and not supported by out tag library AFAIK).

EDIT: We could support this by only using the first ID found, but then we would have to assume that the first ID is always the right one. Is that a safe assumption?

 

[azzuro]

@henso, what do you think to drop %artist% tag import when %artists% is present and maybe contain %artist% value.

second stuff; why we use musicbrainz idtag ?

and second quesiton, why the @albumartist sort view in MP don't use the Albumartist value only?

 

[henso]

@henso, what do you think to drop %artist% tag import when %artists% is present and maybe contain %artist% value.

Like I said, the library (TagLib) we use for reading tags doesn't seem to support this.

why we use musicbrainz idtag ?

Why not? It uniquely identifies the artist which is very convenient when comparing artists.

why the @albumartist sort view in MP don't use the Albumartist value only?

I'm not sure what you mean. You need to describe better what your issue is. If you think you found a bug please make a bug thread so others can confirm it.

 

[azzuro]

Like I said, the library (TagLib) we use for reading tags doesn't seem to support this.

the version from 2016 ?

Why not? It uniquely identifies the artist which is very convenient when comparing artists.

i'm ok with that, my question was only to not overcharge DB

I'm not sure what you mean. You need to describe better what your issue is. If you think you found a bug please make a bug thread so others can confirm it.

the origin of this thread was, the albumartist sort view is not respected on MP Client, it seems use artist node instead of albumartists

 

[azzuro]

@henso / @hwahrmann
maybe update taglib to latest 2.2 ?

 

[hwahrmann]

Taglib SHarp can handle Album Artists without any Problems. This is what we do for years.
If i follow the discussion correctly, MP2 is reyling on MusicBrainz Tags, for whatever reason.

Anyway, you can address MusicBrainz related fields by setting / getting:
MusicBrainzArtistId
MusicBrainzReleaseGroupId
MusicBrainzReleaseId
MusicBrainzReleaseArtistId
MusicBrainzTrackId
MusicBrainzDiscId
MusicIpId
AmazonId
MusicBrainzReleaseStatus
MusicBrainzReleaseType
MusicBrainzReleaseCountry

They all will be stored as TXXX frame.
The AlbumARtist is then store as: "TXXX:MusicBrainz Album Artist Id"

You could use MpTagthat to maintain that.