#musicbrainz

Blockchain MusicBrainz isn't real. It cannot hurt you

Blockchain MusicBrainz:

It seems like they want to add MusicBrainz data as they made a PR to my rust API bindings. Not sure if it needs to be checked out

<thermospore[m]> "musicbrainz down everyone panic..." <- Sorry about that, it was due to maintenance operations and unexpected.

All good :)

mayhem: ^ in case it's important at some point, see rustynova's post from earlier :)

I'm not quite sure how it works nor how to contribute because it's all hidden behind buzzwords and stuff so...

It seems both pay-to-add and get paid for adding? Very confusing stuff

<reosarevok[m]> "mayhem: ^ in case it's important..." <- yeah, this dude thinks he's building all the solutions for the music industry by handing them a blockchain. kept trying to work with us, but refusing any sort of feedback about how futuile that project is. set phasors to ignore.

Ah, ok, so you are aware. I meant more in case they ever make any money

reosarevok[m]: if they do, I'll go collect some money. but I am not holding my breath, pickle or blockchain.

Definitely an over-engineered thing. However I'll gladly accept the contributions~

honestly when bands first started doing NFT-related releases, before I had any real grasp of what it was supposed to be (honestly I still don't), I thought it seemed like a decent idea — in my mind it seemed like a way to provide a more concrete form of ownership of digital copies...... not the nonsense it all ended up being

I've got my hands on this older CD (Prefab's "Jordan: The Comeback") whose disc ID is unique and doesn't exist in the database yet;

but the edition it seems to match (straightforward OG US release) *is* there, with two disc IDs already attached;

so I have to presume this is just a minor re-press of the same edition...... and if it's worth adding in another release where pretty much all the info will look identical save for the disc ID

meant to say, "...and I'm wondering if it's worth adding..."

If there is no other difference and the track times aren’t hugely different you can add the disc ID to the existing release

that's the more elegant solution I preferred 😃

I get anxious sometimes about all the older submissions in the DB that must have disc IDs attached that should have gone into other editions like box sets or anniversary editions or what-have-you 🙈

Historically MB didn’t have releases and release groups and attached all variations to a single release with multiple release events and labels

There are tons of wrong discids out there. The problem is while it is easy to verify that a disc in hand belongs to a certain release, it is near impossible to know if there is a bad discid that should be removed. There are some obvious cases with very unique pressings but that is not very common.

https://accuraterip.com/ has a database of CDs extracted with Exact Audio Copy. It would be nice if we could make use of it here at MB

Anyone have info on JonnyJD's isrcsubmit dev branch?

Wondering what it changes (and whether it has OAuth support).

zoe.division: imo, if you look at the edit history and the other DiscID’s were added way back when (in the change to NGS every discID in a group was duplicated to every release), and are attached to multiple releases, add yours and wipe the others. It’s impossible to prove a negative, so it’s the only way to eventually get everything correct

(doubling up on what others have said, but adding more explicit ‘permission’ to delete em!)