If you did you would not be seeing much, and I would not care
If you did you would not be seeing much, and I would not care
[deleted]
What raw reading and how did a raw file give you a reading of 250 250 250
If it was a raw reading and the ceiling was white you would not get 250 250 250 values if it was truly raw reading
sony a6300. perfect histogram 1 tiny pixel from clipping had to use the 3x jewelers loupe again, raw converted 16 bit numbers read 250 250 250
ooc jpeg read 255 255 255.
How embarressing for you guys the a6300 has been out for 7 years đđđ and no one had the sense to test the actual jpeg ,your all to busy
looking at the raws.
Your cherry picking now " 16 bit converted raw read 250 250 250" do i need to explain ?
@DonaldB has written: @JACS has written: @DonaldB has written:lets get this straight AGAIN. the incamera histogram represents at best, the raw file NOT the Jpeg. which part do you not understand ?
You do not know, you are only speculating.
speculating is haveing no proof. i have presented the proof may times. you prove me wrong. Oh you cant because you dont own a sony đ
I have not been to space either but I know that "proofs" that Earth is flat are wrong.
𤣠start posting some sensable material with your camera rather than the arm chair theroies that have brought you all undone đ
raw converted 16 bit numbers read 250 250 250
Again what was the settings of the processing used to create that 16 bit tiff ?
What WB?
What curves?
What color profile?
What BLE adjustment?
All of these influence how at that 16 bit file was created from that raw data
A very simple test to show your competency in what you are trying to show us, it would be to create a tiff file from that raw file that neutralizes even the BLE and the multipliers use in the WB and the raw converters hidden processing. Just doing this would show yourself how silly you are being at insulting much of us.
But you do not understand any of this is you did you would realize how silly you are being and eating a lot of crow
@xpatUSA has written: @DonaldB has written: @DannoLeftForums has written: @DonaldB has written: @DannoLeftForums has written:For a given scene lighting, if you change the WB setting or the colour space in your camera your Sony histogram, like every other camera manufacturer's histogram, will vary đ¤Łđ¤Ł
Im not worried about WB auto is as close as you can get for a camera to be a reliable light meter.
That's fine but given that WB is not applied to the raw data in camera but when the raw data is rendered into a jpeg image either in camera or in post proves that all camera histograms are not a raw histogram.
You stupidly claimed your Sony's camera histogram is a raw histogram đ
Your camera's histogram will vary according to the WB setting and your selected colour space and so cannot possibly be a raw histogram đđ
If you ask the engineers at Sony I can guarantee you 100% they will tell you the camera's histogram is not a raw histogram đ¤Łđ
think about it. if i posted a raw histogram what would the jpeg histogram look like đ¤
The definitive answer is:
a raw histogram
the jpeg histogram
LOL
thank you, you have just proved my findings and point. so if the camera live luminousity histogram was sampling the jpeg then the camera histogram should have been highlight clipped quite a lot.
but guess what ! "IT ISNT"đđđ
Idiot ...
@DonaldB has written:raw converted 16 bit numbers read 250 250 250
Again what was the settings of the processing used to create that 16 bit tiff ?
What WB?
What curves?
What color profile?
What BLE adjustment?
All of these influence how at that 16 bit file was created from that raw dataA very simple test to show your competency in what you are trying to show us, it would be to create a tiff file from that raw file that neutralizes even the BLE and the multipliers use in the WB and the raw converters hidden processing. Just doing this would show yourself how silly you are being at insulting much of us.
But you do not understand any of this is you did you would realize how silly you are being and eating a lot of crow
as ive said it doesnt matter as the jpeg is clipped. couldnt care less what the raw is because the info is all there.
your out of ammo give up.
16 bit converted raw read 250 250 250" do i need to explain ?
Yes and I will ask again
What WB was used?
What color profile was used?
What curves are used?
What BLE was used?
Like you say what don't you understand ?
If you don't understand go back to John's post and review
no comment
đđ
@DonaldB has written:16 bit converted raw read 250 250 250" do i need to explain ?
Yes and I will ask again
What WB was used?
What color profile was used?
What curves are used?
What BLE was used?Like you say what don't you understand ?
If you don't understand go back to John's post and review
as ive said it doesnt matter as the jpeg is clipped. couldnt care less what the raw is because the info is all there.
your out of ammo give up.
couldnt care less what the raw is because the info is all there
And those values that you converted to a 16 bit file that read 250 250 250 are not raw data
@DonaldB has written:couldnt care less what the raw is because the info is all there
And those values that you converted to a 16 bit file that read 250 250 250 are not raw data
I dont care what the raw file is doing ,the fact remains the OOC jpegs has clipped and unreadable information. the raw does not.
and the camera histogram represents the raw file NOT the jpeg.
zoom in on the camera histogram
as ive said it doesnt matter as the jpeg is clipped.
You do realize that if you change the color profile that created that jpeg or even the color space used that jpeg image it may not even show clipping
@DonaldB has written:as ive said it doesnt matter as the jpeg is clipped.
You do realize that if you change the color profile that created that jpeg or even the color space used that jpeg image it may not even show clipping
I have read a paper about using the incamera histogram as a luminence meter and they said auto WB is the best setting. My cameras dont
have RGB live histograms.