Reduce delay in MusicBrainz querys

[paultaylor]

1. It would be great in any case if Jaikoz would iteratively “match to single release” per sub folder - I think this was a topic somewhere else.

You can already do this you just need to change the options, enable
Preferences:Remote Correct:Only Match Complete Releases and
Preferences:Remote Correct:Group Songs by Folder Only

[quote=Grafter]
2. Where my logic was heading and to fix my incomplete release issues:

• add all files from (say) a single artist.
• ignore existing meta data and ignore underlying folder structure
• so just assuming a big pool of files and only starting with puid:
  – get a universe of all possible releases derived from the puids
  – do some sort of magic “best fit” analysis to determine the most complete set of releases with all tracks matched that can be built from the pool of input tracks.[/quote]
  You could simulate this in MusicBrainz by removing all metadata then Jaikoz would be forced to just use Puids, but there are a number of drawbacks to this.

1. Slow. Puids take a while to retrieve/generate and a Musicbrainz lookups is need for ever file
2. Incomplete. Not all Puids link to songs in Musicbrainz
3. Inaccurate. Its easier to get a good match if there if existing metadata can be used to direct to the best match. Linking to the least number of releases doesnt neccessarily reflect the best match.

[paultaylor]

Is there a manual override for MusicBrainz lookups, for those of us who run a mirror/local musicbrainz server?

Yes , there is now in the Jaikoz 4.3.0 Beta, but to remove the 1 second delay you do need a Pro license.

[scribebox]

If additionally you setup your own search server using Preferences:MusicBrainz:Submissions to MusicBrainz:MusicBrainz Search Server the limit is removed for searches as well.

I upgraded to PRO last night, because these were THE features i needed, i then installed and updated the mirror of the MusicBrainz NGS server, only realizing that i needed to install the Search Server portion, but im running into all kinds of issues setting up the Search Server over SSH / PuTTY / CLI…

im also not sure what HTTP server the current NGS VM image uses (downloaded from here: ftp://ftp.musicbrainz.org/pub/musicbrainz/vm/ ), can we install the search server along side the VM, and why doesnt the VM come with the search server enabled by default? maybe some ninja out there would like to download the current MB NGS VM file, ADD the search server, and then upload a torrent somewhere, i think that would be invaluable for all the pro users!

or atleast someone post a current step by step using the latest VM build…

i mean, im just happy its querying my local database, but the search server functionality would cut down drastically on time… (not to mention MB server resources)

also, the vm image im running only has 1gb of free space, i say we also increase the disk size to about 45gb…

im currently trying to hack a search server into the vm image and do all of the above, but im afraid i might be half assing it…

here is my current PuTTY logs… for the search server… maybe someone can point out what im doing wrong:…

http://pastebin.com/JvyKRqek

i think putty might have cut off the first half after the maven install…

ill make sure and get more thorough logging as i progress.

-ScribeBox

[paultaylor]

HI, I think you might have forgot to build the mmd-schema first

From the README file:

Check out and build server code
-------------------------------

If you haven't already done so, check out the mmd-schema repository using Subversion as follows:

    svn co http://svn.musicbrainz.org/mmd-schema/trunk mmd-schema

Then build and install the model:

    cd mmd-schema/brainz-mmd2-jaxb
    mvn install

If you haven't already done so, check out the server source code using Subversion via:

    svn co http://svn.musicbrainz.org/search_server/trunk search_server

Then build the indexer and the search application as follows:

    cd search_server
    ./makeinstall.sh
    mvn package

This step will download any required java components and then compile and test
the whole server.

The search server needs about 10GB free to build the search indexes and is Operating System independent (Works fine on OSX, LInux,WIndows) so I would suggest you install the search server directly on your machine.

I think there are some reasons why the Search Server isn’t installed as part of the VM Image but I cant remember why.