ISO is not fake and here is the standards document

Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:


bayer-simulation2.png
 
I’ve heard internet personalities and people on this forum assert that ISO is “fake”, “made up number” etc. but from my testing this did not seem to be true and also there is a standards document describing how the values should be determined:

ABSTRACT PREVIEW

This document specifies the method for assigning and reporting ISO speed ratings, ISO speed latitude ratings, standard output sensitivity values, and recommended exposure index values, for digital still cameras. It is applicable to both monochrome and colour digital still cameras.
The PREVIEW describes it very well. ISO is the camera setting that is necessary to transform a midtone exposure (measured in light per area and time on the sensor) into a recommended midtone in the RAW data. The Preview also explains why this is necessary.
Raw data isn't a picture. It doesn't have any midtones. It's data.
In that sense, a jpeg file is also 'data' and not a picture. One may say that a picture is formed by pixels in an LCD panel or ink droplets on photo paper.

raw data can be interpreted as a picture to render and it may/does have midtones.
My understanding is that the raw data "suggests" something approximating an image.
Not 'approximating', it is an image.
But there isn't a definition of what that image should look like. There are a range of images that are correct representations of the raw file.

The image you get out of Adobe Camera Raw will differ from the image you get out of the manufacture's software. There isn't a standard that suggests one of them is "correct" and the other is not.
For either jpeg or raw, we have

data -> pre-existing render routine -> image on display
The only difference is, there's the wide spread and widely used standard that specifies how to render jpeg files, whereas rendering routines are very specific to each concrete raw format.
It's worse than that. There are multiple rendering routines for each concrete raw format. There is no agreement as to which is correct and which is not.

If everyone thought that only the manufacture's software was correct, there would be no market for other software.

Even if you think the manufacture's software is the only correct software, then which set of options is the one that yields the correct image? For instance, Canon has an option called "highlight tone priority". The raw data is the same whether the option is on or off. Does changing this option in the rendering software produce an incorrect result?

On the other hand there is a well accepted standard on exactly what color to render each RGB pixel value in a JPEG file. Any other color is an incorrect result.

Yes, most people don't have a fully calibrated workflow, and therefore the rendered colors are usually close, but not always exact. This deviation from the ideal is an error.

With raw files, there is no agreed upon standard for what color each pixel should be. Therefore we can't say whether any particular rendering is correct. At best we can say that it looks pleasingly close to what we expect.

As a general rule, it doesn't completely specify the value of any of the pixels in the resulting RGB image. Software has to make educated guesses as to what color to use for the pixels in the RGB file. Technology is at the point where we get very good results. However, different raw processors will guess differently, and will produce different RGB values.

Now the differences may be small, but there will be color shifts from one raw processor to another, and even within the same raw processor with different options. The RAW file does not completely specify what the image should look like.

On the other hand, the values in an RGB image file, along with the associated colorspace, exactly specify colors for each pixel. In a properly calibrated world, the image would look the same on any output device.

Therefore it is not unreasonable to suggest that raw files contain data which must be interpreted before we know what it looks like, while RGB images contain data that specifies exactly how the image should look.
Take a Canon's cr3 raw file, load it into Canon's DPP software and you'll see exactly the same image as an OOC jpeg.
Ideally yes, but in practice no. Last time I checked, there were differences between camera produced JPEGs and JPEGs produced by Canon's DPP software. My understanding was that the camera does not have as much computing power as a typical home computer. In order to maintain acceptable performance, the camera's processing takes some shortcuts to speed things up. The results look close to what DPP produces, but there are not quite the same.
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.



For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
It is a picture but it is not the RAW data. The latter looks like this: 0010110110100...
 
I’ve heard internet personalities and people on this forum assert that ISO is “fake”, “made up number” etc. but from my testing this did not seem to be true and also there is a standards document describing how the values should be determined:

ABSTRACT PREVIEW

This document specifies the method for assigning and reporting ISO speed ratings, ISO speed latitude ratings, standard output sensitivity values, and recommended exposure index values, for digital still cameras. It is applicable to both monochrome and colour digital still cameras.
The PREVIEW describes it very well. ISO is the camera setting that is necessary to transform a midtone exposure (measured in light per area and time on the sensor) into a recommended midtone in the RAW data. The Preview also explains why this is necessary.
Raw data isn't a picture. It doesn't have any midtones. It's data.
In that sense, a jpeg file is also 'data' and not a picture. One may say that a picture is formed by pixels in an LCD panel or ink droplets on photo paper.

raw data can be interpreted as a picture to render and it may/does have midtones.
My understanding is that the raw data "suggests" something approximating an image.
Rawtherapee can show the grgb hidden image as an image for all pixels
As a general rule, it doesn't completely specify the value of any of the pixels in the resulting RGB image. Software has to make educated guesses as to what color to use for the pixels in the RGB file. Technology is at the point where we get very good results. However, different raw processors will guess differently, and will produce different RGB values.

