09-11-2020, 09:40 PM (This post was last modified: 09-11-2020, 10:00 PM by challenge.
Edit Reason: mb's terminology is not easy to grasp
)
1) there are many musicbrainz tags as you said. MPD supports these:
musicbrainz_artistid: the artist id in the MusicBrainz database.
musicbrainz_albumid: the album id in the MusicBrainz database.
musicbrainz_albumartistid: the album artist id in the MusicBrainz database.
musicbrainz_trackid: the track id in the MusicBrainz database.
musicbrainz_releasetrackid: the release track id in the MusicBrainz database.
musicbrainz_workid: the work id in the MusicBrainz database.
The files I attached above have nearly all of them populated (I did automatically with Picard), but I think "musicbrainz_albumid" is enough for the scope of this thread.
Take two releases of the same album (eg two CDs, or e.g. a CD and a vinyl) with the same title/author. Moode should show/group them as different if the musicbrainz_albumid tag is different.
I'm not asking to implement the whole release-group/release architecture, I care only about release now, aka tag musicbrainz_albumid, NOT release group.
quote from mb's docs:
Quote:A release group, just as the name suggests, is used to group several different releases into a single logical entity. Every release belongs to one, and only one release group.
Both release groups and releases are "albums" in a general sense, but with an important difference: a release is something you can buy as media such as a CD or a vinyl record, while a release group embraces the overall concept of an album -- it doesn't matter how many CDs or editions/versions it had.
When an artist says "We've released our new album", they're talking about a release group. When their publisher says "This new album gets released next week in Japan and next month in Europe", they're referring to the different releases that belong in the above mentioned release group.
MusicBrainz automatically considers every release in the database to be part of a release group, even if this group only contains the one release. When a brand new release is added to the database, a new release group is automatically added as well.
2) yes you're right. good catch. they had it, something went wrong in the naming script. fixed the previous attachment.
Yeah, but there ain't no MUSICBRAINZ_ALBUMID here, mate.
Code:
kreed@T520:~/Downloads/challenge/In Step_EK45024$ mediainfo "01 The House Is Rockin'"
General
Complete name : 01 The House Is Rockin'
Format : FLAC
Format/Info : Free Lossless Audio Codec
File size : 565 KiB
Duration : 32 s 26 ms
Overall bit rate mode : Variable
Overall bit rate : 145 kb/s
Album : In Step
Part : 1
Part/Total : 1 / 1
Track name : The House Is Rockin'
Track name/Position : 1
Track name/Total : 10 / 10
Performer : Chris Layton (membranophone and percussion);Tommy Shannon (bass guitar);Stevie Ray Vaughan (guitar family);Reese Wynans (keyboard);Stevie Ray Vaughan (vocals)
Composer : Stevie Ray Vaughan and Double Trouble
Label : Epic
Genre : Test
Recorded date : 1989
ISRC : USSM18900387
MUSICBRAINZ_RELEASEGROUPID : 889b20e8-c7e6-3f77-bced-31667be37b57
ORIGINALDATE : 1989-06-06
ORIGINALYEAR : 1989
RELEASETYPE : album
BARCODE : 0208313823274
RELEASESTATUS : official
ENGINEER : Jim Gaines / Richard McKernen / Richard Mullins
MIXER : Jim Gaines / Dave McNair
PRODUCER : Jim Gaines / Stevie Ray Vaughan and Double Trouble
ALBUMARTISTSORT : Vaughan, Stevie Ray and Double Trouble
CATALOGNUMBER : EK 45024
SCRIPT : Latn
RELEASECOUNTRY : US
MEDIA : CD
ARTISTSORT : Vaughan, Stevie Ray and Double Trouble
ARTISTS : Stevie Ray Vaughan and Double Trouble
MUSICBRAINZ_RELEASETRACKID : 2f06aafb-728a-37a7-b24c-15e7f2061c1d
Album/Composer : Stevie Ray Vaughan and Double Trouble
FileExtension_Invalid : flac
...
Fascinating. I can confirm. First time I've seen a swing and a miss from mediainfo.
Out of the 7 MUSICBRAINZ_... IDs recorded in the metadata tag of the track I examined, only two are reported by mediainfo. Never noticed before because I've never had an occasion to work with MB database info.
Too bad, because unlike metaflac it's a more or less a "universal format" tool.
FYI, here's what the mpd protocol reports for one of your tracks:
Code:
currentsong
file: SDCARD/In Step-albumid_tags/In Step_EK45024/01 The House Is Rockin'.flac
Last-Modified: 2020-09-11T18:50:47Z
Genre: Test
OriginalDate: 1989-06-06
MUSICBRAINZ_ALBUMID: 78cd46b0-d661-3e57-81c8-fcfd54b4b391
Performer: Chris Layton (membranophone and percussion)
Performer: Tommy Shannon (bass guitar)
Performer: Stevie Ray Vaughan (guitar family)
Performer: Reese Wynans (keyboard)
Performer: Stevie Ray Vaughan (vocals)
MUSICBRAINZ_ALBUMARTISTID: e3c8b0c8-3fa0-464b-b1f5-119cb52d3817
AlbumArtist: Stevie Ray Vaughan and Double Trouble
AlbumArtistSort: Vaughan, Stevie Ray and Double Trouble
Label: Epic
Album: In Step
Date: 1989
Disc: 1
MUSICBRAINZ_TRACKID: 98ade8e0-2681-4896-b3ae-5fc44cab7d2c
MUSICBRAINZ_ARTISTID: e3c8b0c8-3fa0-464b-b1f5-119cb52d3817
Artist: Stevie Ray Vaughan and Double Trouble
ArtistSort: Vaughan, Stevie Ray and Double Trouble
Title: The House Is Rockin'
MUSICBRAINZ_RELEASETRACKID: 2f06aafb-728a-37a7-b24c-15e7f2061c1d
Track: 1
Time: 32
duration: 32.026
Pos: 63
Id: 64
OK
This is mpd v0.21.24 (which echoes "OK MPD 0.21.11" because the protocol version increments more slowly than the software version; a source of confusion.)
Note that MPD is pretty cavalier about the case of labels. Fortunately, the mpc commands and also the protocol commands seem to crush the case, so "mpc list MuSiCbRaInZ_aLbUmId", "mpc list musicbrainz_albumid", and "mpc list MUSICBRAINZ_ALBUMID" all return the same list; similarly for the protocol list command.
09-12-2020, 09:09 PM (This post was last modified: 09-12-2020, 09:14 PM by challenge.)
ok thank you for the test, wasn't at home. It seems they're fine? (the "test" in the genre tag was intentional)
Interesting info on the tag case handling.
Getting back on track, I edited the files and added a comment tag too, so now I think they are useful for the scope of this thread.
@Tim Curtis
this should be the definitive version
remember these have the real music tags, but they are 1kHz test tones.
to recap since it's getting pages long...
Moode should also use the musicbrainz_albumid to form the unique album key, as you were saying previously.
Once grouped by that, moode's library would show them as two separate albums, albeit with same name. (while keeping the sorting options in appearance or people get angry)
The comment tag should then be readily available somehow in the UI, we could use that to distinguish them in the library view.
As today the de facto standard seems to store these kind of info in the comment, even though musicbrainz talks about catalognumber tag, but that's not supported by all formats/players nor mpd as now.
This feature would help not only to distinguish between releases of the same medium, but also between CDs / web releases / Vinyl rips of the same album as long as they have an unique musicbrainz_albumid / the correct musicbrainz tags.
Note, i don't like musicbrainz too much, but since mpd is supporting those fields I think that's the way to do it.
maybe useful from picard docs, musicbrainz tag mapping in the various formats, as posted also by @TheOldPresbyope :
__________
(same files as post #19, just added comment tag)
these are the two folders inside the zip. they are same album but different release, some of the differences are:
folder "In Step_4633952"
catalog number: "463395 2"
musicbrainz_albumid 87fc0ed7-e0d9-4df6-91d0-a3950099bbde
comment: "Catalog number 463395 2, if you can see this in moode then it's working correctly."
folder "In Step_EK45024"
catalog number: "EK 45024"
musicbrainz_albumid: 78cd46b0-d661-3e57-81c8-fcfd54b4b391
comment: "Catalog number EK 45024, if you can see this in moode then it's working correctly."
Regarding the metadata mapping table, we have no control over the mpd plugins. I've been creating a corpora of test files to see what gets mapped into what by them for MP3, FLAC, M4A (with ALAC), VORBIS/OGG, VORBIS/OPUS, WMA encoded/formatted audio tracks. Obviously the FLAC and the VORBIS formats would be expected to be treated the same since they all use the VORBIS COMMENT_BLOCK to contain metadata, but the others may be interesting
I got sidetracked by the multiple-genre issue but that seems to be settled now.
