#musicbrainz

scrub that.

If the track artist == the album artist

Then it considers that you're doing a first-time VA-conversion, and auto-splits the track name.

it did this exact thing when I first converted the album and answered yes to converint the tracks.

on a different album?

this album. I originally pulled it out of one of the suggestions.

Ah. so this is a side-effect of the modbot not running perhaps? In a way

modbot should be running.

every 10 I think.

Oh yes, your server. I forgot :-)

So maybe a workaround would be as follows:

if the album artist == the track artist /or/ all the track artists are the same,

then auto-split. Otherwise not.

what if a moderation gets applied before the user is done with the album.

that would change the behaviour of the process part of the way through...

Mmmm. Not sure, I'm having trouble understanding this this morning.

I know that I was specifically trying to address a particular bug in SF

ok.

#689150

I see.

we could add a flag to the changetrack that tells it to split or not to split.

we could add another javascript button that also does a split.

OK, that's good.

We can just make the "use guessed" button do the split in both cases.

sure...

A couple of extra vars in the page... a pair for "default", a pair for "guessed", a pair for "current".

BTW is the staging server codebase just the latest HEAD?

Not sure when I did the last update.

should I update just in case?

I'll tag my codebase. Please update to my tag, to be sure there are no changes.

Wait a mo...

the track name problem page is really killer!

btw I'm out tomorrow evening, so releasing is probably no-go then, unless you want to do it.

sat perhaps?

good for me

suggest a time.

err, let's say 8pm BST, that's 7pm UTC, 11am PST. I think.

is that ok?

11am is perfect.

got tag?

OK, try updating to RELEASE_20030404-RC1

yes, he knows :-)

:-)

RCS file: /var/cvs/mb_server/admin/handler-dist.pl,v

Merging differences between 1.26 and 1.27 into handler-dist.pl

Merging differences between 1.9 and 1.10 into CreateTables.sql

Merging differences between 1.2 and 1.3 into WordTables20030321.sql

Merging differences between 1.32 and 1.34 into SearchEngine.pm

does that mean you're patching forwards, or backwards?

I just updated to the tag.

should I just nuke those files and re up?

If you like. It's safer, for sure.

Right, I must leave you to it.

Night!

ok

have a good day

thanks. Catch you later

for your backlog reading pleasure:

the RELEASE_20030404-RC1 is now active

grishnav (~grishnav@12-224-166-69.client.attbi.com) has joined #musicbrainz

spaetz (~chatzilla@hsg00327.unisg.ch) has joined #musicbrainz

alus (alus@cs242710-9.austin.rr.com) has joined #musicbrainz

icepick is now known as icepick-away

jsimmons (~jsimmons@gryphon.punk.net) has joined #musicbrainz

MacDome^zzz is now known as MacDome

icepick-away is now known as icepick

icepick is now known as icepick-away

icepick-away is now known as icepick

icepick is now known as icepick-away

djce (~davide@195.60.9.122) has joined #musicbrainz

ruaok (~robert@adsl-63-194-101-14.dsl.snlo01.pacbell.net) has joined #musicbrainz

Morning!

evening!

I've /just/ mailed mb-users with a plea for testing volunteers.

good.

personally, I think things look quite good.

Yes. The only bit which concerns me is all the moderation web forms.

That's just because, although conceptually the changes were simple, the diffs were complex.

So it's hard to prove to oneself that the changes are correct.

I walked through quite a few of them yesterday...

understood.

That's good. I haven't really, not since originally coding them.

"server version: 2003-04-05-RC1" - I hope :-)

So is there a preview binary of the tagger to test?

yes. I posted about it yesterday.

0.9.0-test1

ok

so far I've not had any comments on it.

Time to fire up my wife's Windows box so I can play

I suppose no news is good news.

/I'll/ comment ;-)

damn.

when I've tried it

(damn, forgot to ask about the icons.)

About the tagger...

In the installation process, it asks about making the tagger the default CD player app.

I've never said "yes" yet, but I've noticed it's the default.

Has anybody requested the default be "no" ?

i'm formally requesting that the default be no

;)

I'm assuming that having the tagger set to your CD-app-thing makes it pretty hard to actually /play/ the cd, does it?

yeah, but who uses CDs?

:-)

hmmm. some answer!

ouch. an error. let me transcribe it...

Access violation at address 66806730 in SHELL32.DLL, Read of address FFFFFFFF

That was after going into the options screen, changing a couple of things, then it did it when I clicked OK

ugh.

can you try and reproduce it?

No, I lie, not OK. sorry.

When I clicked "Browse" next to "move tagged files to..."

I'll try.

Yup, same again.

G'day, gang. Any objections to me hacking on logwatch so that we get a summary of ANON proftpd logins instead of a complete list in the email we get every day?

This is on Win98 with IE 5.5

Crack on. I've never understood logwatch anyway!

ruaok: to reproduce (for me): start tagger, dismiss nag, open options dialog, go to "Directories" tag, check "move tagged files to this directory", click "Browse".

jsimmons: sure.

djce: ok, I think I know what the problem us.

After the crash dialog message is dismissed, the app is unresponsive, as if it's waiting for you to complete the "browse" dialog which /should/ have appeared. But it never did appear, so the tagger has to be killed.

cool

I'll keep playing, pending a workaround or -test-2

workaround:

check the box, type some text into the field and then hit browse.

FYI, exactly the same crash on the other "browse" button just below.

ok

workaround successful :-)

rudolf (davide@195.60.9.121) has joined #musicbrainz

Look ma, I'm on Windows!

another crash :-(

module ID3LIB.DLL at 017f:006b4ca4.

Looks like it's a specific input file. I'll try to confirm...

if so, mail me the file or stick it onto zim

No wait, that's not quite it.

The problem is the file /before/, which fails to decode.

After failing to decode that file, trying to process any other file causes the crash.

I'll provide you the "file before".