....
It's completely not worth the time! maybe if I'm printing, but the gains are lost on the limitations of a display screen.
...and, sadly... I've got a
seriously bad problem w/hot pixels.
I'd pretty much stopped shooting JPG and only shot RAW for the previous 9 months before sending the camera to get fixed. With the broken screen, I couldn't change from RAW and was fine w/that. Now I could so I did. But whoa, when you look @ the JPG in full rez, it's practically unusable! Hot pixels are pretty much eliminated by Lightroom, so it's back to RAW I see.
Back to the HDR.
Spent time d/l'ing some freeware & trialware. Started w/ Qtpfsgui [I couldn't figure it out nor commit the time], then gave HDRShop a try [too "weird" of an interface, and I didn't like it], then settled on FDRTools Basic 2.2.
Shot a bunch of shots @ f/22 at 13sec, 15sec, 20sec & 30sec, natural dim sunlight, of a glowing tube amp. (I have about a dozen and a half tube amps, so more to come one of these days). Took one of the sequences to experiment.
Loaded 4 images and composed a few HDRs until settling on one once I understand how to work it well. Was surprised at how 'dim' the exposure was out. So I needed to load it back into Lightroom, and fiddle w/it anyway.
So I said to myself, well bet I just take my highest exposure image out of the series of 4 I made this HDR from, and copy the Lightroom setting to it, tweek & output, and I bet it would be close. What do you think?
With more time I probably could have gotten the black levels & wall shading even closer. But I think you see what I mean. I think the detail is lost @ 800 px wide. Looking @ full rez or full screen image on a 1900x1200 screen, I see the HDR image shows the detail of the painted wood of the top of the speaker cabinet better... but does
that make all the time I spent making that HDR, then needing to tweek in Lightroom anyway, worth it?
No, not doing
that again. I'll revisit with RAW HDR (in an app that supports PEF) but not bothering w/JPG HDR again (ignoring that I won't be shooting in JPG anyway due to the hot pixel problem :ugh