Hi all — I’m an independent Mac developer working on a new project called gr∞ves, a macOS companion app to Apple Music.
The idea is to bring back a bit of the album-oriented listening experience for people who maintain their own digital music libraries. While a track or album is playing, the app displays the cover art at large scale on the desktop and can surface additional artwork (alternate covers, booklet images, etc.), along with expanded information about the release, and more details from user tags than Apple Music exposes.
Right now the metadata enrichment side leans mostly on Discogs and the user’s existing tags, since the focus has been on edition-specific artwork and release details.
However, while building this I’ve been thinking that MusicBrainz could potentially add some interesting dimensions, especially for things like:
- canonical artist identities and aliases
- relationships between artists and works
- cross-links to other databases
- more consistent identifiers for releases across libraries
Before I go too far down that path I was curious about a couple things from the community here:
-
Do people commonly embed MusicBrainz IDs in their personal library tags (MBID, release group ID, etc.)?
-
If a tool detected those IDs in tags, would resolving additional metadata through the MusicBrainz API be useful in practice? Why for you?
-
Are there particular parts of the MusicBrainz data model that third-party listening tools tend to underutilize?
-
adding last.fm scrobble support is on the long-term road map. would users here like to see it also support ListenBrainz?
If anyone is curious about the project itself, there’s a brief overview here:
And there’s currently a small public TestFlight beta open for Mac users:
I’d especially be interested to hear from anyone here who maintains large tagged libraries or already incorporates MusicBrainz identifiers into their files — it would help guide whether MB integration would actually improve the experience.