#musicbrainz

Were I an auto-editor, I would use it to force-change everything in some category to be my new, preferred style and then put forth a style proposal claiming that it was just documenting current usage.

(The same goes for Norwegian hip hop/trad. stuff, CatCat.)

Freso: I don't own music

(as in, CDs and stuff)

Not here

reosarevok: Ah well. :)

hmm. I might have to bring along one of my weird extra-thick japanese jewel cases or something.

hawke_: Really??

Freso: No.

Aw. :(

Freso: that said, http://8tracks.com/reosarevok/estonian-hip-hop-...

rütm = rhythm, riim = rhyme?

yep

(that's from the lyrics to one of the tracks)

http://sasslantis.ee/lyrics-noizmakaz-monument to be precise

:)

(rytme and rim in Danish, respectively)

...

Amazing track titles right there

at least they're not Track 01, Track 02, ...

heh, yeah

heya

is mwiencek here?

bitmap --^

ty :)

LordSputnik: Any news on the recording merge style proposal? :-)

hawke_: I'm about 10 pages through the isrc handbook

hawke_; so no, not yet :P

LordSputnik: I’d just read pages 17–19 if I were you.

hawke_: but hopefully this weekend

hawke_: I want to read it properly :P

A lot of it is just talking about how to store the damn things

k

someone had to sit and write it, so it deserves to be read :P

It’s pretty decent and reasonable. Now if only the industry would actually follow it.

I think musicbrainz does actually follow the appropriate storage guidelines :)

also: http://tickets.musicbrainz.org/browse/MBS-5507

please vote or tell me why not :)

LordSputnik: right now, because we don't know

(we don't have info on the size of the full image)

reosarevok: how can we not have that sort of info? 0o

Because those images never touch MusicBrainz

i'm pretty sure the caa specification says that the '500px' image will have height and width values both <=500px

They go directly to the Archive

so we're following the spec :)

heh

In any case, we want to know (and display) the size

well, the ticket doesn't say to remove the 500px and 250px, it just says to remove the links

They're looking into how we can do it without needing to have the images ourselves IIRC

yeah - it requires that archive.org saves the image size info, and somehow sends that back to musicbrainz

can't we just store the dimensions from the upload form?

LordSputnik: the upload form doesn't know the dimensions.

the dimensions are only known after the image is parsed on the server.

what's it written in?

oh

LordSputnik: I think we should retain the links no matter the size, TBH.

Freso: but it's just wrong. If I click a 500px link, I expect a 500px image, and it isn't :P

supporting the links is good for simple clients

LordSputnik: If we're able to do proper replacements at some later date, the URL won't change, but the image dimensions may.

i.e. i write a music player that just wants to display a medium sized cover art image. I use only the -500.jpg link. Everything works, but some images might have to be scaled up.

ok, well then CAA would need to know the size of their images

kepstin-work: I'm not talking about the URL, just the text links on the cover art page

LordSputnik: Well, if you can think of a wording to say "less than or equal to 500px x less than or equal to 500px" without looking off.. :)

all those links always link to distinct images

sometimes they are images with the same content

however, all three links are always valid

^

inasmuch as they point to different URLs

Freso: just don't load the link on the page if the original size is less (obviously, once CAA sends us the info)

LordSputnik: And what if I want a 500px or less image to link to in a blog post or something?

I don't mean the url links, I mean the text links "500px" and "250px" on the cover art page on the release

huh, when were those added

your ticket is really confusing - you don't mention anything about the release cover artist display page at all in it.

edited the ticket

LordSputnik: Anyway, asking people to vote or explain why not is silly. People vote on the issues that are important to them.

LordSputnik: Obviously, that issue isn't important for a lot of people here, even if it may be for you.

Freso: Ah ok, I just thought it was vote if you think it's a good idea

LordSputnik: mind if I edit your ticket description to say this: https://gist.github.com/ea32b36d06607f2cd2bb ?

LordSputnik: Well, you obviously wouldn't vote for it if you didn't think it was a good idea. :)

I think that's a bit more clear

kepstin-work: refresh the page, i updated it again while you were writing that, it may be a bit better now

kepstin-work: "false impression" is a good phrase, could edit to include that bit, i think the rest is mostly in there now

ttyl

I think that ticket's mostly relevant to you and the people who might potentially fix it, and I suspect I'm not alone among those in the second category in thinking it's not worth the effort :P

Everything is worth the effort if there's the time to make the effort. Obviously there are many other more important tickets, but this one is there for when all others have been done ;)

ianmcorvidae, may i ping you about the mb2freedb gateway? still seems out of sync

I haven't actually gotten to updating it yet :( sorry

I have everything I need, just been working on other things

bitmap: any chance of a "guess remixer" addition to "guess featured" ?

huh, that's cool. nicovideo.jp actually stores a work 'content tree' that tracks which videos contain derivative works of what other videos.

is niconico.com still up?

indeed it is.

I wonder when that'll stop