#musicbrainz

no problem!

can you perhaps ping bitmap about them?

I can try to have a look, but I can't guarantee it will be soon

bitmap: ping

done :-)

a track with different parts should be named how? Main title: foo / bar / ... or Main: foo, bar, ...

_5moufl: http://musicbrainz.org/doc/Style/Titles/Multipl...

:)

n

I'd probably go Main Title: Part X: Subtitle, Part Y: Subtitle (if parts are numbered/marked) or Main Title: Subtitle / Subtitle as reosarevok said.

Oh, just realised I'm a bit late

heh

Why are there no aliases for RGs?

They're abstract entities

They definitely should have them

someone once said releases are aliases for release groups

Pfft

:-)

http://www.discogs.com/viewimages?release=1228052 yeah sure

I have about 40 no-votes in my INBOX for BBC reviews o_O

heh

I guess that's good :p

mostly by monxton, who does an amazing job checking classical reviews

I suspect it will be *much* more in 7 days

I guess so, too :-)

but it means I can't handle it by my own, so I will just add the reviews to the wiki, for volunteers to check/correct

Sounds fine

BBC seems to have reviews for multiple albums

I just linked them to every RG they are about

Multiple albums?

but on the BBC side of course there should be either no tracklist or tracklists of all albums. But I guess it is so unimportant that no one there will spend much time implementing...

reosarevok: yes, Pseudo-Release = alias then :-)

Yeah, but pseudos are... crappy

yes, terrible

I wish they were integrated like on vgmdb

their solution is beautiful

multiple tracklists on one release, yeah.

kepstin-netbook: yes!

Can I haz link?

?

To one of those releases

In vgmdb

reosarevok: http://vgmdb.net/album/21751

very simple, but it is nice

Yeah, that's a good design

Huh

kepstin-netbook, so, do that for the browsing page :p

I suspect it wouldn't be too hard to do it in MB

It can load the pseudo-releases

(as they'll be linked to the right release)

And display them like this

but a schema change would be required (move script/language to tracklist table)

hrglgrmpf, not really

:)

Well, depends how much you want

what? "not too hard"?

Pseudos are not necessarily a bad thing - they're useful for tagging and can store useful info

Say, script/language

If we had a browsing page

We could keep pseudos in MB as tools

yes, I want to move script/language to the tracklist

But display them integrated

In the page which we used to actually browse and see stuff

hmm, that could actually work fairly well

they are actually bad, because say we have 8 versions of a release (with different cat/barcode), we would need 8 different pseudo releases as well

to get the right cat/barcode

they are terrible

make release list pages simply not display pseudo-releases, other than as alternate tracklists for real releases

hrglgrmpf: it would follow the 'transliteration/translation' ar

and imo psudo-releases shouldn't have cat no, label, etc. anyways

hrglgrmpf, http://musicbrainz.org/release/cec3ac43-3c4b-41...

That's one of the ones I just added

because they're not real releases :)

As you see, I left it pretty much empty

If it was me, I'd just block entering any of that info if pseudo-release is selected

yeah.

would need a style proposal to do that, of course.

Sure

nikki, opinions?

reosarevok: well, you couldn't stop me from filling out the missing information :-)

I've seen edits voted down (I think also by nikki) that tried to remove information from Pseudos

hrglgrmpf: yes - you would be blockedfrom entering it in the release editor.

hrglgrmpf, unless we block entering that if pseudo-release is selected

As in, graying out all the fields

well, it is still bad

Why?

hrglgrmpf: well, in this way pseudo-releases are /just/ holders for alternate tracklists for real releases

why not multiple tracklists per release?

so a tool takes a real release, follows the ar, grabs the tracklist

hrglgrmpf: that requires major schema changes

What's the plan/priority with multiple tracklists, anyway?

I don't think major

Aw :(

jacobbrett, that's what we're trying to think about

We were considering having an actual "frontend" page to MB

(which would be prettier and less full of menus and with no editing weirdness

)

picard could easily gain support for handling pseudo-releases like this as well

frontend...?

kepstin-netbook: yes, it could...

jacobbrett, a "read-only" page, so to say

Ah, I see...

Where we display data, but don't change it

I don't like the "read-only" thing too much... I think the SoundUnwound approach is best

What's that approach?

So more "glossy" and hide all the "edit X" links etc.

they have two modes for the same page

in editing mode you get all the editing links, and in viewing mode you see the normal page

http://people.scs.carleton.ca/~cwalton3/temp/mb... - fear my glossy page design mockup ;)

kepstin-netbook: it looks very nice I think!

That's why I want to try to get kepstin-netbook to be a GSoC student this year for such a frontend

On actual separate page VS. different view mode, I don't mind either

other sorts of things we could do on a page like this is embed youtube/soundcloud links as inline players, show wikipedia descriptions, etc.

Ah, kepstin-netbook--I like your "expand" solution

artwork should go full size lightbox-style, or something

hmm, and that would open up a slideshow style browser that lets you view all the images if there are multiple. good idea.

Awesome! Also, for the wishlist: http://www.playdar.org/ support ..pre-NGS had a plugin available

jacobbrett: that's a niche thing, far better served with a greasemonkey script than in a sort of general audience browsing page.

Ah, that's what I was using...Greasemonkey..tied into Playdar/Tomahawk

jacobbrett: click the 'edit' button on the top of http://people.scs.carleton.ca/~cwalton3/temp/mb... - I was playing around with the inline editor idea.

not perfect, and I'm not sure how it would map to releases, but yeah.

kepstin-netbook: I think I'd rather not merge editing and browsing in the same page like that - although I have to say it looks really cool

but yeah, with the initial idea of this glossy browsing page, there will just be some 'edit on MusicBrainz' links scattered around.

reosarevok: I think it's a way better idea than the current release editor.

the page switching is ridiculous.

heh

kepstin-netbook: that's what we original tried for the release editor

it didn't come out very well

Hmm, I guess you could do a similar planel for a release, as well as inline edit panels for each medium, though it might be better to do it all on a separate pagee...perhaps with a nifty animation that slides over to an edit screen or something

it's recording associations that are the most problematic

i'd do recording associations in the tracklist similar to how artist associations are done in the artist credit editor, imo

not sure how well that would work out, exactly.

hi everyone

Hi!

Hi!

I was wondering: how should you (or even would you) add an unknown singer to a recording ? I have a blues album where performers are identified but for a singer who (from what I read on the Internet) has not yet been identified by biographers...

Sekhmetouserapis: we have a special artist named "[unknown]" that we use in credits like that

Sekhmetouserapis: is the name known?

Sekhmetouserapis: or anything?

or if the name is known, just add a new artist with no data other than the name, yeah