They've got queues to match their data with external sources.
MB is just one of those sources of course
nikki blinks at all the info
nikki
I clicked on one of the lines with mb and got a HUGE orange menu bar from us
navap
Yeah..
I took a look and couldn't figure that out
But besides that css glitch I think it works really well
nikki
it would work better if it actually fit on the screen for me
instead it's all scrolly and resizey and things move around when I move my mouse :(
navap
Okay besides the css and resizing issues then :)
hawke
Works for me in Chrome
I don't know what it does, but it works
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.
nikki
that would get rid of a lot of my submissions then :P
(well, my potential ones in the future)
hawke
Why's that?
nikki
because I'm not going to go through setting recording times manually
hawke
hmm
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
hawke: why not?
hawke
kepstin: because there's no duration information with that recording.
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
oh, hi kepstin
hawke
I dunno, maybe there's a better way to handle it.
Like setting durations from acoustIDs somehow
Or...I dunno
kepstin
setting recording times from track times automatically would help a lot...
hawke
can that be done in a reasonable way?
given that it often varies
nikki
how do you actually decide anyway?
hawke
I don't.
I don't know that I've ever set a recording duration intentionally
nikki
I've only done it to fix times which were completely off
hawke
I might have done that, not sure
Usually I'm entering new recordings, and those get set automatically from the tracklist. Otherwise I mostly use existing recordings if possible
There's no way to merge an entire disc of recordings, is there?
nikki
nope
hawke
:-(
I suppose I could edit one of the releases, delete one disc, and add the other disc from the existing one.
igndenok joined the channel
Except that the release editor won't find it.
...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.
navap
That sounds like it could get messy
hawke
or maybe just display the RG annotation above the release annotation, as a separate paragraph
but that would imply giving more than one line to annotations.
jacobbrett
I was thinking more like: Release Name (release comment grey) (release group comment grey & italic) or something.
navap
Messy, and backwards.
You'd want the RG comment first
jacobbrett
Yeah, I just thought that.
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
I was imagining duplicated comments
The release would inherit the RG comment and could optionally have something release-specific set.
hawke
yep
Would also show the RG information everywhere it was relevant
navap
What kind of capitalization should we have in comments?
ETI case?
kepstin
I don't remember what ETI case is exactly. I normally prefer sentence caps in comments.
(ETI is normally sentence caps with first word lowercased, iirc?)
navap
ETI words/phrases is stuff like 'bonus disc', 'remix', 'instrumental' and it's all in lower case unless there's a proper noun