Jaikoz- Discussion Forum

I'm using BETA 2
And I am getting some odd problems with matching files against MusicBrainz.
Here is an example:

I am matching the Insane Clown Posse album Hallowicked. All files matched properly except track 13.
Track 13 has the correct Artist, Album, Track Number, and Track length. The only problem is one character in the title. The file has "Wicked Hellaween" where MusicBrainz has "Wicked Helloween".

When I do a manual correct I get every track in the album EXCEPT track 13 (no MusicIP ID match).
If I fix the title (change one character) it returns with a score of 86 (all other tracks in album score a 47).

oillio wrote:

I am getting some odd problems with matching files against The file has "Wicked Hellaween" where MusicBrainz has "Wicked Helloween".

Is this odd, the title doesn't match and by default the title is worth 40 when it does match. When querying Musicbrainz complete words have to match to get a match so every track with the word Wicked in the title matches as accurately as Wicked Helloween so we end up with alot of potential matches based on matching the word wicked, matching the release or artist or track number.

When selecting which one to choose with jaikoz matches dont have to be exact to get a match but we only check the first ten matches based on Musicbrainz Server scoring. And any tracks with the word Wicked in them and a match on one other field such as trackno may score higher than the real track , if there are ten or more such tracks the real track will not be in the list to check further.

So its not that odd, but Ill consider this problem when refining the jaikoz matching algorithm.

That would make sense, except all of the fields that come up do not have wicked in the title. The one track in the album that has wicked in the track name and the correct track number and the correct track length is not presented. 10 other songs in the album (without a matching track number or track name) are displayed. All with the same match score. As you said, the one track that matches album name, track number, and a partial track name should get a higher score than all of these.

It happened to me again on a John Lee Hooker album. The track number was prepended to the track name, so the name looks like "04 Hobo Blues." So again the partial track name and the correct track number should give the correct track a higher score. And it did for tracks 1 - 10 (scored 81 for the correct track 47 for the others). But tracks 11 - 24 did the same thing, displayed 10 tracks from the album with a score of 47, none of them the correct track.

There seems to be an inconsistency in the musicbrainz search index, I should have a workaround for this in the next release.

Excellent man. Thanks.
This bug is frustrating. Seeing the entry I need, one track down, for 10 tracks at a time can get annoying.

Thanks again.

I downloaded the new version and I am still having problems. Another example:
I manually copied the MB Unique ID field and updated the tags from that, so all the tags should match the MBDB exactly and the song length matches. But when I run manual correct I don't get the song. The match scores that are returned are 55, 47, and 11. No MusicIP matches. The correct entry should be at least in the 90's and an 11 is beating it out?
The song is:
Artist - The Supremes
Album - The Supremes (disc 2)
Title - Falling in Love With Love
Track - 16
MB ID - 612a24b1-1575-4f72-8aab-a3b47b8ff3b5

I have edited the Match Score values, making Title, Artist, and Track No the highest importance.

BTW- I like the darker colors in the new Mac version (though I would still suggest highlighting the entire row is some way). And the fixes to selecting and editing fields in the table really help. Thanks.

Sorry I didnt get to fix this issue in this release.

The problem is to with case in prepositions on the Music search Engine
http://bugs.musicbrainz.org/ticket/3741

I thought prepositions need to always be lowercase so when I query Musicbrainz for tracks with a title of 'Falling in Love With Love' I send it
'falling in love with love' , but it turns out most prepositions/conjunctives must always match the case they are on the server which is usually but not always lowercase.

So on the server this track is held as 'Falling in Love With Love'

Sending

'Falling in Love With Love'
'falling in love With love'
'falling in love With Love'

would all match

but

'Falling in Love with Love'
'falling In love With love'
'Falling In love with Love'

would not match (only the case of in and With is important)

They are looking at replacing the search engine used, but the timescale has not been defined. So I'll put in a workaround in the next release that will try different combinations of prepositions to get a match. because I always make the value lowercase in the current version of Jaikoz there is no workaround at the moment.

Cool. Thanks for for figuring out what the problem was.
I know how much it sucks to have to hack around problems with someone else's systems.

Have you considered adding support for their test search server mentioned on their blog.
I have no idea how much work that would be for you, but it would be cool to be able to try out the new system on the tracks I get bad results on.

-oillio

Musicbrainz provides a web interface and an xml interface for searching for tracks. Jaikoz uses the xml interface but only the Web Interface is available on the test server so this canot be used with Jaikoz, anyway this is intended for testing not general purpose use. But I am doing some tests with the new Musicbrainz/Xapian search so that when it is released it will work properly with Jaikoz.

Jaikoz 2.5 beta contains a workaround for the current Musicbrainz server that will handle most cases - and the MB server should be updated next week.

It's back, but different.

I have an album Janet Jackson - All for You (Don't ask WHY I have it), only two tracks match automatically.
I open MusicBrainz for the matched release, pull the MB UID for the track "Intro" and add it to the appropriate track and fix tag data from that UID, so all track data should match the MB DB exactly.
I have unchecked "Possible matches must be within track duration" but the track is only 2 sec off anyway.
Manual Correct tags from MB returns no results.

I get similar results for most on the tracks in the album.

hmm, unfortunately the planned update of the Musicbrainz Server for improved search hasnt happened yet, so Im stuck with still working round the issues in the current search, I'll have to take another look.

Just FYI - I tried it on the Development server and it returned nothing as well.

Thanks for the info