MusicBrainz
MusicBrainz supplies structured music catalogue entities and relationships through separate search, lookup and browse operations.
MusicBrainz organizes music information into entities such as artists, recordings, releases, release groups and works. Its relationships let a library describe more than one title string attached to an audio file.
Three operations ask different questions
| Operation | Original example question |
|---|---|
| Search | Which artists or releases match these words? |
| Lookup | What does this known entity identifier describe? |
| Browse | Which releases are related to this known artist or recording? |
Searching by an album name can produce several candidate releases. Selecting an MBID gives a particular reference for later lookup; browsing then explores connected records.
The distinction matters when the library already has a reliable identifier. Repeating a broad name search can reintroduce ambiguity that the selected identity had resolved.
Recording and release data serve different actions
An invented recording, Platform Lights, appears on a standard album and a compilation. Both releases refer to its audio relationship, but each can have its own track order, credits and product information.
MusicBrainz identifiers explains those entity levels. A fingerprint-assisted recording match does not necessarily choose the album release whose cover belongs to the local files.
In Emby music matching, local tags and the selected provider relationship should agree at the intended level. Music naming guidance gives the product context; the provider model explains the meanings of those references.
Related information is not always in one response
A lookup can request supported related information through the API's inclusion mechanisms. Browse and search also have their own result sets and pagination relationships.
A short response can consequently be complete for its requested shape while omitting data that another operation would retrieve. Absence from that one response does not prove the catalogue lacks the relationship.
A useful integration retains the request scope with the response, including entity, requested additions and language/format context where applicable.
A catalogue reference is separate from a media resource
MusicBrainz metadata describes music relationships; it is not the local encoded song. Artwork retrieval also has an associated-resource boundary, and the correct release or release group matters there.
Imported descriptions can coexist with embedded cover art and edited library values. Matching the catalogue entity is the basis for selecting related data, rather than an instruction to replace every existing resource.