Completely resetting an image

[seanharding]

What is the correct and most thorough way to entirely reset everything about an image so it is processed as if it was brand new? Particularly when I want to see how a new release handles an image I have converted in the past. Sometimes I feel like the "reset" option doesn't wipe everything (but maybe that's just in my head)... Should I delete the row from edits.db? Is there a better way? Just trust that "reset" does the right thing?

[seanharding]

Also, since the settings are tracked by file fingerprint (looks like it's not even a hash of the full contents?), I assume there's no way to make a copy of a file and process it with different settings than the original. Am I missing something on that?

[marcinz606]

"reset" completely nukes everything related to that image (hash) from edits.db and from session.

[seanharding]

Ok, here's an example of the kind of thing I'm worried about. During testing trying to narrow down the issue I describe in #401, I have been repeatedly "reset settings" and exporting on the same file. At some point, something happened where the file started exporting far too magenta. Reset settings didn't fix it. I nuked edits.db (really, renamed it), loaded the same file again, exported without touching anything, and it looks fine. So it seems like SOMETHING persisted past "reset settings" and was messing up the color on this image.

Before deleting edits.db:

After deleting edits.db:

[seanharding]

Seems like the only differences in the db between those two is in local_floors and local_ceils.

Before (too magenta):

  "local_floors": [
    -1.371046025367578,
    -1.4107763596494993,
    -1.3302998705824216
  ],
  "local_ceils": [
    -0.17023609219996383,
    -0.1903589188954058,
    0.07505424619706239
  ],

After (looks ok):

  "local_floors": [
    -1.651103561723232,
    -1.4205274899840352,
    -1.5217355616927144
  ],
  "local_ceils": [
    -0.5566676710615694,
    -0.30650313840013127,
    -0.2228034426341592
  ],