2 ms·
Yes, almost certainly. It's a free database created by a community for multiple different needs. Barcodes are very useful way to check you're talking about th
by ZeroGravitas 4y ago
Yes, almost certainly.
It's a free database created by a community for multiple different needs.
Barcodes are very useful way to check you're talking about the same item, similar to isbns for books. Of course many classics either have no ISBN/barcode or lots of them depending on how you look at it, and sometimes you care exactly which one you are talking about and sometime you care about the thing that they are all different versions of. This is a whole fascinating area of library science:
https://en.m.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records https://en.m.wikipedia.org/wiki/Functional_Requirements_for_...
You've not been super specific about what you're trying to achieve but there's almost certainly a chunk of the Musicbrainz community that wants the same thing and has a way of getting it from the interlinked data.
The benefit of doing it in one big super-complicated database is that the interests overlap and so the different needs have synergy, which makes the more obscure details more tractable.
I'll have a quick look at their wiki to see if I can give you pointers.
Also, they link the band's, songs, instruments etc to Wikipedia via wikidata IDs, so of you like reading Wiki text about things, they've got you covered.
- ZeroGravitas 4y agoSo, what you call "an album" or "single" is a release group, because there multiple re-issues of beatles albums, in mono, stereo, red vinyl etc. each of which is a release. They often but not always share the same recordings e.g. the US release may replace an album track with the single version or re-order tracks. You probably want to find a release of that release group that closely matches your files (e.g. is there a "bonus" track, does it have both mono and stereo versions of everything). It's not 100% vital though to get an exact match unless you care about the bonus tracks and other obscurities. The beatles are an extreme case since there's like a million demo and session versions of each song, which is why its easier to start from a release, which then points to the specific recordings used. So if you got the files from iTunes and it's the 2009 remaster then it's this one: https://musicbrainz.org/recording/2df46dec-b453-4444-91b9-5fa5d7515fd9 https://musicbrainz.org/recording/2df46dec-b453-4444-91b9-5f... Which then points to a specific recording used (the original studio mix), which was also released as a single and appeared on many different albums, listed here: https://musicbrainz.org/recording/2df46dec-b453-4444-91b9-5fa5d7515fd9 https://musicbrainz.org/recording/2df46dec-b453-4444-91b9-5f... Although that's on lots of different releases (and release groups), if anyone updates the info on that recording, it'll update for all of them. To get those track level tags you need to choose an option in Picard and there's a couple of 'plugins' for it that let you format the instrument tags in a way you want. It also lets you script the tags if you have something super specific.
- raffraffraff 4y agoI picked The Beatles because it's "hard", but also because it's the most likely candidate to have all of the metadata populated (including instruments). And it's a perfect example of why a gigantic database that tries too hard to please the 'train spotters' with catalog numbers and barcodes, is not suitable for someone who has the album version of a song and just wants to tag it. What normal person knows/cares what a release group is? Edit: "You probably want to find a release of that release group that closely matches your files". And this is why you can't just point it at your library and let it go. You need to shepherd it at every turn or it'll screw things up. I've used countless auto-taggers over the years (all of which pull from MusicBrainz) and I've never had decent results. These days I tag manually. Most of it's already done, so I just have to handle the new stuff, and sometimes update old stuff (add instruments that 'stand out', update ratings etc).
- raffraffraff 4y agoIf I'm doing it wrong after spending 15 minutes fine-tuning the Picard settings, installing plugins and googling "Picard use recording year" so that I don't get '60s re-releases on a '90s auto-playlist, and it is still producing garbage, then I don't know who this is aimed at.
- ZeroGravitas 4y agoHow did you create the 90's auto playlist? I'm reasonably certain that Picard adds this information by default without you needing to do anything, so whatever created the playlist was probably just looking in the wrong place. https://picard-docs.musicbrainz.org/downloads/MusicBrainz_Picard_v2.7_[en].pdf https://picard-docs.musicbrainz.org/downloads/MusicBrainz_Pi... > Chapter 7.1 'basic tags' > The following tags are populated from MusicBrainz data for most releases, without any special Picard settings. > Note: Some of these tags are only supported for certain file types or tag formats. Please see the Picard Tag Mapping section for details. Are you using the 'originalyear' value? > The year of the original release date in the format YYYY. By default this is set to the earliest release in the Release Group. This can provide, for example, the release year of the vinyl version of what you have on CD. If you have compilations, like film soundtrack and want each track tagged with it's original release date, then you need to tweak things, as noted in the help for the slightly more precise 'originaldate' tag > This is the same information provided in the _releasegroup_firstreleasedate variable, and is consistent across all tracks in the release. If you prefer to have this tag populated with the date of the earliest recording of the track in the database, which will likely be different for each track in the release, this can be achieved by enabling a one-line tagging script as $set(originaldate,%_recording_firstreleasedate%). > Be aware that setting this can cause a release to be scattered across multiple directories if you use %originaldate% as part of the path portion of your file naming script. edit: worth mentioning that Musicbrainz also tracks when things were recorded (i.e. when were the artits in the studio making the music), which is different again from the original release date (when it was made available for sale), so your search term may have been ambigous.