#musicbrainz

SothoTalKer: a sibling label is just a different word for a sublabel, isn't it? I mean, unless they literally create a second company, it's just an imprint of the first label

reosarevok: it isnt. unless you consider parents to be siblings aswell. ;)

sometimes/often companies use different sub-labels for different genres of music, those sibling-labels are currently only connected by their parent-label

well, labels have always been the poor cousin of musicbrainz, so meh (:

catalog numbers can be emoji, right?

context: I'm working on my next "hit" single, Electric Vuvuzela Baghorn, and I'm thinking of "🔌🎈🎺🔊" for the catalog number

🤔

Getting ready to release my new album, ""

elomatreb[m]: really? I've thought about doing something like that, but I haven't bothered yet

No, just joking, sorry :)

that's too bad, I was looking forward to hearing it

dseomn: AWESOME

also afaik catalogue numbers are freetext so yes emoji?

barcode has to be a numeral value thoguh, but like, it's a barcode :D

anyway for a non-excisiting space named release, there might be some esoteric unicode that lets yo udo that withouth stripping it away

but, alas "" will probably just be considered "[untitled]" :/

unless "" <-- is the exact title (ie double qutationmarks)

my favorite unicode code point for messing with field validation is MONGOLIAN VOWEL SEPARATOR

.3.

it looks like a zero-width space (i.e., nothing), but it doesn't register as whitespace, so it's not usually trimmed

awesomesauce

I like VARIATION SELECTOR-15

it is intended to turn those icky colourful images int oproper font emoji (black and white)

ooh, I haven't used that, but I like the goal

:D

if you do use 🔌🎈🎺🔊 as a catalogue number, please use it!

please don't

SothoTalKer: sush

I'd rather have color emoji for this specific release

aw

well i see it as black and white anyway :D

whne is it getting released?

if I ever make a sequel to "Sweet Suites, Volume 1", I hope it has a Unicode Suite, which I can do all sorts of stuff with ;)

Someone should make a release with titles consisting exclusively of empty strings, NULL bytes, PUA codepoints, etc

literally iching?

videos are good to go, I'm doing (hopefully) final audio review now. still waiting to hear back from one person about the dedication, and still need to do cover design

if you want a suggestion for covers. Fish is always good

Mojibake-as-Artists-Intent

🐟️

fish!

𓆟 𓆝

🎣

🍣

fish

that's sushi

(A story in three emoji)

CatQuest: I took photos of the horrendous instrument, so those will probably be the main feature of the cover. it's just a matter of picking which photos and laying them out and stuff

made with fish, but also other things

dseomn: neat

elomatreb[m]: I fully intend to include mojibake if I ever write and release Unicode Suite

emoji-bake?

:DDDD

nice

Looking forward to ID3v2.3 tags with non-UTF-8 encoding finally going away

there was a time when catalog "numbers" where meant to exist, so releases can be easily found and sorted, not to display some strange artistic freedom

SothoTalKer: sush

it's a database field… I play with those

!m dseomn

You're doing good work, dseomn!

❤️

If catalog numbers were enough for releases to be easily found and sorted, MBIDs would be superflous

elomatreb[m]: exactly!

I mean, at least my catalog numbers are unique, so far. combined with my label MBID (but not name), they're reasonable-ish for finding and sorting my releases

in a way, they are. just another identifier like barcode or discogs id :p

that's actually a good point

Plenty of the big labels just use numeric sequences for their catalog numbers, so they easily collide given enough time

you probably had to be more creative with the label name then. just add some emojis to it, maybe?

SothoTalKer: my label name is [no label]

the "numeric sequences" are actually part of the barcode ^^

catalog numbers are many decades older than barcodes though, right?

these days, yes often. esp things liek universal. the cat# is a section (r the whole) ean/barcode thinger

but back in the day, this was not true

it really depends on the label, yes

Yeah, and even EANs/UPCs will collide simply as a result of not being long enough numbers

and recency

like 20 year old releases can have a barcode and catalogue# hat is totally not the same or even a section of

actually, in theory, there should be no collisions at all

in theory you liek music SothoTalKer

there's a solution to the collision issue: https://musicbrainz.org/release/ef83d7bf-10c3-4...

If you assume the assigning body for the codes is eternal and vigilant, and stops issuing IDs altogether once they run out