Maybe this is nonsense, but may this have to do with spurious leftovers from earlier installs? Did one of those able to reproduce try with a fresh checkout of master, submodules updated, fresh, unused install location and empty directory for database and config?
I removed the ~/.config/darktable working folder.
As for leftovers, is it possible to happen if I update via obs packages, not manual build?
Well the only workaround I know is exporting to something but original size.
- I first of all duplicated my image having the same strange behaviour,
- have discarded the history stack using lighttable
- newly edited the photo
- → et voilá - DONE.
Please see before (damaged) and after (fine)
I think this is specific to individual photos and its histoy stack (had to this for some but not all of previously editied photos …)
I don’t think this is the same.
But how did you duplicate the photo?
We have already tried that to no success. Thanks anyway.
Either in lightable/selected images/duplicate
or in darkroom/duplicate manager
As I understand it, you’re not duplicating the raw file, just the xmp sidecar file, so you can profit from different editing versions of the same raw file. In duplicate manager, you can even name each one of the copies, if you want.
I have this bug on the latest 3.0rc0.
Windows10
Ricoh GRIII
load the raw dng
to reproduce the border
turn on denoise profiled
change to wavelets auto
change the strength to 0.02
export and you will see the border
If you reset the denoise profiled settings the file will export ok.
Hope that narrows it down for you.
The bug was fixed yesterday
3 Likes