Now the differences may be small, but there will be color shifts from one raw processor to another, and even within the same raw processor with different options. The RAW file does not completely specify what the image should look like.

On the other hand, the values in an RGB image file, along with the associated colorspace, exactly specify colors for each pixel. In a properly calibrated world, the image would look the same on any output device.

Therefore it is not unreasonable to suggest that raw files contain data which must be interpreted before we know what it looks like, while RGB images contain data that specifies exactly how the image should look.
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.

Then what's the point of anyone singling out RAW files to say they're not pictures?
 
Last edited:
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.
Why would you write this after I answered the same objection 10-15 min ago?
Then what's the point of anyone singling out RAW files to say they're not pictures?
Because they are not?
 
Despite the various limitations, digital ISO can be quite useful.

The ISO setting informs the camera of a target exposure (light per unit area on the sensor). The camera can then configure itself to best respond to that target exposure. This may involve choosing between a configuration that supports a higher exposure or one that adds less noise. The camera may also scale the raw data to something it seems appropriate for that exposure.

Both are useful.

As to how dark or how light the image looks, that depends on many factors, not just ISO. For instance, many cameras allow the use to select from a variety of tone curve options. Some compress the highlights to keep them from being blown out. Some boost the shadows to maintain shadow detail.

Most cameras adjust the colors in an attempt to make them more pleasing. Some cameras allow you to select from a variety of color manipulations (Canon offers "portrait" , "landscape" and other styles.

All of these adjustments can affect the lightness of the camera produced JPEG. By adjusting these (and other) settings, you can change the lightness of the JPEG, without altering the scene or the ISO setting.

If you think ISO allows you to accurately predict the results, then you are mistaken. It can usually get you into the ballpark, but there are a lot of complicated mechanisms contributing to image lightness.
All these complications arise from the fact that ISO is applied after processing, not before. Therefore the implementation depends on the processing.

Which is no use at all if you shoot raw.
It depends on the camera.

For instance if you set a high ISO, the camera might configure itself to have less highlight headroom, and to add less noise to the image. This can be helpful with low exposures, even if you are shooting raw.
What does that have to do with the ISO number? They can do that anyway.
That's a reasonable question.

Each ISO setting has a corresponding expected exposure. If you meter a scene, and your meter says that at f/8 and 1/60 you should use ISO 400, then the exposure you get a f/8 and 1/60 is likely appropriate for ISO 400.

When you set the ISO on a digital camera, the camera will expect an exposure that's appropriate for the selected ISO.

Some cameras will make internal configuration adjustments based on that expected exposure.

It is possible for a camera manufacture to separate out those configuration adjustments from the ISO setting, but that's not how typical cameras work.

From a practical matter, setting the ISO value is how you adjust those config settings.

Setting the ISO also sets a target exposure for the camera's metering system, but there is no requirement that you have to make the camera's meter happy.

These are implementation choices on the part of the camera manufacturer.
I can do that myself. How does the manufacturer know what I'm pointing the camera at?
The camera manufacturer doesn't know what you are pointing the camera at. You can let the camera's meter measure the scene, and use Auto-ISO, or you can manually inform the camera what exposure to expect by setting a specific ISO.

For those who are shooting raw, it doesn't hurt to have the ISO be a good fit for the exposure, and it sometimes helps.
For those who shoot raw, it's currently useless.
Not with modern cameras.

Assume you are in a position where motion blur concerns require you to use a shutter of 1/60, and you have the lens wide open at f/2.8

You get a camera produced JPEG with reasonable lightness when you set the ISO to 1600.

You could set the camera to ISO 100, and adjust the lightness when processing. If the results were the same, then there would be no advantage to ISO settings for raw shooters.

It's true that on some cameras, there would be no difference, but on some cameras, the image shot at ISO 1600 would have less noise. This is because some cameras add less noise to the image when set to ISO 1600 than when set to ISO 100. If you have one of these cameras (and many popular cameras fall into this category) then the ISO setting is quite useful to a raw shooter.

If you are using Auto-ISO, the ISO chosen by the camera is useful, and it gives you a rough idea of the exposure you are getting, and therefore a rough idea of how noisy the image will look. If you think the image will have more noise than you find acceptable, you can look at various options for raising exposure (adding more light to the scene, using a tripod for longer shutter, switching to a lens with a wider aperture, etc.) This is helpful even to those who shoot raw.
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.

Then what's the point of anyone singling out RAW files to say they're not pictures?
Why would you write this after I answered the same objection 10-15 min ago?
I don't always read everything in every thread. Looking back, I guess you mean this:

"JPEGs correspond to output pictures. RAWs correspond to an input (of a scene)."

But you yourself say both varieties produce pictures, and that was the question.
Then what's the point of anyone singling out RAW files to say they're not pictures?
Because they are not?
Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
 
Last edited:
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.
Why would you write this after I answered the same objection 10-15 min ago?
Then what's the point of anyone singling out RAW files to say they're not pictures?
Because they are not?
I disagree :-)

