I edited while you were typing, Iliah, please see above. I used the quote marks because we were unable to find that exact phrase in the article; I was not intending to discuss it's meaning.
I edited while you were typing, Iliah, please see above. I used the quote marks because we were unable to find that exact phrase in the article; I was not intending to discuss it's meaning.
If you shunt it the current will divide between the two resistors in proportion to the resistance.
In proportion to the conductance. Or inversely proportional to the resistance. But you know that.
@bobn2 has written:If you shunt it the current will divide between the two resistors in proportion to the resistance.
In proportion to the conductance. Or inversely proportional to the resistance. But you know that.
Indeed, silly mistake.
@cowpatUSA has written: @DannoLeftForums has written: @PeteWanker has written:This scene has quite good brightness but I feel that the blacks and shadows could have been lifted a little.
Whether anyone feels blacks or shadows in an image they are viewing on their monitor [need] lifting or not will depend to some extent on the brightness the monitor is set to.
A given image viewed on a screen [set] to 80 cd/m2 might look a little dark compared to it being viewed on a screen [set] to 190 cd/m2 where it might look OK.
I'm wondering how Pete knew what the scene brightness was ...
I determined it using the exposure triangle.
no comment
I'd prefer a "blinkie" mechanism that puts an indication of "brighter-than-sensor-can-resolve" indication on each pixel thusly affected. Current such mechanisms aren't based on the raw data, so not helpful...
let me get this right ,you like using blinkies but they are not helpful 😏 other wise i like your overall post.
@JimKasson has written: @bobn2 has written:If you shunt it the current will divide between the two resistors in proportion to the resistance.
In proportion to the conductance. Or inversely proportional to the resistance. But you know that.
Indeed, silly mistake.
its been 40years since i studied/played electronics. it just works 😁 and i calibrate the meter without any mathematics ,pretty much the same as my photography.
Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
have you actually tested your histogram accuracy ? because my sony a74 coudnt be any more accurate.
@PeteW has written: @cowpatUSA has written: @DannoLeftForums has written: @PeteWanker has written:This scene has quite good brightness but I feel that the blacks and shadows could have been lifted a little.
Whether anyone feels blacks or shadows in an image they are viewing on their monitor [need] lifting or not will depend to some extent on the brightness the monitor is set to.
A given image viewed on a screen [set] to 80 cd/m2 might look a little dark compared to it being viewed on a screen [set] to 190 cd/m2 where it might look OK.
I'm wondering how Pete knew what the scene brightness was ...
I determined it using the exposure triangle.
no comment
"I determined it using the exposure triangle."
Gold 😁
@ggbutcher has written:Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
have you actually tested your histogram accuracy ? because my sony a74 coudnt be any more accurate.
It's a histogram of a JPEG, and it's accurately histograms that JPEG :))
Gold 😁
Scenes don't have brightness, they have a range of brightnesses. Otherwise they are as emotionally engaging as uniformly lit grey cards are.
Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
Blinkies based on the raw data would be pretty cool, Glenn.
have you actually tested your histogram accuracy ? because my sony a74 coudnt be any more accurate.
That would be interesting to do, Donald, but sadly I don't know how to test the accuracy of my histogram.
As you likely know, a histogram is a set of vertical columns arranged sid-by-side, each column width (or "bin") representing a range of values and each column height representing a count of how many image pixel values are within that range. The problem with my histogram is that it is quite small on the LCD and the bin size/width is not given in the manual and, worse, the column heights are auto-ranged to fit the histogram rectangle height and there is no scale shown on the Y-axis of the histogram diagram. So, for me, it is impossible to check accuracy because I don't know the bin width and I don't know the count for any particular bin.
Would you share how you tested the accuracy of the Sony a74 histogram?
[deleted]
@ggbutcher has written:Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
Blinkies based on the raw data would be pretty cool, Glenn.
@DonaldB has written:have you actually tested your histogram accuracy ? because my sony a74 coudnt be any more accurate.
That would be interesting to do, Donald, but sadly I don't know how to test the accuracy of my histogram.
As you likely know, a histogram is a set of vertical columns arranged sid-by-side, each column width (or "bin") representing a range of values and each column height representing a count of how many image pixel values are within that range. The problem with my histogram is that it is quite small on the LCD and the bin size/width is not given in the manual and, worse, the column heights are auto-ranged to fit the histogram rectangle height and there is no scale shown on the Y-axis of the histogram diagram. So, for me, it is impossible to check accuracy because I don't know the bin width and I don't know the count for any particular bin.
Would you share how you tested the accuracy of the Sony a74 histogram?
theres a thread i started with 1000 posts somewhere on this forum. are raw histograms important or something like that. good luck finding it.
found it
dprevived.com/t/raw-histogram-and-why-does-it-matter/1848/
theres a thread i started with 1000 posts somewhere on this forum.
To prove a fact, one post is usually enough.
A histogram of a JPEG is an accurate (within histogram window width and height constraints) histogram of a JPEG. Ta-daaaa!
I guess this is the time to ask what a histogram actually represents. I guess that depends on the camera? Adobe says:
Most digital cameras have both a luminosity histogram (measuring total brightness) and a color histogram (measuring the intensity of red, green, and blue tones). Adobe Photoshop Lightroom shows both luminosity and colors on the same histogram.
At least in LR, that should be luminance, I guess, which is defined in some color space as R+G+B? Then what is 100% in LR? I guess not quite gray at 33 1/3 %?
I don't know exactly what the Elephant-in-the-room uses but one standard says "When encoding Y’CBCR video, BT.709 creates gamma-encoded luma (Y’) using matrix coefficients 0.2126, 0.7152, and 0.0722"
en.wikipedia.org/wiki/Rec._709
So Luma would be 100% when 0.2126R+ 0.7152G+0.0722B=1.
@xpatUSA has written: @ggbutcher has written:Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
Blinkies based on the raw data would be pretty cool, Glenn.
@DonaldB has written:have you actually tested your histogram accuracy ? because my sony a74 coudnt be any more accurate.
That would be interesting to do, Donald, but sadly I don't know how to test the accuracy of my histogram.
As you likely know, a histogram is a set of vertical columns arranged sid-by-side, each column width (or "bin") representing a range of values and each column height representing a count of how many image pixel values are within that range. The problem with my histogram is that it is quite small on the LCD and the bin size/width is not given in the manual and, worse, the column heights are auto-ranged to fit the histogram rectangle height and there is no scale shown on the Y-axis of the histogram diagram. So, for me, it is impossible to check accuracy because I don't know the bin width and I don't know the count for any particular bin.
Would you share how you tested the accuracy of the Sony a74 histogram?
theres a thread i started with 1000 posts somewhere on this forum. are raw histograms important or something like that. good luck finding it.
found it
dprevived.com/t/raw-histogram-and-why-does-it-matter/1848/
Thanks - I see that you use RawDigger, this is your posted image:
Because the histogram can be scaled at least you can determine counts and bin sizes.
@DonaldB has written: @xpatUSA has written: @ggbutcher has written:Current implementations use the JPEG EVF image, not much use for determining clipping with all the processing applied. I want blinkies based on the raw data.
Blinkies based on the raw data would be pretty cool, Glenn.
@DonaldB has written:have you actually tested your histogram accuracy ? because my sony a74 coudnt be any more accurate.
That would be interesting to do, Donald, but sadly I don't know how to test the accuracy of my histogram.
As you likely know, a histogram is a set of vertical columns arranged sid-by-side, each column width (or "bin") representing a range of values and each column height representing a count of how many image pixel values are within that range. The problem with my histogram is that it is quite small on the LCD and the bin size/width is not given in the manual and, worse, the column heights are auto-ranged to fit the histogram rectangle height and there is no scale shown on the Y-axis of the histogram diagram. So, for me, it is impossible to check accuracy because I don't know the bin width and I don't know the count for any particular bin.
Would you share how you tested the accuracy of the Sony a74 histogram?
theres a thread i started with 1000 posts somewhere on this forum. are raw histograms important or something like that. good luck finding it.
found it
dprevived.com/t/raw-histogram-and-why-does-it-matter/1848/Thanks - I see that you use RawDigger, this is your posted image:
Because the histogram can be scaled at least you can determine counts and bin sizes.
all the posted raw file links wont work as i have deleted the images they were clogging up mu one drive.
any you will get the idea or maybe not its such a merry go round thread with a lot of off topic comments.