Access MusicBrainz

This function is used to access MusicBrainz to log changes between the database and your tracks and/or save the changes.

Release Matching

Only folders where every track in the folder has the same MusicBrainz releaseID will be processed. Further, only those tracks which have a MusicBrainz Recording Id and/or a MusicBrainz Release Track Id will be processed. This is the most accurate method and allows for the import of all available data. This method assumes that all the tracks in a folder are in the same release.

Loose Matching

Only folders where at most one MusicBrainz Release Id is found will be processed. The Release Id does not have to be present in all tracks. This method is useful when you have the correct MusicBrainz Release Id in one or more tracks but you do not necessarily have the ordinal matching metadata. This method will not import the classical metadata, Disc, Disc count, ISRC, location/date metadata, Media subtitles, Recording id, Release track id, Track, Track count, Track position or Title metadata. Note that if you have sufficient metadata to not require Loose Matching, Yate will automatically disable the option.

Track Matching

Only those tracks which have a MusicBrainz Recording Id and/or a MusicBrainz Release Track Id will be processed. The MusicBrainz releaseID does not have to be the same in all tracks. Tracks which have the same MusicBrainz releaseID are processed as a group. This method is useful when you have tracks from different albums in the same folder.

You can choose to use the import settings retained in the tracks, alternately specify a saved import settings set, or specify your own custom settings. If using the retained settings, they must be present and consistant across all tracks to be examined. The custom settings table has a context menu used to change multiple entries and to access the MusicBrainz Import Settings Manager.

The action test state will be set to true, if any attempt is made to access MusicBrainz.

Yate attempts to follow the MusicBrainz guidelines for rate limiting its requests. However, there are external causes outside of Yate's control which could cause a network response of Service Unavailable (503). You can test for 503 errors by testing the numeric value of the MusicBrainz Unavailable named variable. A non zero value implies that 503 errors occurred. When Track Matching, it is possible that the count could be greater than one.

This function is only valid in a stepwise execution context. If Import Changes is selected and the mode is Release Matching or Loose Matching, the statement will be valid in immediate mode. Otherwise the statement is only valid while batch processing. Be aware that all network accesses are rate limited. When running in immediate mode if Discogs metadata is being loaded and artwork is being loaded from multiple sources, the statement may run for a while. Note that when running in immediate mode, an open Discogs Wizard or MusicBrainz Wizard window will be closed.