sybersitizen
Forum Pro
Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
The Bayer Sensor Strategy
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
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.Not 'approximating', it is an image.My understanding is that the raw data "suggests" something approximating an image.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 isn't a picture. It doesn't have any midtones. It's data.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.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.
raw data can be interpreted as a picture to render and it may/does have midtones.
For either jpeg or raw, we have
data -> pre-existing render routine -> image on display
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.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.
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.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.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.
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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
So you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
It is a picture but it is not the RAW data. The latter looks like this: 0010110110100...So you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
Rawtherapee can show the grgb hidden image as an image for all pixelsMy understanding is that the raw data "suggests" something approximating an image.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 isn't a picture. It doesn't have any midtones. It's data.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.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.
raw data can be interpreted as a picture to render and it may/does have midtones.
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.
I think so too.It is a pictureSo you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Why would you write this after I answered the same objection 10-15 min ago?I think so too.It is a pictureSo you think it's not a picture?
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Because they are not?Then what's the point of anyone singling out RAW files to say they're not pictures?
That's a reasonable question.What does that have to do with the ISO number? They can do that anyway.It depends on the camera.All these complications arise from the fact that ISO is applied after processing, not before. Therefore the implementation depends on the processing.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.
Which is no use at all if you shoot raw.
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.
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.I can do that myself. How does the manufacturer know what I'm pointing the camera at?These are implementation choices on the part of the camera manufacturer.
Not with modern cameras.For those who shoot raw, it's currently useless.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.
I don't always read everything in every thread. Looking back, I guess you mean this:Why would you write this after I answered the same objection 10-15 min ago?I think so too.It is a pictureSo you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Then what's the point of anyone singling out RAW files to say they're not pictures?
Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.Because they are not?Then what's the point of anyone singling out RAW files to say they're not pictures?
I disagreeWhy would you write this after I answered the same objection 10-15 min ago?I think so too.It is a pictureSo you think it's not a picture?
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Because they are not?Then what's the point of anyone singling out RAW files to say they're not pictures?
That was after I said that JPEG corresponds to a picture by some standards, both the JPEG one and the color space one.I don't always read everything in every thread. Looking back, I guess you mean this:Why would you write this after I answered the same objection 10-15 min ago?I think so too.It is a pictureSo you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Then what's the point of anyone singling out RAW files to say they're not pictures?
"JPEGs correspond to output pictures. RAWs correspond to an input (of a scene)."
No, I did not say that. I said that what you posted was a picture. And I said that it was not the RAW.But you yourself say both varieties are pictures, and that was the question.
The standards used to encode a picture are responsible for the discrimination.Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.Because they are not?Then what's the point of anyone singling out RAW files to say they're not pictures?
I think it is a picture inspired by the raw data. It is not the picture represented by the raw data.So you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
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.I disagreeWhy would you write this after I answered the same objection 10-15 min ago?I think so too.It is a pictureSo you think it's not a picture?
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Because they are not?Then what's the point of anyone singling out RAW files to say they're not pictures?
They seem to be images images in GRGB rather than RGB.
Good use of the quotation marks.Look at the options in Rawtherapee which gives an "image" of the raw data.
What I actually ended up posting is this: But you yourself say both varieties produce 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.But you yourself say both varieties are pictures, and that was the question.
Both can be considered pictures encoded as data, although one picture might look more familiar than the other.The standards used to encode a picture are responsible for the discrimination.Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
Good. That's all I'm asking here.I think it is a picture inspired by the raw data.So you think it's not a picture?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.Looks like a picture to me - with midtones:Raw data isn't a picture. It doesn't have any midtones. It's data.
https://www.red.com/red-101/bayer-sensor-strategy
![]()
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.
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.What I actually ended up posting is this: But you yourself say both varieties produce 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.But you yourself say both varieties are pictures, and that was the question.
No, only one of them has a standard to tell you what picture to get.If you didn't say that either, okay, I retract it and will not comment on what you said.
Both can be considered pictures encoded as data, although one picture might look more familiar than the other.The standards used to encode a picture are responsible for the discrimination.Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
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.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.I disagreeWhy would you write this after I answered the same objection 10-15 min ago?I think so too.It is a pictureSo you think it's not a picture?
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.but it is not the RAW data. The latter looks like this: 0010110110100...
Because they are not?Then what's the point of anyone singling out RAW files to say they're not pictures?
They seem to be images images in GRGB rather than RGB.
Good use of the quotation marks.Look at the options in Rawtherapee which gives an "image" of the raw data.
Here's the difference.What I actually ended up posting is this: But you yourself say both varieties produce 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.But you yourself say both varieties are 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.
Both can be considered pictures encoded as data, although one picture might look more familiar than the other.The standards used to encode a picture are responsible for the discrimination.Then it's better to say no digital file is a picture to cover the facts without appearing to be discriminatory.
That's not the question either.No, only one of them has a standard to tell you what picture to get.Both can be considered pictures encoded as data, although one picture might look more familiar than the other.