They've got queues to match their data with external sources.
2011-11-01 30547, 2011
navap
MB is just one of those sources of course
2011-11-01 30537, 2011
nikki blinks at all the info
2011-11-01 30559, 2011
nikki
I clicked on one of the lines with mb and got a HUGE orange menu bar from us
2011-11-01 30530, 2011
navap
Yeah..
2011-11-01 30546, 2011
navap
I took a look and couldn't figure that out
2011-11-01 30519, 2011
navap
But besides that css glitch I think it works really well
2011-11-01 30534, 2011
nikki
it would work better if it actually fit on the screen for me
2011-11-01 30548, 2011
nikki
instead it's all scrolly and resizey and things move around when I move my mouse :(
2011-11-01 30545, 2011
navap
Okay besides the css and resizing issues then :)
2011-11-01 30559, 2011
hawke
Works for me in Chrome
2011-11-01 30515, 2011
hawke
I don't know what it does, but it works
2011-11-01 30550, 2011
hawke
luks: Don't know if you're around, or if you read the scrollback, but: acoustID should probably refuse to associate unknown/0:00 recordings with acoustIDs.
2011-11-01 30539, 2011
nikki
that would get rid of a lot of my submissions then :P
2011-11-01 30513, 2011
nikki
(well, my potential ones in the future)
2011-11-01 30513, 2011
hawke
Why's that?
2011-11-01 30534, 2011
nikki
because I'm not going to go through setting recording times manually
2011-11-01 30514, 2011
hawke
hmm
2011-11-01 30535, 2011
nikki
I add releases to the db, then when they finally arrive, I add the disc ids and rip them
it's really annoying that adding a disc id to a release doesn't set the recording times, yeah
2011-11-01 30558, 2011
kepstin
hawke: why not?
2011-11-01 30519, 2011
hawke
kepstin: because there's no duration information with that recording.
2011-11-01 30520, 2011
nikki
but adding track times from a disc id doesn't set recording times, and assuming luks is using the replication thing, it would mean having to wait an hour from adding times on the site to being able to submit stuff
2011-11-01 30544, 2011
nikki
oh, hi kepstin
2011-11-01 30507, 2011
hawke
I dunno, maybe there's a better way to handle it.
2011-11-01 30522, 2011
hawke
Like setting durations from acoustIDs somehow
2011-11-01 30528, 2011
hawke
Or...I dunno
2011-11-01 30540, 2011
kepstin
setting recording times from track times automatically would help a lot...
2011-11-01 30507, 2011
hawke
can that be done in a reasonable way?
2011-11-01 30517, 2011
hawke
given that it often varies
2011-11-01 30526, 2011
nikki
how do you actually decide anyway?
2011-11-01 30535, 2011
hawke
I don't.
2011-11-01 30512, 2011
hawke
I don't know that I've ever set a recording duration intentionally
2011-11-01 30551, 2011
nikki
I've only done it to fix times which were completely off
2011-11-01 30559, 2011
hawke
I might have done that, not sure
2011-11-01 30548, 2011
hawke
Usually I'm entering new recordings, and those get set automatically from the tracklist. Otherwise I mostly use existing recordings if possible
2011-11-01 30500, 2011
hawke
There's no way to merge an entire disc of recordings, is there?
2011-11-01 30506, 2011
nikki
nope
2011-11-01 30526, 2011
hawke
:-(
2011-11-01 30511, 2011
hawke
I suppose I could edit one of the releases, delete one disc, and add the other disc from the existing one.
2011-11-01 30538, 2011
igndenok joined the channel
2011-11-01 30531, 2011
hawke
Except that the release editor won't find it.
2011-11-01 30505, 2011
hawke
...as long as I give it a number of tracks, it won't. :-(
Alternatively, it could be a good idea for releases to inherit the release group's comment in search results, etc.
2011-11-01 30511, 2011
navap
That sounds like it could get messy
2011-11-01 30539, 2011
hawke
or maybe just display the RG annotation above the release annotation, as a separate paragraph
2011-11-01 30549, 2011
hawke
but that would imply giving more than one line to annotations.
2011-11-01 30535, 2011
jacobbrett
I was thinking more like: Release Name (release comment grey) (release group comment grey & italic) or something.
2011-11-01 30505, 2011
navap
Messy, and backwards.
2011-11-01 30518, 2011
navap
You'd want the RG comment first
2011-11-01 30524, 2011
jacobbrett
Yeah, I just thought that.
2011-11-01 30554, 2011
navap
Actually, if we showed both comments then in the above cases the comment would only be needed at the RG level and so it wouln't be duplicated and wouldn't be as messy
2011-11-01 30516, 2011
navap
I was imagining duplicated comments
2011-11-01 30554, 2011
navap
The release would inherit the RG comment and could optionally have something release-specific set.
2011-11-01 30526, 2011
hawke
yep
2011-11-01 30539, 2011
hawke
Would also show the RG information everywhere it was relevant
2011-11-01 30558, 2011
navap
What kind of capitalization should we have in comments?
2011-11-01 30520, 2011
navap
ETI case?
2011-11-01 30549, 2011
kepstin
I don't remember what ETI case is exactly. I normally prefer sentence caps in comments.
2011-11-01 30510, 2011
kepstin
(ETI is normally sentence caps with first word lowercased, iirc?)
2011-11-01 30520, 2011
navap
ETI words/phrases is stuff like 'bonus disc', 'remix', 'instrumental' and it's all in lower case unless there's a proper noun
