Automatic matching is difficult but I've made a number of changes to improve the matching in Jaikoz in the latest release.
Jaikoz searches for possible matches in Musicbrainz then rescores them taking additional information into account to find the best match, it does this because an original Musicbrainz score only takes into account the search terms when scoring but we need to consider more values. For example we do not specify a duration in a search because some songs do not even have a duration within Musicbrainz so would never be returned by a search, but having got some potential results we want to give a higher score to those with a duration that matches the original song. Musicbrainz uses Lucene for searching with its own custom analyzer for deciding which songs are returned by a search and this latest release of Jaikoz uses the exact same analyzer to ensure scoring is compatible. This is one advantage of working on both Musicbrainz and Jaikoz !
When searching for a track we now consider more variations of the name because songs entered into Musicbrainz are normalized , for example We Have Explosive (Pt. 5) should be entered into Musicbrainz as We Have Explosive, Part 5 but they might not have been. This normalization is detailed in the Style Guidelines and In Jaikoz we now check for the title as it appears in your metadata and also as a normalized version as far as possible.
We also make workarounds for common errors in entering data. For example Musicbrainz Issue #5538 shows that users usually enter song titles as 'No. 1' , but in a large minority of cases enter 'No.1' , Jaikoz workrounds this issue.
Cluster Albums finds albums by artists with the same name but a different Release Id and tries to move the songs so that they are all on the same Release Id, note this is different to what 'Cluster' means in Musicbrainz Picard and perhaps I should have called it something different. Previously it did this by matching title against title for each Release Id being used, and picked the Release Id which had the most matches but now this has been improved. Firstly we use fuzzy matching on the title allowing for normalization as explained earlier. Secondly if all but a couple of tracks are successfully matched to one Release Id we allow matches on Acoustic Id and song length to shoehorn the remaining tracks into a potential release. This is really useful when the same song exists on two albums but is radically renamed between the two.
|
9 comments:
I am waiting for my Google order number: 812434605894710
Print
Shipping Status Qty Item Price
Not yet shipped 1 Jaikoz Audio Tagger - Lifetime license for jaikoz
Would you please be so kind as to send it to me?
Yours,
Hal N.
Hi it was sent by email, and has just been resent do you have it now.
i have payd for Jaikoz and i think ist the most powerful and perfekt taggingsoftware i´ve ever seen.... but:
i cannot use all functions because its not very userftriendly i think. i have to search for every function and it takes much time to find these things. is it not possible to switch to an other GUI or skin without all the symbols? i just want to have a GUI like MagicMP3Tagger... just load my folders and klick... KISS :)
Anonymous, I'm suprised you mention the MagicTagger Gui it looks real ugly to me. I'm always working on improving Jaikoz but its an ongoing process, however by customizing the tasks configured in the Autocorrecter you can do most things with one click
Tried it out a couple of weeks ago and purchased a license. Nice program. Looking to replace the Perl script/MediaMonkey system I currently use to get my files in line. One thing I see missing (unless *I'm* the one missing how to do this in the current version) is the capability to move articles ("A", "An", "The") to the end of a tag (e.g. correct "The Beatles" to "Beatles, The"). Otherwise filenames and tags don't sort correctly, the way they would be filed in a library or music store which knows to ignore the article. Any plans to implement this functionality?
Hi, you might be approaching this the wrong way. There are associated sort fields for the most popular fields, so whereas the ARTIST field might contain 'The Beatles', the SORTARTIST field should contains 'Beatles, The', and this field is filled in by Musicbrainz. Players such as iTunes and Winamop use this sort field if it exists to sort the songs.
The sort fields are not shown in the table view by default, but they can easily be added using the dropdrown at the top righthandside of the table.
Still not sure how to get this to do what I want. Because the "Sort " tags aren't always populated (I'm assuming because the regular tag is already properly sortable according to MusicBrainz?) I am not able to generate a file rename mask, unless I'm not properly understanding the $if(,) directive (i.e. it's NOT capable of expressing an IF/THEN/ELSE condition). Thanks for your quick reply and for writing an awesome program! If you can explain how to write a proper file rename mask and/or implement an $ifelse(,,) directive, it would be the awesomEST! :)
I think Musicbrainz does always populate the Sort Artist field, it might be that you didn't actually get a match from Musicbrainz at all.
But you are right about the if directive, its not very flexible and the aim is to improve this.
I am looking to rename based on sort artist, sort album and sort title. I guess you could argue that sort title is not needed, but sort album matters for compilations where the filename would start with the album name.
Please put my name on the list of those who will be eagerly awaiting some if/then/else functionality.
Post a Comment