batch-handling, write changes as they occur not after 1.000.000.000.000 songs have been processed

[MAzE5h1p69wB]

That would make it so easier to get things done.

I can process about 5.000 files in 12 hours.

But I have 50.000 files.

So I have to fiddle around with choosing only so-and-so many files each day, in order to be able to get done with the processing.

And Jaikuz is so resource-hogging (and slow), that I have to kill it if I want to do anything else at the same time.

This leads to frustrations, as I start a batch (at home) before I go to work, try to monitor it throughout the day (by vnc), and when I get home it still isn’t done and it takes forever to write changes to disk as it decides to “check” all of the files in the directory and not just the ones I have chosen to process, again.

So then I have to chose only so-and-so many files to process for the next day, put them in a directory all by themselves, check that there aren’t too many, if there are then put some back to where they came from, and, well.

Save on change please (and don’t check files with unique musicbrain ids?).

[paultaylor]

You can save changes as you go, please see http://www.jaikoz.net/jaikozforum/posts/list/0/1345.page#5501

Save is much slower if you are saving your files to a networked drive

[MAzE5h1p69wB]

Thank you for taking the time to advice, that helped a bit.

If I may, I would like to suggest two additional options, “Move recognized files” and “Move unrecognized files”.

The idea being, to have a directory in which you put your music-files, and then putting them into the appropriate directories.

Just a thought, thank you for your feedback.