Jaikoz- Discussion Forum

1. If you select that you prefer Jaikoz to use albums that have been matched before, does it match based on the tilte of the album or the Album MusicBrainz ID?

2. When you perform the cluster alums function, does it choose an album ID that goes by your settings? Like, so, if I select to prefer official releases and from a certain country, will it take that into consideration and choose the album based off of that?

1. You said you take that into account. But my REAL focus was just how fast it opens, which is much slower for me consistently than all other programs.

2. I guess so. Whenever I have downloaded any other computer program, generally, I have just clicked on the thing that downloads it, clicked "download" or whatever, and just basically clicked "Next" over and over, sometimes clicking options, without having to follow any real instructions except for clicking "Next". I know that's kinda vague, but that's the gist it. I think it would be easier if Jaikoz were like that.

3. You said: "If you are saying you want metamatch to take precdedence over acoustic ids, the easiest way to do this would be to run Autoccorect From MusicBrainz without doing Retrieve Acoustic Ids first." What if acoustic Id's are already on the audio files? If they are, there should be an option to ignore the acoustic Id and just do a metadata match.

4. Okay.

5. Okay. But, for my knowledge, what do you mean by "you should really only ever encode from a lossless format."?

6. Nevermind.

7. That's even better.

8. I'll send my files which Jaikoz can't save.

9. I was hoping for automatic save changes to any changes, whether it be acoustic Id (which I know is already in place), Correct from MuiscBrainz, autocorrect, update tags from existing musicbrainz id, etc.

1. Jaikoz should open faster.

2. To download/update Jaikoz, it would be easier to just click on through everything, as opposed to extracting the file.

3. When there is an acoustic match, it should look for all releases that are the same as the ones just associated with the acoustic fingerprint, and then find the correct release based on a metadata match, if there is already metadata.

4. Jaikoz should have an option to translate foreign artist names, if possible --- like MusicBrainz Picard. But this would be disabled by default.

5. I know that, at least on iTunes, you can convert songs between AAC and MP3 formats. Jaikoz should be able to convert between any formats that are possible to convert (not ID3 on MP3's, but the MAJOR formats: MP3, Flaac, Vorbis, etc.).

6. I think, by default, the following options should be set ONLY if there is no metadata match : prefer official albums, prefer JUST studio albums. If there is metadata, it should just find the match closest to the metadata, despite those options. But there should still be an option to ALWAYS set those options. So, in this scenario, it would have under prefer official albums "only if there is no metadata match" and "always" and you would choose one, but it would, by default, it would have chosen "only if there is no metadata match".

7. I think the prefer country should not be set by default, not only because it should just find the best metadata match despite country, but because Jaikoz supports different languages, and, therefore, different countries.

8. I might be incorrect on this, but, from my understanding, when saving track changes, it can either save ALL the changes made to it or NONE, if just ONE change cannot be saved. So, if you choose to do multiple things in the autocorrector, it should look at the individual changes and save all it can, but not necessarily ALL the changes. But this would be disabled by default.

9. Jaikoz should have an option to save changes to EACH track as it goes. So, if it makes a change to a track, it should save it, move on to the next track, save the changes, etc. But this would be disabled by default.

---Thanks

But if there is an acoustic ID match, will it utilize the new options (try to find official release, try to find certain types of releases, try to find releases used before, etc.)? If 'Acoustic Id Match must also have minimum meta rating' is selected? If not?

Pretty much what I was looking for on the 30th of January release, except see my last new threads I created.

I think when it does this, it should ignore the album title, find different releases with the same critera that already exists (except album title), going by your options of metadata match (e.g., "find songs on albums that were previously used", "country," etc.).

THEN, it would look at the album title and album ID and make sure albums of the same name have the same album ID.

Also, a question. The way it is now, does it try to find album ID's of albums that match your options criteria (I'm referring to the same options as before)? If not, it should.

