New Autocorrecting Save Options

[paultaylor]

In the current Autocorrecter you cannot save changes as you go along with a few exceptions, you can save puids as they are created, and you can use the Save and Move task to save changes at points during the autocorrect. I also introduced the ‘Fix Song by Songs’ option so you can see how your songs progress.

In the new version the ‘Fix Song by Songs’ option is removed. This is because it was confusing because only some tasks could be fixed song by song, and because even less tasks work song by song now that we have multiple pass release matching. But I have removed the restriction preventing you from scrolling through the results whilst the autocorrect is occurring.

I now have the capacity to allow changing of saves within a task but Im wondering how best to present these options to the user.

First option, have a ‘Save as you go along’ option that would apply during each task, that would be simple but of course all those extra saves would slow down processing time a little. Alternatively have ‘Save as you go along’ option per task.

Secondly what do you actually want the save to do, should it only save changes made by that task, or save anything outstanding. For example if you have made manual changes to a file before autocorrecter, and then run Create Acoustic Ids should it just save the acoustic id, or all the manual changes you made ?

If you have changed the filename should the file be renamed as part of the save ?

Any opionions on this please let me know asap

[dkoh]

Maybe just the way I do things, but is there a need for this?

There are times when I’m working on a 18-release stack, using “match one release” all the way down. Then I use autocorrector to correct grammar, find better images, and fix filenames on the whole list. I find that you can hit ctrl-c then ctrl-v and it “unlocks” Jaikoz to do other tasks. I will close (and save) releases down the list as autocorrector finishes with them.

I think it would be nice to be allowed to other things (like the ctrl-C, V method). I find that running two autocorrectors causes hell, but fixing artwork or genres when autocorrect has already passed is extremely handy.

Maybe an automated save isn’t necessary if you can manually save while autocorrector is running?

…my two cents.

[MAzE5h1p69wB]

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.

[paultaylor]

[quote=dkoh]Maybe just the way I do things, but is there a need for this?

There are times when I’m working on a 18-release stack, using “match one release” all the way down. Then I use autocorrector to correct grammar, find better images, and fix filenames on the whole list. I find that you can hit ctrl-c then ctrl-v and it “unlocks” Jaikoz to do other tasks. I will close (and save) releases down the list as autocorrector finishes with them.

I think it would be nice to be allowed to other things (like the ctrl-C, V method). I find that running two autocorrectors causes hell, but fixing artwork or genres when autocorrect has already passed is extremely handy.

Maybe an automated save isn’t necessary if you can manually save while autocorrector is running?

…my two cents.[/quote]
Hmm, I didnt know you could do this, I dont really like letting you perform editing whilst the files are being used by Autocorrecter because what values should autocorrecter be working on , the values when you started the autocoreccter or values you’ve started changing to after Autocrrecter started. It really isn’t a good idea.

With the new release the Autocorrecter will essentially let you do ‘Match One Release’ in one click, instead of having to do it one album at a time so I think you’ll find you can just run Autocorrecter in one click, and come back to it at the end.

One reason for automated save is to protect against a crash at some point in the process. Of course it would better if Jaikoz never crashed, but even then that would protect against external events like a power cut. Now Im writing this it occurs to me it might be better if Jaikoz wrote changes somewhere so that they could be recovered and saved at a later point, but thats a whole bunch of new work.

[paultaylor]

[quote=MAzE5h1p69wB]Two different parts, here.

1. Autocorrecter
   Save each file once, upon completion of all tasks for that file
   [/quote]
   Thats already possible with the ‘Save Changes’ task but if there is a crash/power cut before you get to that point the nothing gets saved.

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

Thats how it works now I think

[quote=MAzE5h1p69wB]
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.[/quote]
Its kind of impossible to keep track of all chnages to files and whether they were edited manualy or not, furthermore Autocorrect should be interaction free, however Musicbrainz Manual Correct will receive an overhaul soon and I’ll think about this then.