I don't use the numbers down in the status bar for such as a histogram. I think things are now aligned between RawDigger and PixInsight. You certainly need to choose whether or not you want to see bias-subtracted values.Įdited by sharkmelley, 16 February 2022 - 02:10 AM. In the end it is possible to see the same values in PixInsight as you see in RawDigger but you need RawDigger and PixInsight both to be set up in the same way. To see the Red, Green, Blue histograms in the PixInsight HistogramTransformation window, the image needs to be demosaiced. The RawDigger histogram you showed is from demosaiced data so you can see the Red, Green, Blue histograms separately (but are they bias-subtracted values?). If I want bias-subtracted values, I explicitly subtract the bias. For instance have you set RawDigger to automatically subtract bias? What 'RAW format preferences' have you set in PixInsight for reading in raw files - is it 'Pure Raw' or 'Demosaiced RGB'? Is white balance set or not? I generally read raw files as 'Pure Raw' and I explicitly run the Debayer process to perform the demosaicing. There are other reasons why RawDigger values might differ from PixInsight. However, to obtain values similar to other apps (like RawDigger) you need to choose the range 0-65535. But you don't have to deal with the floating point numbers - instead PixInsight will allow you to read them out into any range you prefer e.g. A typical 14bit DSLR has integer values in the range 0-16383 and so the values are converted internally into the range 0.0-0.25. Note that PixInsight internally stores values and works on values as floating point values in the range 0.0-1.0 When a raw file is read, it assumes the raw values are integers in the range 0-65535 and scales these to the range 0.0-1.0. The format setting in the HistogramTransformation window or Statistics window does not affect the values you see on the PixInsight status bar when running your cursor over an image i.e. If you open the Statistics process then again you can change the way the values are reported within the Statistics window. In addition, the HistogramTransformation dialog allows you to change the way the values are reported within that window: The Readout Option window in the 'Edit' pull down menu is just another way of doing the same thing. You can change the way these values are reported by hitting the indicated arrow on the status bar, which brings up a further menu: When you run the cursor over an image, the pixel values are reported on the status bar at the bottom of the PixInsight app: I don't know which parts of this you do or do not understand so apologies if I now explain things you already know. The main concern here is that I am using their script WeightedBatchPreprocessing to post-process my raws.

However, I have used the 'FlatContourPlot' script, and the 'HistogramTransformation' process and they show low histogram counts. The other option is that maybe I am using incorrectly their tools.

Now on the Pixinsight, version, I have the Core Version 1.8.8-12 Ripley (圆4). I tend to agree with you that probably RawDigger would be the correct one, as it is a product focused on that type of analysis, so I assume that their histogram would be correct. Newer versions of PixInsight use LibRaw instead of DCRaw and this fixes the problem. DCRaw had a known bug with some Sony cameras (including the A7S) which resulted in values being one quarter of what they should be, so you are seeing peaks of 2000 out of 4096. I think you are using an out-of-date version of PixInsight which uses DCRaw to read the raw files.

Rawdigger green raw export