options for visualising histogram as shot in camera

I nearly always shoot bracketed exposures. I would find it convenient to have the option of when I hover the mouse over the image in lighttable to see a histogram of the image as shot in the camera. Am I the only person who would like to see this or would others like to see it as well? Maybe even the ability to reveal on the thumbnail raw overexposure clipping would be helpful. It would be a bonus if these options were available when hovering the mouse over an image in the filmstrip in the darkroom view too.

I presume it may all be too difficult to implement and maybe not be of much interest to other users of DT. For the moment my solution is to create a style to set WB and exposure as shot in the camera and apply denoise (profiled). This then lets me judge each of the bracketed exposure for noise and highlight details with the histogram as a guide. Then I can reject or edit images based on which has the best exposure.

Aren’t the previews the embedded jpeg?

Depends on: darktable 4.6 user manual - lighttable

If it’s for judging bracketed exposures, what do you gain from a histogram the size of a (largish) post-stamp?
You won’t be able to judge any raw clipping from that (clipping, yes, raw clipping, no)

I strongly suggest you download FastRawViewer and spend 30 days with it. Culling at it’s best.

2 Likes

@dnlyko thanks for the suggestion. I only created this thread to see if others felt the same as me or not. I don’t want to burden developers with feature requests that no one else wants. I like to edit and reject my images in the darkroom view of DT. It is just convenient for my workflow. I feel having a style for exposure as shot will work for me. I then look at the histogram and can decide which of the three shots is best to work with. My camera is a Canon R7 and it benefits from exposing to right without any clipping to minimise noise. I know some cameras like Fuji XT-5 that exposing to the right is not important but on my beasty it is.

BTW, it seems I am alone on this suggestion and I am fine with that. Some of my past suggestions have received traction and been implemented.