I’ve checked these two options, but is that better or worse for me?
If these options improve tagging, I think it’s possible to permanently enable them in Picard’s code and remove their visibility in the options.
Picard does not “guess” tags.
When you do a lookup, Picard tries to make an educated guess about which MusicBrainz release your files belong to based on whatever information it already has from existing tags and file names and the count and music length of each file. It is the user’s responsibility to check whether the educated guess is correct and if not select a different Release from the same Release Group or find a completely different release.
But once, it has determined which release is best, it then downloads metadata about that release. The options you are highlighting simply control whether additional metadata about the release or the track/recording is also downloaded resulting in more metadata in more tags in your music files. But all of this metadata are crowdsourced facts rather than guesses.
1 Like
“Guessing” wasn’t the right word.
It’s obvious that it retrieves data from a database. 
The reasons that these options exist are:
- Some people only want basic data - some want more advanced data
- There is a significant extra Musicbrainz server load to retrieve related data.
1 Like
Release Relationships means add relationships attached at Release level to all the tracks.
Track Relationships means write the relationships found on a recording to the tracks.
This is what data gets written to your files AFTER they are matched.
2 Likes