
There remains the question as to why set_shot_meter(1,2,2,98,98) doesn’t work.īottom line: by exploring images with RawDigger I have concluded that if I restrict my histo_range counting, using Lapser’s functions, to between 130 (I may go higher for ‘safety’) and 4094, I should have a stable auto bracketing script (at least for my 12b S95 and G11).īTW I have noticed that the G11 is much slower at running my script than the S95. The differences will appear when you test the same image with both profiles and correct settings. In other words, data at the high end of the histogram will be more stable, ie you know where you are at 4094 and below. The current Histogram display in Lightroom and Adobe Camera Raw accurately display the file image data for JPEG, PNG, PSD, TIFF file types, but not for raw files. In contrast, RawDigger is way more oriented toward slow, methodical, scientific analysis of raw data from a single image. Also tons more really useful culling features. I will also initially meter in the dark areas so that my script will only need to take one more bracket at that end. Its designed for quick image browsing & culling and has all the same features you listed above: raw histograms, over/underexposure warnings, etc. Data in this range (130 to 4094) should represent my image data. I believe I can work around the two spikes at 127/1 by sampling above, say, 130, and 4094 and below. Well my script is an auto bracketing one and I wished to ensure I caught ‘all’ the highlights, even speculars. There appears to 'always' be a spike at 4095, also about 2000 count in RawDigger, even when I underexpose and skew the histrogram way to the left.


I have explored the S95 and G11 through RawDigger and now 'understand' what is going on.įirst, when I tried to use set_shot_meter(1,2,2,98,98) it returned an error (nil value).
