Single album option

[Luke 42077]

14 hours ago, gsites said:

Não fiz a respeito do VA, mas não corresponde a maioria dos artistas da musica.
No Plex corresponde, mas no emby não

HI there, how you have configured the metadata options in your music library?

[gsites 14]

On 3/17/2022 at 1:03 PM, Luke said:

HI there, how you have configured the metadata options in your music library?

Hello

 

[Luke 42077]

23 hours ago, gsites said:

Hello

 

Most likely the same issue as here: 

 

[gsites 14]

6 hours ago, Luke said:

Most likely the same issue as here: 

 

Probably, but how to solve?

[Luke 42077]

10 hours ago, gsites said:

Probably, but how to solve?

We'll discuss in your topic. Thanks.

[gsites 14]

I installed PLEX to do a test and with plex everything matches perfectly.

I'm not understanding the error.

[Luke 42077]

17 minutes ago, gsites said:

I installed PLEX to do a test and with plex everything matches perfectly.

I'm not understanding the error.

I think we're having the same conversation in two places now so let's please continue in your topic. Thanks.

[xe` 45]

On 9/6/2021 at 11:00 AM, Happy2Play said:

... so to group the album into a single item the tracks need same Album and Album Artist or MusicBrainsAlbumid.

The reference to `MusicBrainsAlbumid` was the thing that finally explained the mixed results I have been seeing.

Is this the only ID that is used for grouping in this way? For instance there are others like Barcode and Deezer id that would serve the exact same purpose with no practical risk of false positives.

Edited June 8, 2024 by xe`

[Happy2Play 9780]

19 minutes ago, xe` said:

The reference to `MusicBrainsAlbumid` was the thing that finally explained the mixed results I have been seeing.

Is this the only ID that is used for grouping in this way? For instance there are others like Barcode and Deezer id that would serve the exact same purpose with no practical risk of false positives.

Pretty sure this is the only method that is currently coded.

[xe` 45]

It feels like this may be a fairly accessible and reliable quality of life feature. Any objections if I raise it as as feature request.

[jiggity 35]

7 hours ago, xe` said:

It feels like this may be a fairly accessible and reliable quality of life feature. Any objections if I raise it as as feature request.

I have requested that the Discogs release ID gets used as an unique identifier.

unless there is a plugin for Deezer, there is probably not going to be a way to use deezer tags for anything, I strip them out from any releases.

Musicbrainz can't even search for barcode, and it is of limited use in Discogs, so i cannot see it being useful for the Emby back end.

[xe` 45]

I think my request would be much simpler than that. There exists a number of well defined tag fields that would uniquely groups albums without user interaction. We dont need to request any GUI control of this data, or storage of this data, only that they be used as a trigger for grouping.

[Luke 42077]

1 hour ago, xe` said:

I think my request would be much simpler than that. There exists a number of well defined tag fields that would uniquely groups albums without user interaction. We dont need to request any GUI control of this data, or storage of this data, only that they be used as a trigger for grouping.

Are you saying you have multiple albums of the same name from the same album Artist?

 Because unless you have that, then the combination of album and albumartist is all you need to group properly.

[xe` 45]

This is what it looks like without the musicbrainz tag. Notice it is splitting by Album and Artist even though all the AlbumArtist tags match

If I add the musicbrainz tag it becomes as expected

 

So here at least this doesnt work as I would expect with "combination of album and albumartist" not grouping correctly. Am I being stupid?

Edit: I will find a new clean untouched example to test with and report back.

Edited June 9, 2024 by xe`
Talkign rubbish fixed with real data

[Happy2Play 9780]

11 minutes ago, xe` said:

This is what it looks like without the musicbrainz tag. Notice it is splitting by Album and Artist even though all the AlbumArtist tags match

If I add the musicbrainz tag it becomes as expected

 

So here at least this doesnt work as I would expect with "combination of album and albumartist" not grouping correctly. Am I being stupid?

