Application icon

Search Discogs/MusicBrainz


This action is used to interactively search Discogs or Musicbrainz attempting to match releases and import metadata. The action can be run in immediate mode or via the Batch Processor. Four actions are provided:

Search Discogs
The action you call to search Discogs.

Search MusicBrainz
The action you call to search MusicBrainz.

Search DCMB
This is a helper action and should not be directly called.

Search DCMB - Config
This is the configuration action. While it may be directly called, it is automatically called by Search Discogs and Search MusicBrainz if configuration has not occurred or if the Option key is held down when the actions start.


The following is a description of the configuration questions:

Do you want the actions to work with the selected files or should all loaded files be used?

This setting is only used when running in immediate mode. When running in the Batch Processor all files in a given folder are processed. The choices are to use all loaded files or only those which are selected..

Using the picker control choose how files are grouped into releases. Each release will be issued a separate search.

The choices are:

Treat all files as a single release
No metadata is used in grouping tracks. All processed files are treated as a single release.
Group releases based on the album metadata
Tracks are grouped by the contents of the Album field.
Group releases based on folders
All tracks in any given folder are treated as being part of the same release.

When running in the batch Processor the grouping mode is always Group releases based on folders.

You must specify when a group of files has sufficient metadata to be ignored by this action.
If you choose 'Process all files' you will search for all releases.
If you choose 'Ignore files which have release IDs' and all files have a consistent non empty release ID, the files will not be processed.
If you choose 'Ignore files which have all access IDs', files will be ignored if they have consistent release IDs and sufficient metadata to correctly identify track associations.

The choices are interpreted as follows:

Process all files
Releases are never deemed completed. Always search.
Ignore files which have release IDs
This choice evaluates Discogs Release ID or MusicBrainz Release ID and checks to see if they are consistent across all files.
Ignore files which have all access IDs
The preceding Release ID test is performed. In addition Search Discogs will determine if there is a non empty Discogs Release Ordinal Position and Track Position UDTI. Search MusicBrainz will determine if there is a non empty MusicBrainz Recording Id.

Unfortunately Discogs does not return disc and track counts when searching. This action can populate those fields but it takes one request per search result. You can elect to have the action get the additional information or not.
When the extra information is being downloaded you will see a progress message on the main window's and database's status bars. You can stop the downloading at any time by holding down the Option button until it stops.
Do you want to extract Disc and Track information?

It's easier to associate releases when you have the track and disc information. Discogs does not include this information in the search results. The action can fetch the information ... but it's slow as it is in the Discogs Wizard. How this works will become more evident in the workflow discussion.

After selecting a match, IDs identifying the release will be imported.
It is typically possible to import release specific metadata and it may be possible to import track specific metadata as well.
Do you want to import metadata other than the release IDs?

After a match is made the action will import the release and master IDs for Discogs and the release and release group IDs for MusicBrainz. Quite possibly additional metadata can be imported.

After selecting a match, IDs identifying the release will be imported.
It is typically possible to import release specific metadata and it may be possible to import track specific metadata as well.
You specify the metadata of interest in an import set named 'Search Discogs Import Set' or 'Search MusicBrainz Import Set'. You can manage these sets via 'Actions>Manage Import Sets'.
Do you want to import metadata other than the release IDs?

You're only asked this question if you elected to import additional metadata. A 'loose' download should always work but can only download metadata which is not unique for each track. A 'full' download must match tracks in order to download per track metadata. 'loose' or 'full' both require that you have configured a Discogs or MusicBrainz import set to discribe what metadata you want to import. The sets must be named Search Discogs Import Set or Search MusicBrainz Import Set. The action will import these sets automatically when installed and they will initially import all metadata except the retained import settings. You can change the import sets to import whatever fields you're interested in. Not that the preferences settings for Discogs and MusicBrainz may also affect what or how metadata is imported.

If you skip a release, you have the option of saving a UDTI to the files to indicate that they've been skipped. One of the following two UDTIs can be written:
Skipped by Search Discogs
Skipped by Search MusicBrainz
Note that some file formats will write the UDTIs all in upper case. The action accounts for this.
If you actually write data to the files, the appropriate UDTI will be removed.
Do you want to write these UDTIs to the files in the event that a release is skipped?

At various times when the action is running you can elect to skip a release. You have the option of writing UDTIs to the files so that subsequent runs can test for the skipped state. During execution, the UDTIs are removed if metadata is imported.

You can choose to ignore or honour the 'Skipped by Search ...' UDTIs. Note they are always ignored if they are not set for every track currently being processed.
Do you want to ignore the 'Skipped by Search ...' UDTIs?

When executing you can choose to not process any track grouping which has a skipped UDTI in every track or to ignore ignore the skipped UDTIs and process the files.

... and last but not least ... you have the option of automatically saving the changes made to files.
When running in immediate mode and changes are not automatically saved you can review what is done and revert the files if desired.
When running in the Batch Processor changes will always be saved if the Batch Processor's Auto-Save option is enabled.
Do you want to automatically save changes made to the file?

When running the action in immediate mode not saving the changes allows you to view what was imported and to revert the files if desired. When running in the Batch Processor, if you choose 'do not save', teh changes will still be saved if the Batch Processor's Auto save files option is set.


The workflow proceeds as follows:

Content List:

Action: Search DCMB

Action: Search DCMB - Config

Action: Search Discogs

Action: Search MusicBrainz

Discogs Import Set: Search Discogs Import Set

Export Set: Search Discogs

Export Set: Search MusicBrainz

MusicBrainz Import Set: Search MusicBrainz Import Set


Yate v6.0.2


2020-07-01  v1.0 Released to Preview list.

2020-07-07  v1.1 First general release.

2020-08-10  v1.2 Changes for Yate v6.0.1.

2020-09-13  v1.3 Added documentation link.


Back to Yate Resources