As CompMusic we proposed turning instruments into first level entities in the MusicBrainz database. This means exposing a unique identifier for each instrument.
uh like we haven't been talkign about that for aaaaages
morning, so I reluctantly tried installing a linux virtual machine from scratch in order to run mbslave (rather than full mbserver)
After a failed attempt to installed ArchLinux I went for Ubunto Desktop which was very easy to install :)
but ran like an absolute dog, even if given 2gb of memory
So I then tried Fedora with LXDE which is so much better, and quite responsive with the default of 768MB of memory
so I was wondering is it just the Desktop part of Ubunto that is slow or is the whole ubunto flavour of linux rather slow ?
luks
I don't find neither version slow, but I've never ran them in a VM
nikki
I use ubuntu in a vm with xfce and don't find it slow
luks
but you shouldn't really need the gui just to run mbslave
ijabz
maybe its just the default desktop it provides then
luks
I'm guessing it needs 3d acceleration
ijabz
its not just to run mbslave, also for other linux testing
aaron_sk
Hi there :) I'm going to attempt to setup a local search server against my MusicBrainz server install (so my API requests aren't throttled by passing through search.musicbrainz.org). The docs here (http://wiki.musicbrainz.org/Development/Search_...) mention that for the search server to work, it requires "a MusicBrainz database with the core data set loaded". Does anyone know what constitutes a core data set?
luks
ijabz: I'd for xubuntu then
xfce has relatively low requirements
aaron_sk
Is it simply mbdump, mbdump-editor and mbdump-derived?
nikki guesses ijabz is the best person to answer that
ijabz
right, is ubunto better for mbslave thane fedora then ?
nikki notes that the last character is a u, not an o
aaron_sk: yes think so in fact I don't think you need mbdump-editor
nikki
ubuntu is probably better for mb stuff since that's what we officially support
but I imagine mbslave works fine with either
aaron_sk
Ok, that's great ijabz. I've got those 3 already, so as long as I've met the requirements, I'm good to continue with the HOWTO
ijabz
this is mbslave, but I suppose if that what lukas uses would make sense to use that
luks
ijabz: I run mbslave on multiple systems
djce joined the channel
so really any unix is fine
ijabz
hmm, annoying I don't seem able to get VirtuslBox Guest Additions to work on Fedora, was fine on Ubunto
warp
murdos: ok, I'll have a look.
goodmorning #musicbrainz-devel!
reosarevok joined the channel
murdos: looks like it crashed or got killed at some point, but didn't continue updating the indexes because the lock file was still there.
murdos
ok. could you send me the log if you have it? and then re-index recordings and reenable the updater
warp
murdos: what happens if I just start the updater? you think a week is too long for it to catch up?
murdos
for recordings? yes, it's way too long
warp
ok, I'll stop the updaters and reindex.
murdos
but just for recordings, right?
warp
I was planning to do it for everything, seems easier.
murdos
I'd rather not
warp
ok
nikki wonders when this ajax uploading thingy will make it to beta
but this fails on line 7 because obviously it does return some JSON :)
aaron_sk
Hi all. Does anyone know of a way to get an exact artist match (by name or alias) from MusicBrainz? Using the search endpoint gives me lots of matches, I'm looking for exact matches only.
ocharles
but the JSON it returns i can't no ahead of time because it has an MBID in
warp
mock MBID generation?
(to be predictable)
ocharles
that's done by musicbrainz-data, so that's not really an option
warp
then you have to write your test to not care about it. possibly check that the mbid is a valid mbid, then remove it from the json (or replace it), and then do further checks.
ocharles
yea, i think that's the only real option
nikki
aaron_sk: using quotes tends to help, but since it's for searching rather than exact matches, it's not very good at only returning things that match exactly
warp
in python I'd probably add some testing features to the library to make the generation predictable for clients of the library.
ocharles: but either solution works, and I can't think of anything else.