First, congrats on a truly remarkable v3 release. I’m so impressed with the great work that has gone into this latest release of darktable.
Second, I’m seeing a replicable and extremely unusual/unexpected behavior that seems to be tied to the Raw Black/White Point module and/or potentially interaction with Lens Correction modules. I am using the official release v3.0.0 on Mac OS X.
I first noticed this unexpected behavior when copying/pasting a stack of edits from one Raw file to another.
What I observed is the edits pasted in and did the expected things, but in addition I am seeing a new and unexpected vertical slice of pixel data (about 1.5% of the image, or for my camera and image, this turns out to be a 78 pixel wide vertical slice) pasted/appended to the right side of the image. This slice of pixel data is not random - it is duplicated from another more central part of the image and appended to the right side of the image.
This comparison/culling view screen capture illustrates the behavior (please ignore the garish colors; the edit stack I copied pasted from an interior shot with completely different white balance).
To see if I could isolate and replicate where in the pipeline the problem was occurring, I walked through the history stack starting at original and then adding one edit at a time to see where the extra pixel data was appended. I observed that the new vertical slice of data was added on the Raw Black/White Point module step in the pipeline.
I tested this by making a new virgin duplicate image, and copying/pasting the editing stack while unchecking the Raw Black/White Point module. When I do this, I end up with a normal/expected image without the vertical stripe of extra image data.
This seems to confirm to me that the problem may be linked to the Raw Black/White Point module step.
I have saved the problematic stack as a style and exported it, and attached it here if it is useful for trying to diagnose or fix the problem.
test_append-to-right.dtstyle (9.0 KB)
I may test uninstalling and reinstalling darktable to see if somehow there’s been a corruption a config file somewhere that’s led to this problem.
If I can provide any additional assistance in diagnosing/testing/fixing this issue, please let me know.