They seem to be images images in GRGB rather than RGB. Look at the options in Rawtherapee which gives an "image" of the raw data.
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.

Then what's the point of anyone singling out RAW files to say they're not pictures?
Why would you write this after I answered the same objection 10-15 min ago?
I don't always read everything in every thread. Looking back, I guess you mean this:

"JPEGs correspond to output pictures. RAWs correspond to an input (of a scene)."
That was after I said that JPEG corresponds to a picture by some standards, both the JPEG one and the color space one.
But you yourself say both varieties are pictures, and that was the question.
No, I did not say that. I said that what you posted was a picture. And I said that it was not the RAW.
Then what's the point of anyone singling out RAW files to say they're not pictures?
Because they are not?
Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
The standards used to encode a picture are responsible for the discrimination.
 
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
I think it is a picture inspired by the raw data. It is not the picture represented by the raw data.

There are many other ways of visualizing the data in a raw file. A more common way would be to use full color for each pixel.





So the above is a picture visualizing the raw data. But it is not the only one.

With a JPEG, there is a single correct rendering.
 
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.
Why would you write this after I answered the same objection 10-15 min ago?
Then what's the point of anyone singling out RAW files to say they're not pictures?
Because they are not?
I disagree :-)

They seem to be images images in GRGB rather than RGB.
They may seem that way but they are not. They represent sensor data, with a black point added, encoded linearly, each channel scaled somehow depending on the sensor, those RGB are not the ones we use in any standard color space, and they have that Bayer structure. There is no inherent lightness, for starters.
Look at the options in Rawtherapee which gives an "image" of the raw data.
Good use of the quotation marks.
 
But you yourself say both varieties are pictures, and that was the question.
No, I did not say that. I said that what you posted was a picture. And I said that it was not the RAW.
What I actually ended up posting is this: But you yourself say both varieties produce pictures, and that was the question.

If you didn't say that either, okay, I retract it and will not comment on what you said, or refer to it.
Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
The standards used to encode a picture are responsible for the discrimination.
Both can be considered pictures encoded as data, although one picture might look more familiar than the other.
 
Last edited:
Raw data isn't a picture. It doesn't have any midtones. It's data.
Looks like a picture to me - with midtones:

https://www.red.com/red-101/bayer-sensor-strategy

bayer-simulation2.png
That's an interpretation of the data. There are many other ways of expressing the data that produce different results, but are also reasonable interpretations of the data.

For instance, the spectral response of the red, green and blue pixels in the above image likely don't match the filters in front of the various pixels.
So you think it's not a picture?
I think it is a picture inspired by the raw data.
Good. That's all I'm asking here.
 
Last edited:
But you yourself say both varieties are pictures, and that was the question.
No, I did not say that. I said that what you posted was a picture. And I said that it was not the RAW.
What I actually ended up posting is this: But you yourself say both varieties produce pictures, and that was the question.
No, that was not the question, and you can produce a lot of pictures from the same file. A gray one, for example, why not.

If you didn't say that either, okay, I retract it and will not comment on what you said.
Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
The standards used to encode a picture are responsible for the discrimination.
Both can be considered pictures encoded as data, although one picture might look more familiar than the other.
No, only one of them has a standard to tell you what picture to get.
 
So you think it's not a picture?
It is a picture
I think so too.
but it is not the RAW data. The latter looks like this: 0010110110100...
If that's the criterion for calling something a picture, then no digital file of any kind is a picture either - not even a JPEG.
Why would you write this after I answered the same objection 10-15 min ago?
Then what's the point of anyone singling out RAW files to say they're not pictures?
Because they are not?
I disagree :-)

They seem to be images images in GRGB rather than RGB.
They may seem that way but they are not. They represent sensor data, with a black point added, encoded linearly, each channel scaled somehow depending on the sensor, those RGB are not the ones we use in any standard color space, and they have that Bayer structure. There is no inherent lightness, for starters.
Look at the options in Rawtherapee which gives an "image" of the raw data.
Good use of the quotation marks.
For good reason! It seems to decode the TIFF image block containing the raw data in a linear manner with an appropriate pixel colour. Give it a try and analyze the result.

--
Charles Darwin: "ignorance more frequently begets confidence than does knowledge."
tony
 
Last edited:
But you yourself say both varieties are pictures, and that was the question.
No, I did not say that. I said that what you posted was a picture. And I said that it was not the RAW.
What I actually ended up posting is this: But you yourself say both varieties produce pictures, and that was the question.

If you didn't say that either, okay, I retract it and will not comment on what you said.
Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
The standards used to encode a picture are responsible for the discrimination.
Both can be considered pictures encoded as data, although one picture might look more familiar than the other.
Here's the difference.

With a JPEG, I can tell you exactly what picture corresponds to the data.

With a RAW file, I can a bunch of images that visualize the data. But there is no standard to determine which (if any) is the picture that the raw data represents.

.

The JPEG data specifies an image.

The RAW data suggests a family of images.
 

Keyboard shortcuts

Back
Top