@afre I don’t see your point.
1594 (0 EV):
hdrmerge 1594-1600:
Maybe I am doing it wrong, which is why I started this thread… I usually go from PhotoFlow to gmic. Since @gadolf is using dt, from dt with everything turned off:
CRW_1597.DNG
hdr6.dng
hdr6.dng + 1.5EV
CRW_1597.DNG (default)
hdr6.dng (default) + 1.5EV
@afre I don’t know what to say except that the only two settings I changed were checking align images at the beginning, and 10 for mask blur radius when saving the hdr, but I can’t see how this could relate to noise.
I just came from repeating it and I got the exact same results as my post above show.
Other thing is that I’m using this binary
hdrmerge-git-20180405.glibc2.14-x86_64.AppImage
from here
Isn’t that unusually high?
Maybe, but on my first set of pictures here in the forum that was the value that prevented artifacts in the highlights (clouds):
… and here
Since then, I’ve been using it as default radius
10 pixels:
3 pixels:
Conclusion: there’s no silver bullet. In this set of images, 3 pixels seems to be more suitable (maybe because there is more detail, maybe because there are no moving objects like clouds…). In these jpgs this is not very clear, but when editing the dngs in Darktable it’s also noticeable that the bigger radius messes with the boundary between darks and highlights
Good point!
Thanks for doing this test. There is a bug in HDRMerge. We’ll fix it soon.
Here’s a dng created by a fixed hdrmerge from all 7 raw files using default settings.
https://filebin.net/k8hy2vjianoplfix/test.dng?t=er8czf8a
I confess that I didn’t quite understood the original issue (since it seemed to work, to me), but anyway, glad to see hdrmerge is better, thanks! I am and will continue be a heavy hdrmerge user.
Where do I find this new version?
The fix is not yet committed. I’ll post here, as soon as it’s committed.
The build from 2018-04-05 you use, does not have this bug.
And this version 2018-04-05 isn’t the latest, correct? Will the latest (the one you’ve just built?) be in jcelaya’s repo?
If you click on the link you posted you will see that the current latest version is from 2018-05-14 (that’s the one with the bug).
The new latest version will be in the repo as soon as the fix is in repo. Currently the fix is on my machine. Will take a day or two.
More precisely, the appimage will be available at most 24 hours after the commit, as it gets built automatically via a cron job that runs daily…
I will wait for the Windows version.
I just commited the fix. Should be in nightly builds soon.
HDRmerge_master_continuous-22-g757f3c4_release_64.zip
uploaded at
https://keybase.pub/gaaned92/LHDR64/
The AppImage is ready: https://github.com/jcelaya/hdrmerge/releases/download/nightly/hdrmerge-git-20180609.glibc2.14-x86_64.AppImage
BTW, when should one use custom white level?