I have seen the same thing in my HDR images taken with Olympus OM-D 1MkII, but I have attributed that to the fact that I have been taking images of a single/few high luminance spots (lamps) in a dark environment and I have assumed that there actually isn't that much color.
I have been using both darktable's HDR functionality and a program called HDR Merge. Both produce a linear 32 bit DNG file that I then process normally with exposure compensation, filmic v4, local contrast and color balance. At least in some of my images HDR Merge produced more saturated images but in some cases there was strange noise around the moon and I got a better result with darktable. To my knowledge if you use darktable's HDR functionality it is just "stacking" the images together without any preprocessing. -Juha On Thu, 20 Aug 2020 at 15:24, Patrick Shanahan <p...@opensuse.org> wrote: > * James Buckle <james.buc...@gmail.com> [08-20-20 08:08]: > > No, I appreciate that fact cometely and admitted I'm new to using it. I'm > > not suggesting the application of a number of preparatory steps is > > confusing. > > > > The HDR creation section of the help pages is 5 lines long, 2 of which > are > > "you can generate them in another package" :) There's no info I can find > as > > to what each module is auto-applying and why (and why the result is > > initially very unlike every other HDR generated by other packages). The > > only other documentation I can find on it via darktable.org is a blog > post > > from 2012 which says turn off all auto applied modules as they "make the > > image strange". Can you provide a link to where it tells me why each > module > > is applying values? Maybe a workflow to get to a usable image? > > > > Jeezo, it's not like I'm not trying here - I've spent an hour or two > > searching and faffing and I'm just asking for a little support. > > > > Cheers > > James > > > > > > On Thu, 20 Aug 2020, 12:35 Patrick Shanahan, <p...@opensuse.org> wrote: > > > > > * James Buckle <james.buc...@gmail.com> [08-20-20 05:15]: > > > > That’s curious, shouldn’t it just pull the mean (or at least one) > value > > > from > > > > the constituent input files? > > > > > > > > > > > > > > > > I’ve just tried opening a fresh DNG HDR file and copying the WB > values > > > from the > > > > first image in the series, and it won’t actually allow me to apply > the > > > values, > > > > the sliders move dependant on each other and I can never reach the > same > > > value. > > > > > > > > > > > > > > > > The workflow is really baffling me at the moment as I’m quite new to > this > > > > package, in the history list it has a bunch of operations including > > > input and > > > > output colour corrections that I have not applied manually – not that > > > they seem > > > > to make any difference to the inability to get back to a nice neutral > > > colour > > > > tone. I can get close with the WB sliders, but then it has pretty > much > > > lost all > > > > saturation. I’ve tried following some youtube tutorials but they > don’t > > > seem to > > > > have this issue at all. > > > > > > and this "bafflement" is a direct result of not perusing the ample > > > documentation for darktable. some operations must be applied to the > image > > > to display it in a manner suitable for you to proceed with your > editing. > > > Those operations are what you are seeing. > > > > > > > > > -- > > > (paka)Patrick Shanahan Plainfield, Indiana, USA > @ptilopteri > > > http://en.opensuse.org openSUSE Community Member > facebook/ptilopteri > > > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet > freenode > > > > ___________________________________________________________________________ > > > darktable developer mailing list > > > to unsubscribe send a mail to > > > darktable-dev+unsubscr...@lists.darktable.org > > > > > > > > not familiar with creating hdr images but doesn't one effectively combine > several images to achieve hdr? If so, individual images must be processed > prior to the combining and the steps to process a single (w/o reference to > hdr) image are what you are seeing. > > perhaps your confusion is from starting quite into the process rather than > at the beginning. your reference to "auto applying" is what happens when > one processess an image and they are discussed quite frequently here. > > One of the "auto applied" early in the "preparation" steps to provide you > an image to edit appears, orientation > > open the configuration, gear wheel, and look at that module in presets > you will see it is locked (padlock icon) and auto applied (far right > checkmark) > > and I agree that some things are only learned/obvious thru experimentation > and curiosity. > > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri > http://en.opensuse.org openSUSE Community Member facebook/ptilopteri > Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
