Music Assistant
How does Music Assistant fetch the metadata for my music? #543
Replies: 6 comments 27 replies
-
|
Thanks for that detailed info @marcelveldt I would just like to show this example where it does not seem to align with what you have written above about matching albums. This isn't a problem for me as I am not seeing lots of duplicate entries but I just wanted to highlight it in case it is not your desired behaviour. In this first image I have selected ARTISTS>>ABBA. I only have one CD on my NAS which is called The Definitive Collection https://musicbrainz.org/release-group/e2996feb-86b9-3550-88ec-f1c9c9af3961 As far as I can tell this Album is NOT on Spotify. However you can see some but not all tracks have matched: |
Beta Was this translation helpful? Give feedback.
-
|
This is possible because the same tracks (as in same recording with same isrc or MusicBrainzRecordingId) can be used on different albums. If you would open the context menu for one of those tracks and go the details, I'm pretty sure you will find that this is exactly the same track (you can verify with the preview buttons). So a track can belong to 1 or more albums) In this case that is pretty obvious because "The Definitive Collection" is a Compilation. It contains tracks from previous albums. It can also happen for various artists Collections, such as "Best Hits of the 80s". In that case such an album contains tracks from many artists (and albums) and the track linking will work too in that case. It is exactly the same as Spotify's own track linking for tracks within playlists. Does that make sense? |
Beta Was this translation helpful? Give feedback.
-
|
Yes it does and I’m happy with that as it removes duplicates. I guess I am just wondering if it is an issue that some but not all tracks matched? And whether those two entries that look like a case mismatch is worth fixing or able to be fixed! |
Beta Was this translation helpful? Give feedback.
-
|
It is all "lazy" so maybe just click one of the tracks and see if it matches ?
|
Beta Was this translation helpful? Give feedback.
-
|
I’ve seen that before but now I am seeing SHOW INFO not REFRESH ITEM? Edit. Actually found it top right. So that seems to refresh the artist. Don’t think I can just refresh a track |
Beta Was this translation helpful? Give feedback.
-
|
Yes cool I can see that refresh is doing something but no change to the other entries…. |
Beta Was this translation helpful? Give feedback.
-
|
What exactly is the issue that you still see ? Do note that it possible that there are no matches on Spotify for the isrc's of your local files. |
Beta Was this translation helpful? Give feedback.
-
|
Mainly just wanted to make sure you were happy this was working correctly. Maybe the two that didn’t match on case (if that indeed is the problem)? |
Beta Was this translation helpful? Give feedback.
-
|
Yesterday I fixed that "case issue" but I'm not sure it will be corrected if it is already wrong in the db. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I just can’t tell how “exact” the match is. For their most popular songs when there are a lot of options in Spotify it is matching but other with less than 10 options it isn’t. See below for an example. Can I do any refreshing anywhere to see if that case issue resolves? |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
Yes FLAC does. Tag your files with Picard and you will be all set |
Beta Was this translation helpful? Give feedback.
-
|
You're right and that's exactly what I did. There are tons of contradictory information out there : your approach seems to be the most consistent one (relying only on tags) but I admit that the "self management" of Jellyfin was easier to start with. |
Beta Was this translation helpful? Give feedback.
-
|
My YouTube music doesn't display the metadata or artwork. My entire flac library is what I've uploaded and it has properly embedded metadata and art that is recognized in the YouTube interface fine. When playing through MA is only shows the song title on my Google displays. How can I correct this? |
Beta Was this translation helpful? Give feedback.
-
|
You can still share your library locally. MA will then link to the YouTube tracks. Your playlists will be visible but when the tracks are played the local tracks should be used. |
Beta Was this translation helpful? Give feedback.
-
|
Smells like another inconsistency in YTM. This would require a fair amount of work to support 'personally uploaded songs to YTM' and to be honest it's not something that is high on my priority list. Like @OzGav mentioned, the local file system provider is the way to go for your flac library. I would say, please hang on until there's a fix for your large playlist |
Beta Was this translation helpful? Give feedback.
-
|
What is strange, is the first song displays the metadata fine on the google hub devices (except album art). The following songs all report the song title properly, but the artist is always "Music Library Uploads". Yet in the music assistant queue, it displays all the proper metadata (artist, album, song title) including album art. |
Beta Was this translation helpful? Give feedback.
-
Am I waiting for something on the music assistant end for the large playlist support? The same playlists work fine on my Android based sony walkman that i use for playing the same flac/hi-res files in my work office. I feel like my home assistant OS running directly and alone on my slightly older i5/8gb dell optiplex should be capable hardware for this function. |
Beta Was this translation helpful? Give feedback.
-
|
As I said in your other question if MA is failing to load your playlist beyond 800 songs then open an issue. There are people with playlists bigger than that where it works fine so look at what is maybe causing a problem. Marvin said above that “personally uploaded songs” are not currently supported. If that is the problem then open a feature request. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Marcel, I have a question about duo released albums. I tried to implement the 'albumartist' tag as : "duo name; artist1; artist2" I have 3 different artist folders on the share: "Miss Kittin", "Golden Boy", "Golden Boy with Miss Kittin". For the folder "Golden Boy with Miss Kittin / Or" i can put the album metadata. In Picard I change tags like below: I already tried several solutions but in the end some metadata gets messed up. Any suggetions? |
Beta Was this translation helpful? Give feedback.
-
|
It should be listed under Ellen Allien as well which it looks like it might be (based on the first image) |
Beta Was this translation helpful? Give feedback.
-
|
If it’s not it might be because of the problem I mentioned. Look in the logs for errrors |
Beta Was this translation helpful? Give feedback.
-
Yes, it is only listed under 1 artist, in this case Ellen Allien. |
Beta Was this translation helpful? Give feedback.
-
|
Although there is the strange behavior that some tracks seem to be recognized for both artists e.g. Track 11 'Rippin Kittin'.
In this case the artists 'Golden Boy' and 'Miss Kittin' are individually listed for this track.
For another album (Or) they are not both listed, just 'Golden Boy' for album and tracks. |
Beta Was this translation helpful? Give feedback.
-
|
You will need to do a careful examination of the tags. If they are identical but MA is behaving inconsistently then open an issue. |
Beta Was this translation helpful? Give feedback.
-
If you have local musicfiles (e.g. mp3 or flac files) it is very important that the ID3 tags are correct on your music files. Based on these tags, your music will be loaded into Music Assistant with the correct name, metadata etc.
You can use an ID3 tag editor such as MusicBrainz Picard to correct/set the tags on your music files.
For online music sources (e.g. Spotify) the metadata are retrieved from the music provider(s) itself.
Basic metadata
title: read from "title" ID3 tag, fallback to filename if the tag is missing.
version: parsed from the title. For example "My great song (live version)" will be parsed as title "My great song" and version "live"
track artist(s): The Track artist(s) will be read from "artist" ID3 tag. Multiple artists are allowed in that field by a few common separators (e.g. semicolon). If no artist ID3 tag is present, it will try to parse it from the filename (e.g. artist - title.mp3).
album title: The album title will be read from the "album" ID3 tag. A track will NOT be assigned to any album if the album tag is missing. Just like the track title, the version of the album will be parsed from the title.
album artist: The Album artist(s) will be read from the "albumartist" ID3 tag. Just like regular track artist(s), this accepts multiple artists with the common separators. If the albumartist ID3 tag is missing, the whole album will be assigned to "Various Artists.
Album type: If there are 5 tracks or less within an album, the albumtype will be parsed as "single". If most/all tracks of the album have different artists, the album version will be set to "compilation". In all other cases the type will be set to just "album".
isrc: will be read from ID3 tags if present. ISRC is used to match tracks on streaming providers. If no ISRC present we fallback to exact name matching. Having ISRC on the ID3 tracks saves a lot of comparing and thus is faster. I recommend to have it when you have streaming providers and files (but things will work without).
disc and track number: will be read from ID3 tags if present.
some other metadata will be read too from the ID3 tags if present, such as lyrics, genre(s) and copyright. In fact all tags that are supported by the "Tinytag" python library used under the hood.
Images and additional metadata
If the musicfile contains an embedded image, that is preferred as main image and copied over to the album as fallback.
If the music is stored as "AlbumArtist\Album\song.ext" file structure, we will look for additional metadata there.
If we did not find additional metadata stored within folders or the source is a streaming provider, we will fetch the additional metadata from online sources such as fanrt.tv and the audiodb. To not stress those providers with useless requests we only fetch the metadata in a lazy manner. Only when view the details of an artist or album or when you play one of the tracks, this metadata will be fetched. This means that when you do not have local metadata you will slowly get this metadata filled into the db.
If there is an Artist folder found, we check for images there, like fanart(s), logos etc. If there is an artist.nfo file found, we grab the additional metadata from there. We follow the pattern from Kodi here
If there is an AlbumArtist folder found, we check for images there, like cover(s), discart etc. If there is an album.nfo file found, we grab the additional metadata from there. We follow the pattern from Kodi here
We do not (yet) store any online fetched metadata into the folders on disk but this might be something for a future release to add (with a toggle to enable it).
Matching Artist/Album/Song on multiple providers
If you use MA with multiple music providers we match the same items on multiple providers. We do this by strict matching.
For each track we store a reference for each quality. You can have the same song but with different qualities. For example losless FLAC file on disk but compressed ogg vorbis on a streaming provider. When playback is requested of a song, we always sort by quality and availability meaning we prefer the highest quality.
matching artists
matching albums
matching tracks
Correcting changes
If you've spotted some errors in the metadata from your files, e.g. an album attached to the wrong artist, you can correct the issue with a ID3 tag editor. This change will be picked up by MA on the next sync interval.
Sync of library
MA syncs the library items of the streaming providers and the files on disk to the database. The first time this sync runs this takes a lot of time (depending on hardware and collection size) because MA has to read all tags from the files which is slow. This is one time only. Once the first sync is completed, MA switches to delta syncs which only take seconds. If teh initial sync gets aborted somehow by accident, the sync will continue where it left off.
The MA (delta) sync runs every 3 hours. This is a very fast sync because only items with a changed checksum are processed. For the filesystem provider this means that the timestamp changed. The delta sync
You can trigger a manual sync by simply reloading the integration or HA. Besides that you can trigger a manual sync within the library view (e.g. Artists) and click the menu button on the top right (the 3 dots).
It is not possible to force a full sync / rescan but that should not be needed in normal circumstances.
If things are really wrong and you need to start over, you can remove the integration and re-add it, which will wipe the database. Only do that as a last resort because you will loose all metadata in the database including playcounts and normalization data.
Beta Was this translation helpful? Give feedback.
All reactions