Edit: I will find a new clean untouched example to test with and report back.

I will have to try and test again with no provider data but should be just album and albumartist.

But without seeing track tags before you added MBZ tags it really is hard to say.

[Happy2Play 9780]

17 minutes ago, xe` said:

. Notice it is splitting by Album and Artist even though all the AlbumArtist tags match

What is the matching AA?  

Quote

For these types of compilation albums if you want all tracks to show up as a single entity you want to make sure both the "album" and "album artist" fields are the same for all tracks. Otherwise the album will be split up for the various artists listed.

 

[Happy2Play 9780]

Found no issue with compilation album with same album and AlbumArtist with no metadata ids 

But per the image above they appear to not have same AA.

[xe` 45]

I will get an identical set of FLACs to test with to reproduce the original condition.

Thanks for the info and help. I will do the leg work here now that I understand how this works to find out what the issue is and report back if its an actual issue or PEBCAK.

[Happy2Play 9780]

3 minutes ago, xe` said:

I will get an identical set of FLACs to test with to reproduce the original condition.

Thanks for the info and help. I will do the leg work here now that I understand how this works to find out what the issue is and report back if its an actual issue or PEBCAK.

Yes as this image suggest no AA.  As it shows different Artists per track.

[xe` 45]

I went back to the master copies and confirmed this was made confusing by my own doing. The AA is not in the master so at some point during debugging I must have tagged them but continued to work from old screenshots.

This has been a bit of a steep learning curve for me. For instance I didn't realize some tools treats ID3 tags as case sensitive e.g. `album artist` is understood by Emby and exiftool but it needs to be `Album Artist` for mp3tag leading to confusing moments of how Emby is grouping something with no AA or musicbrainz tag.

I think my proposal still has some merits though. Take the following hypothetical example:

exiftool 01-bon_jovi-ill_be_there_for_you.flac
ExifTool Version Number         : 12.76
File Name                       : 01-bon_jovi-ill_be_there_for_you.flac
Directory                       : .
File Size                       : 43 MB
...
File Type                       : FLAC
File Type Extension             : flac
MIME Type                       : audio/flac
...

Artist                          : Bon Jovi
Title                           : I'll Be There For You
...
Encoder                         : FLAC 1.3.1
Release Type                    : Album
Genre                           : Rock
Organization                    : Sony Music
Catalog                         : 88875190412
Album                           : Now That's What I Call Power Ballads Hits: The Definitive Collection
Duration                        : 0:05:44

 

This would not be grouped by Emby as it does not have Album Artist but the Catalog number would be a reliable alternate means to group as it is unique to the Album.

Other fields I routinely see that are also unique to the Album are Barcode, Catalogue Number, Deezer ID etc which all could be used for grouping trigger only when a Album and Album Artist pair of ID3 tags dont exist.

Hopefully I am not oversimplying the situation. In the interim I am manually identifying compilations in my library and fixing with musicbrainz but its is laborious.

 

 

[Luke 42077]

They still won’t get grouped without albumartist, so I would make sure to fill that in.

[xe` 45]

Yes that is the point I am trying to make. There are other unique and unambiguous fields that could be used as a fallback in the event that albumartist is not populated.

e.g. If Album exists and Album Artist is NULL AND Barcode is NOT NULL then group by barcode

 

So far in every case I have manually fixed here Barcode or Catalogue Number would have worked as a fallback. Obviously there will always be edge cases.

[Happy2Play 9780]

2 hours ago, xe` said:

Yes that is the point I am trying to make. There are other unique and unambiguous fields that could be used as a fallback in the event that albumartist is not populated.

e.g. If Album exists and Album Artist is NULL AND Barcode is NOT NULL then group by barcode

 

So far in every case I have manually fixed here Barcode or Catalogue Number would have worked as a fallback. Obviously there will always be edge cases.

True and would require database changes to add this additional information to possible group off of.  As not every possible tag is written to db.