Jaikoz- Discussion Forum

Right.

Well, I got to line 153 out of ~1300 in half an hour, and did a little sanity-check.

Do I really see the need for a Norwegian translation, which could potentially benefit maybe two out of perhaps ten Norwegian customers, and in reality will benefit nobody because they will just use the English version anyway?

Nah. Case closed.

I do not enjoy doing this.

What's with the empty fields, do you plan to either:
1. Leave fields having identical text-strings between the two languages, empty
2. Forget to auto-translate new strings

Ok, got it. I confused it with settings in the "my documents"-folder.

Anyway, this is way more than two hours' work.

I'll have a crack at it, but no promises.

Also the automatic translation funnily enough translates to Swedish in some places.

Cool, where's the jaikoz.properties file?

How many lines of text is it and what format?

If it takes me less than two hours I could do it.

Hi, just installed 3.9.

Chose "Eng"(lish) as language, got Norwegian anyway (on first run, at least).

The automatic translation is atrocious. I don't know why one would bother, really.

In the meantime, MP3Tag has support for regex'es.

Sure.

We can start with how metadata isn't fetched from musicbrainz even though it is in the manipulators and how directories and filenames aren't changed even though they are in the manipulators so that I have to auto-correct twice and then a file is perceived as not belonging to the correct album and I have to restart Jaikoz and then load the files for that album from two different folders and try and make Jaikoz understand that I want to match to a single musicbrainz release and then that doesn't work but eventually I can coax it but then it can't save the corrections for that file and I have to manually move the file into the directory for the correct album and then I have to do it all over again and eventually something works somehow.

I'm going to go get drunk now.

Here's the screenshots: http://www.mediafire.com/?r32rwm2ejlae6om

Also it doesn't match to a specified musicbrainz id, and it doesn't save changes, and it doesn't create accustic ids so it's kind of difficult to use.

Maybe testing the application would be an idea?

Just a thought.

A few different things.

1. Hotkeys (various) don't work
2. Have to save artwork (folder.jpg) as separate step now
3. No gracefull handling of timeout ("took longer than 5 minutes so I give up")
4. No statefull handling of choices for available manipulators, i.e. you can't chose to correct filename if metadata hasn't been saved
5. Seem to be race-conditions for the manipulators

5) is the most important one, and means that you can run autocorrect but the file and folder isn't corrected, and then you have to run it again for the tracks that hasn't been corrected.

Given that I am running it on 8 cores, I suppose I could test this by running it under a vmware-image with 2 cores available.

Hi Paul and happy newyears!

Also, Jaikoz doesn't work, will that be fixed in 3.8.4?

If not, I could go into the details.

Cheers!

I don't think I have understood this completely, but.

Only Match Full Release
If one is being anal about accuracy, then perhaps it would be a good thing to get involved with tagging properly.

And showing that the information in musicbrainz / whatever does not match 100% could help getting people involved.

My two cents, and perhaps also you would get some better feedback on this over at hydrogenaudio.org?

Two different parts, here.

1. Autocorrecter
Save each file once, upon completion of all tasks for that file

2. Manual correct
Save each file once, upon exit (with notification) / user request 'save changes'.

Collisions: When a user has made manual corrections, then runs autocorrect.
Ask if autocorrecter should overwrite the manual correction for this tag:
a) this tag for this file (show autocorrector-value and manual correction-value, ask for each file)
b) this tag for all files
c) overwrite all manual tag

To explain, a user may have chosen to correct all the "Year"-tags for some files, and want to keep them that way, but may not want to keep manual corrections for other tags.

True, but we don't live in a perfect world.

My perspective is that of a user, where if the application tells me that files have been changed, and I haven't done anything, I get worried.

Couple that with previously discussed issues regarding subfolders not being corrected, and filenames not being corrected, and my opinion is that a user could get a bit sceptical.

Translation: No, remove duplicates do not work for 100% of users of this program due to the way it has been written.