Puzzling RawTherapee Raw Histogram

This looks ā€œfishyā€ to me:

just setting the scale to 1 shows that there are ā€œblockedā€ blue pixels (at least in ART). Iā€™ve checked also with other images and the histograms are in line with what rawdigger shows (again, for ART, which has some slight changes in the way histograms are shown ā€“ I didnā€™t check in RT but I suppose the issue is the same).

1 Like

Thatā€™s suspicious at leastā€¦

This is probably an artifact from the days of old where some scaling was needed to get (most) values within the display range of the histogram. Maybe thatā€™s not needed anymore. Will test! Thanks @agriggio

Things are even a little more confusing, because the drawCurve function that is called to actually draw the lines always scales values to fit the available vertical height. So, having the scale set to 1 or 8 shouldnā€™t even matter for the actual output (just a quick guess).

I created a GitHub issue to investigate further: Raw histogram very different and less insightful than e.g. RawDigger Ā· Issue #5899 Ā· Beep6581/RawTherapee Ā· GitHub

That makes sense, thanks for looking into this Roel. If I understand your and previous comments correctly the main difference is in the lower granularity of the current result.

As mentioned, my interest in a raw histogram is to check the deepest shadows and the brightest highlights, in part in order to understand how much room I have to raise shadows or lower highlights with real vs reconstructed data. I am usually not concerned if a few hundreds to tens of a percent are clipped/blocked, as implied by the Auto Levels button.

Using the capture above as an example, I would consider it ā€˜properlyā€™ Exposed, with clouds and non-specular data obviously fully captured, ending around DN 11500 (I like detail in clouds). @CarVac makes a good point that in this case about a stop in the highlights could probably be recovered without visible damage, so it possibly could have used one more stop of Exposure to similar effect.

Jack

@heckflosse @agriggio @Thanatomanic
Here is a PhaseOne IQ260 raw file of a Sekonic calibration chart.
Note the ADC is 16bit, hence Raw Digger picks 8192 as EV0
Hereā€™s Linear

Hereā€™s log

and here is square root

In the RT histo, if you take EV0 as being the vertical line to the left of the center green peak, then there is some odd scaling going on - if that is, you take Raw Digger as gospel truth.
-1.5Ev in RT seems to scale UP as far as -4Ev, then scale down and compress the hell out of -5Ev and lower.

If any dev wants this IQ260 raw I can send it to them, together with the L*ab specs for the chart patches.

I did think it unlikely, but sometimes it is worth making sure the obvious easy ideas are done away with first.

Thanks Andy for another example. There has been quite some discussion here and there about improving the histogram and scales and gridlines. Iā€™m not sure we can ever get everyone on the same page on all intricacies, but at the very least the histogram should show what you expect. I believe RawDigger can be used as a sort-of ground truth for that. So clearly, RT does something elseā€¦

I would be interested to obtain your sample and specs for further investigation.

@Thanatomanic @heckflosse
Hi Roel

Iā€™ve uploaded the raw to Dropbox folder ā€˜For Roelā€™ Dropbox - For Roel - Simplify your life
Inside you will find the 58.6Mb IIQ raw file and a jpeg shot of the Sekonic data sheet showing patch numbers and grey values in reflectance, Ev and L* formats.

Let me know your thoughts!

I had planned on doing a much requested YT video on the RT histo but because the datum values are not marked I was going to use Raw Digger as well. It was only when running through what I was going to put in the video that I suddenly realised there was something odd going on in the left side of the histogram - it shows how little I use it in day to day work :crazy_face:

But now the point has been raised it would be nice to see at least some scale information.

I like how Raw Digger picks its Ev0 value based on ADC bit depth.

Thanks for sharing! Iā€™ve dived into the code and Iā€™m pretty sure what is going on. Itā€™s actually pretty silly. RawTherapee does the histogram binning before transforming to log. It should definitely do the transformation first, otherwise you bunch up a whole lot of raw values in a single bin that would otherwise be spread out nicely in a log-transformed plot.

3 Likes

That explains the left end then!

Is it fixable?

Toyota.

2 Likes

I never manage well with cryptic clues Ingo - Iā€™m a big fan of simple things like yes and no :thinking: :exploding_head:

In Germany the Toyota slogan is (translated to English) ā€œEverything is possibleā€ or maybe ā€œAll is possibleā€ or maybe ā€œNothing is impossibleā€. Well it is OT here, but just a small advertisement with the slogan https://www.youtube.com/watch?v=LUewLaYwVe4

( Sorry, could not resist. I heard it since I was writing my original comment :slight_smile: )

5 Likes

Ha, having owned a Supra and an Amazon in the past you would think I would have understood, but as I keep saying - Iā€™m thick :crazy_face: :crazy_face:

@JackH I have done some preliminary changes to the histogram. Please see here, Improvements to change main histogram to 65535 bins by Thanatomanic Ā· Pull Request #5904 Ā· Beep6581/RawTherapee Ā· GitHub
Let me know what you think. Suggestions are welcome.

RawToyota: genuine parts, genuine service.

1 Like

Made a comment. :slight_smile:

1 Like

Me too.

1 Like

Hi Roel, the log-log looks very Raw Digger-ish :smiley: :+1: Is this in dev yet by any chance?