#musicbrainz

is there any way to get MusicBrainz to write the recording ID as a tag? I'm considering building something if some other things work out and it would probably be best to have recording IDs available in metadata

@zayd: Picard will write the recording ID as file tags is all formats where it's supported by default

see https://picard-docs.musicbrainz.org/downloads/M... for details on what the tag is called

weird, mine only seem to have MUSICBRAINZ_RELEASETRACKID and MUSICBRAINZ_RELEASEGROUPID

I'm not entirely sure what format is used for FLAC but I'm probably on whatever the default was

The "Vorbis" column includes FLAC

note that the recording ID is confusingly stored in the MUSICBRAINZ_TRACKID tag

(since that field is from before Musicbrainz had separated the notion of tracks and recordings)

some songs in my library seem to have RELEASETRACKID but not TRACKID, maybe they were messed up by something other than picard?

assuming you don't have some Picard tagger script that unsets the recording ID variable, that is possible

nope, retagged and it still isn't there

elomatreb[m]: I only have naming scripts, not a tagger script

mh, weird

the recording ID shows up in Picard's GUI but isn't getting written to the file

does Picard keep logs anywhere so I can find out what's going on?

see https://picard-docs.musicbrainz.org/v2.12/en/tr...

set it to debug and it's only saying things about saving images

ok a ton of things in my library don't have that tag with no clear pattern of what could've caused it

zayd: check your scripts in Options > Scripting. It requires some effort not to write this tag.

outsidecontext[m: https://pic.t0.vc/BNNA.png as I already said, I don't have a tagger script

Also when you load the files into Picard they show up on the left pane, not the right pane? If you select one file, there is no recording ID shown in metadata?

outsidecontext[m: I assume this is what I'm meant to be seeing (not sure why it says the file's modified even though there's nothing to update) https://pic.t0.vc/ZTNN.png

This shows all the MB ID tags are in the file (original value column). Those are a FLAC files, right? Or MP3s?

yeah, FLAC

is mediainfo just reading them weirdly?

kms

mediainfo doesn't see the tags but ffprobe does

so it was just a mediainfo problem

Then there must be a MUSICBRAINZ_TRACKID tag in the file. Otherwise the original column would be empty

yeah there is, I can see it when I use ffprobe, mediainfo just refuses to read the tag for whatever reason

Yes, mediainfo is kind of special. I think it only has specific tags it reads and shows

anyways, since this is relevant to what I was originally talking about, is it a good idea to use recording IDs as identifiers for a lyric annotation database? I'm considering the idea of trying to build an open source version of Genius and I thought that using the MBIDs would be good because it'll allow better integration with stuff like Beets and Picard

currently in just planning stages, trying to write a decent file format for the annotations rn since there doesn't seem to be one already

I think it is a good idea, yes

Well,maybe more fitting would be the work ID for lyrics. Or allow for lyrics to be linked to multiple recording IDs. But having such identifiers generally seems like a good thing for a lyrics database

E.g. FanartTV and TheAudioDB also use MB identifiers for cover art. And it makes integration really easy

outsidecontext[m: why would I want it linked to multiple recording IDs? Isn't the point of a recording ID that all releases with that recording link to it?

Yes, ideally. But even if everything is perfect there often are multiple recordings of the same song.

do the work IDs include multiple editions of the same song? (like when there's an album version and a single version)

as in same title, same singer, different cut

And as it can be hard to figure out if two tracks on different releases are really the same there can be duplicates (that should or should not be merged)

Yes, work is what you e.g. talk about when talking about a certain song by an artist. There might be different length mixes, re-recordings, live versions etc. But all the same song

Trouble here is that there exist less works in the DB, and many recordings are not linked to works. Creating a work for all the recordings must be done separately and often requires additional research

But it is needed if one wants to set e.g. lyricist or composer on MB

3><outsidecontext[m> Yes, work is what you e.g. talk about when talking about a certain song by an artist. There might be different length mixes, re-recordings, live versions etc. But all the same song

I feel like this could create issues with when a song has multiple editions with different lyrics

also, timing would be off a lot of the time probably

Ah, yes. That's true, if it is for synced lyrics it should better be linked to recordings

yeah I think synced lyrics would be the most convenient for being used locally, and this would be easy to do too as I was probably going to import lots of stuff from LRCLIB, which keeps synced lyrics for a lot of songs

Sounds great

Synced lyrics are a really good reason to use MBIDs of recordings. That way it can be clear which lyrics apply to which exact version. And there can be same lyrics with different timing linked to different recordings

hello everyone

i just started contributing to various open source projects, I came to know about this when i was tagging audio tracks on VLC few days back

I felt to contribute so i hv added a release, i hv researched a lot, so if u will hv time pls review it and vote

here's the link, I am open for suggestions as i am a newbie

vaibhavparmar2377 (@_discord_1069807396773441556:chatbrainz.org) A COuple

hi

sorry, accident

I'll leave a couple of notes

okay np, thanks!

vaibhavparmar2377 (@_discord_1069807396773441556:chatbrainz.org) I left the notes, and welcome to Musicbrainz!

One final thing to note is that you generally don't need to check the "Make all edits votable" checkbox. Edits that automatically apply are easily undone, so you can't really break anything with your edits

hi, thanks u very much

oh okay, i will take care of that , i am new that's why i thought i should check that option😅

it doesn't *hurt* to check that box, but you can end up slowing yourself down if you want to do edits that depend on each other

or if you want to tag your files

in general your release is a good start

the things I left notes about are fairly minor mistakes/improvements

thanks! I will check the notes rn, tbh i am excited to join the community