#musicbrainz

hi

djce rewrote the lucene XML dumper.

oh. what did he do?

My code was taking too long, so he wrote a perl script to parse the pg data dump and kick out the proper XML document.

hm, well. as long as it works :-)

faster than mine. :-)

the database was involved. that's always slow

plus the Pending and PendingData tables have no indexes.

Thus they are painfully slow.

oh, that explains

how big is an XML dump for one hour?

I hope it isn't too slow to apply it

djce forced a data cleanup, which caused a huge update packet.

quick to dump the data, 20 mins to dump the XML.

hm, too bad I can't use the packet for tests

but it's out of context

I'm sure he still has it around.

oh yeah.

at the moment, I'm working on the index updating

I think I solved the problems, the rest is boring implemenation work

I'm adding a plugin system to libtp.

djce: hi!

ruaok: using libtool?

yes.

libtool comes with a minimal dlopen wrapper that works cross-platform

did you have a look at it?

I'm using it. :-)

cool. you did your homework :-)

I originally used it for bitzi's bitcollider two years ago.

And since that code is Public Domain, its now our code. :-)

might be useful for the playlist stuff, too

very much so.

but lucene has my top priority ATM

we just got some mail to helpwanted@ :

that I could help with.

hm

yalaforge, djce: any good ideas to respond with?

yeah, I just read that.

nothing springs to mind straight away

but I'll have a think and see what comes to mind

sorry, nothing here either

it's cool. I always wanted to learn how to do that :-)

and having portable, flexible data is nice :-)

it would also be useful to have an XML data dump to initialize the index

in the same format?

i.e. lots of <insert>s?

hm, I'm not sure about that. it's rather inefficient

joined documents would be best for initializing

the update|insert|delete is the only option we have for updating the index, however

That's probably best done using postgres then -

ok, just tried MusicBrainz again. It actually worked this time (at least, it moved most files to the identified tab). But now, according to the tutorial, there should be a "submit tags" button, but there is none. Also, does MusicBrainz even gather/write genre and year tags?

- i.e. you download a full db export ("core" set only) corresponding to a replication point

then do a join, select, export as xml

then eat replication data thereafter

yup. the problem is that we also need artists that have no albums at the moment

lukeprog: the submit tags button is enabled only if the tagger has gathered information to submit to the server.

and albums that have no tracks yet

lukeprog: short answers first: genre: no

If it is not enabled, don't worry about it.

oh, it looks like "submit info" is greyed out, actually

yalaforge: big left join then?

yup, probably

if you import the four core tables into Postgres, it's entirely up to you.

ah, okay, then - forget it. Thanks anyway.

lukeprog: the year information feature has been in place a few weeks only, thus we have not collected a lot of data.

djce: see you tomorrow :-)

it's 22:44 here

ok

maybe I'll check out MusicBrainz again in six months or so. Feature requests: genre tags, option to automatically choose earliest album for files that come up with multiple matching albums.

lukeprog: make it ten years

ha, ouch

at leaset the audiofingerprint analyzing is quite fast

ok, thanks for all your help, people.

I just found and downloaded MB today. What a great program! I've tagged a few albums and added some unfound discs to the database. I've configured directories for moving and naming. When I click the Save icon to submit my data the files aren't moved to my "move" directory. The FAQ says this is what should be happening. Am I missing a step?

My move folder is on a UNC path if that matters.

I'm high. Forget everything I just asked.

Somebody mentioned a while ago that the year information is in place now. Is there a place in the tagger UI for this?

what kind of 'place in the tagger' feature are you looking for?

The tagger writes year information into the tags if the info is available.

But the tagger is not a tool for submitting this info -- do that via the web pages.

I didn't mean to be able to interact or set the year information. I meant to be able to see it. When I just submitted a couple new discs, for instance, I never saw an indication of the year info.

the only place to see it is in the embedded web pages.

But we should ask for the release year when the CD is entered.

ok, right

I just added a request for enhancement on that.

thanks!

sweet. I got myself a gmail account. :-)

did I mention how cool musicbrainz is

:-)

ruaok: cool! did you have a connection at google or did you fill out the interested form?

I haven't gotten a response to my interest, yet ...

MB has a friend at Google. :-)

nice

I bet you're on that borscht or orkut thing or whatever too!

nope. I refused that.

any particular reason?

I already neglect my friendster account, so why setup another one?

... cause you could neglect your 'cool-people-only' account now too :)

I wish Novell would open myrealbox.com back up for new accounts... webmail gets old after awhile with all the ads and the slow logins

Is there a way to submit an unpublished/hidden track for a released album? When I import the album data from FreeDB it's missing this hidden track. This track is on the ablum, but isn't printed in the liner notes.

ruaok: I just did another sizeable replication packet (this time after running the ModBot to make a bunch of changes)....

k

this time it exported the rows in <2 sec

and did the XML in <5 sec :-)

sweet.

11 sec end-to-end!

I think I'll stick with that. It seems to work.

now just there's just a whole slew of stuff to commit to CVS...

:-)

then I've still got to test the slave auto-loading of rep. data

The stuff which is on the rep. branch - is that ditchable now?

apart from "ProcessReplicationChanges"

?

if you have a slave loading data, then everything on the replication branch can go.

Not yet. but I have some outline code I'm working on.

it will use ProcessRepChanges, from the branch.

ok, then everything else can go.

k

Is there a way to submit an unpublished/hidden track for a released album? When I import the album data from FreeDB it's missing this hidden track. This track is on the ablum, but isn't printed in the liner notes.

can you find the CD with the hidden track in freedb?

that would be best.

Otherwise, enter a new CD that contains the hidden track.

When I query freedb it always lists the 14 tracks printed on the liner only, minus the hidden track

ok enter a whole new CD.

yeah...

thank you

np

Sorry for my lameness. Does that mean I should move the 14 standard tracks from the Identified tab back to the Unidentified tab? Then I can somehow group them as a new CD submission?

if you move them to the unidentified tab and tag all the tracks by clicking on the tag icons for each track, will give you the best results.

I have 15 tracks, 14 of which freedb knows about. I moved all 15 tracks to the Unidentified tab. I clicked through the tag icon and 14 of the tracks are now on the Identified tab. I'm left with track 15, which is a hidden track that freedb doesn't know about. How do I now submit a whole new album, adding this track as "Hidden Track" ?

I can go through the Add Album UI in the lower part of the interface, but do I then have to type in all 15 track titles manually?

unfortunately yes. :-(

this type of stuff MB is still weak on. :-(

Ahhhh, ok. I get it. Gotcha.

a native cddb->mb conversion tool would be handy

wait that's already there..