Okay, so if you don't select "force metadata matches made through acoustic fingerprinting," it doesn't use the current metada when doing a match, right? It just finds a version of metada for the matching acoustic ID, right, because, as far as I know, an acoustic ID just correlates to ONE of the releases of it and not all of them. Is that correct?

So, the new matching system options from the 30th of 2008 version won't even use those options to match if an acoustic ID is found, right?

So, am I correct in thinking if I select "force metadata matches when there is an acoustic fingerprint", then it WILL utilize the new options?

If not, I think there should be an option to just do metada match (automatically; I know there is the manual metada match), even if the song has an acoustic ID with it.

Or, if my assumptions are not correct, you could utilize the new options by Jaikoz automatically (when you press do MusicBrainze matches) finding the metada with an acoustic ID of the song and finding releases that match the metadata of the one with the acoustic ID, going by the new options.

-Thanks

I am still having the first problem tumsuden had. I have the latest version of Java, and I have iTunes installed. (By the way, I use Windows.) I have also uninstalled and reinstalled Jaikoz many times.

Jaikoz should have a "Remove" button (or something along those lines), which would remove (but not delete) songs that the user doesn't want to work with anymore.

[This is on the basis that the album name and/or the MusicBrainz Id [under a different album] change).

If you choose to have one artwork image to be added to each file in the settings, and you go to "Get Artwork" or whatever OR you go to "AutoCorrect Based on MusicBrainz Database" or whatever, will a new, single (based on the settings selected) image override the old one given by Jaikoz and/or iTunes?

I think that there should be an option on manual tag for the user to select which criteria of the tag information (recording length, artist name, song name, album name, etc.) to look up when doing matches.

With the defualt, or all of the criteria, with the manual tag, I have done searches and found literally no matches on some songs, but then, when I manually, MANUALLY looked the song data up, by going to the MusicBrainz website, and typing in less of the tag information (or typing into fewer of the search criteria boxes), I found matches. (But, still, I had to manually type out the MusicBrainz Unique File ID myselft by minimizing and maximinizing the MusicBrainz website page with it on it).

Okay, well, I guess it was an good idea in theory, but if you don't think it would work in practical terms, then forget it.

Okay. Let me try to explain again.

If you have a song collection with some artists known as "The Beetles" but mostly as "The Beatles", the AutoCorrector should change them all to the correct "The Beatles".

But that's only because the AutoCorrector ONlY compares data WITHIN THE SAME RESPECTIVE FIELDS (album name, artist name, etc.) to each other.

But I think that the album name data, artist name data, and song name data should be compared to each other.

Because a band might have a self-titled album and/or song or a band might have a song and album name that this the same (but is NOT the same name of the band). Like the band Black Sabbath has an album entitled Black Sabbath, on which there is a song entitled Black Sabbath.

Let's say you have some Black Sabbath in your music collection. You have all of the band name data spelled correctly, but some of the album name data and/or the song name itself is misspelled "Black Sabath".

If the album name data, song name data, and artist name data were compared to each other during AutoCorrector, it would catch it, and change all of them back to "Black Sabbath".

So, I think that, during the AutoCorrector's run, the artist name data, song name data, and album name data should be compared.

To improve on the "... etc, etc." of the first post, I think this list includes all of the things that are not capitalized in titles in the English Language:

all prepositions
conjugated forms of the verb "to be"
the word "be" itself
the
a
an
and
if a word is hyphenated, the word(s) following the hyphen(s), like Vice-president

(Except, the first letter of the first word is always capitalized, like Of Mice and Men, and the first letters of the first words following spaced hyphens and colons are always capitalized, like Boston: And Their Greatest Hits [made up])

I think that the AutoCorrector should compare album names to song names and vice-versa, song names to artist names and vice-versa, and album names to artists names and vice-versa.

This would help in situations in which artists have self-titled album names or self-titled songs. For example, the band Black Sabbath has an album called "Black Sabbath" and a song called "Black Sabbath".