Question about raw processing, srgb, adobe rgb, etc.

You answered every point, splendid :-P
Glad to be of help.
JPEG is 8 bit, right?
Yes, 8 bits per color channel, and there are typically three color channels. Monochrome images often are converted to a profile with only one channel, but this is not strictly necessary.

I understand that radiologists use JPEGs that have ten bits in a single channel, but good luck finding any photography app that will support it.
I believe the world will end before it gets replaced haha.
HEIC/HEIF seems promising, but there is little software support for it.
So the idea here is that I should stay away from shady software and that a nice profile for my monitor will help a lot. Thank you :)
Yes indeed. If you are running apps that are ancient, I'd look into upgrading or replacing them. But just check if everything supports color management.

One further note:

Your monitor needs a device profile, which is produced by a monitor calibrator, and this is typically set in the operating system. Likewise, printers need device profiles as well, and these are installed in the printer driver or other printing app. These profiles will vary depending on the model of printer, the ink set used, and the paper used. Some apps allow "soft proofing" and so need the printer profile referenced in their settings.

Images need to be in a standard color space such as sRGB, Adobe RGB, or ProPhoto RGB, although custom RGB profiles or four-channel CMYK profiles can be used in some circumstances.

Do not convert images to monitor profiles or printer profiles, and do not assign a standard color space like sRGB to a monitor.
Good advice. I have a printer but I don't use it because it works with expensive ink cartridges. It's 23:38 here, bye :-)
 
Define, “truth”.

Colors that render the scene as you saw it?

Colors that render the scene as it was?

Colors that render the scene as you remember it?

Colors that render the scene as you wish it was?

Colors that render the scene in the most pleasing way?
What I get in the screen, how do I make sure it's being displayed "correctly"?
Correctly as in it will match what you print?

They sell color checker devices for that, but I’ve never used them and I’m not familiar with how they work.
I don’t print haha
If you don't print, just use sRGB. Adobe RGB, from my understanding, requires a very disciplined workflow. And for web display it must be converted to sRGB anyway.
 
Some clarification.

A raw image has no colour space. Colours are undefined.

When it's demosaiced, it will be mapped to whatever colour space you specify. This will be stored as part of the image profile, which tells other applications (that read it) how to interpret the colours correctly.

If the display you are working on is not the same as the profile space you used, you need to define a working space that matches it. This normally defaults to the colour space of your local display device.

The profile colours will be mapped to the working space and back again as you edit, so it should not make any difference what profiles space you use.

Now, if you decide to print the image, the print driver will convert it to CMYK. If you use a larger profile, like Adobe RGB or ProPhoto RGB, it will likely exceed the printer gamut, so you won't clip or compress any colours.

If you publish it online, then it's safest to export the image to sRGB as a JPEG. All display devices can decode JPEGs, and sRGB is the default for applications that don't bother reading the profile tag.

However, it is NOT advisable to edit JPEG files. Because they are only 8 bits and heavily compressed, contrast adjustments can cause banding and other issues.

So, edit your raw files in 16-bit mode, even if you use sRGB, and save them as TIFF or PSD files. Only convert them to JPEG when you want to publish them online.
 
Some clarification.

A raw image has no colour space. Colours are undefined.

When it's demosaiced, it will be mapped to whatever colour space you specify. This will be stored as part of the image profile, which tells other applications (that read it) how to interpret the colours correctly.

If the display you are working on is not the same as the profile space you used, you need to define a working space that matches it. This normally defaults to the colour space of your local display device.

The profile colours will be mapped to the working space and back again as you edit, so it should not make any difference what profiles space you use.

Now, if you decide to print the image, the print driver will convert it to CMYK. If you use a larger profile, like Adobe RGB or ProPhoto RGB, it will likely exceed the printer gamut, so you won't clip or compress any colours.

If you publish it online, then it's safest to export the image to sRGB as a JPEG. All display devices can decode JPEGs, and sRGB is the default for applications that don't bother reading the profile tag.

However, it is NOT advisable to edit JPEG files. Because they are only 8 bits and heavily compressed, contrast adjustments can cause banding and other issues.

So, edit your raw files in 16-bit mode, even if you use sRGB, and save them as TIFF or PSD files. Only convert them to JPEG when you want to publish them online.
 
Some clarification.

A raw image has no colour space. Colours are undefined.

When it's demosaiced, it will be mapped to whatever colour space you specify. This will be stored as part of the image profile, which tells other applications (that read it) how to interpret the colours correctly.

If the display you are working on is not the same as the profile space you used, you need to define a working space that matches it. This normally defaults to the colour space of your local display device.

The profile colours will be mapped to the working space and back again as you edit, so it should not make any difference what profiles space you use.

Now, if you decide to print the image, the print driver will convert it to CMYK. If you use a larger profile, like Adobe RGB or ProPhoto RGB, it will likely exceed the printer gamut, so you won't clip or compress any colours.

If you publish it online, then it's safest to export the image to sRGB as a JPEG. All display devices can decode JPEGs, and sRGB is the default for applications that don't bother reading the profile tag.

However, it is NOT advisable to edit JPEG files. Because they are only 8 bits and heavily compressed, contrast adjustments can cause banding and other issues.

So, edit your raw files in 16-bit mode, even if you use sRGB, and save them as TIFF or PSD files. Only convert them to JPEG when you want to publish them online.
Thank you Mr. 57. So with RAW there is no need to worry (I never print). I was talking about the colors that the camera can detect and the color profile made by the manufacturer or some other company for each camera model. When the user chooses “landscape”, the editing program applies some formula to interpret RAW data following that recipe (?)
Sure. Camera profiles can be applied to any colour space. The colour space just matches an actual colour to a specific number.

The reason for user a larger colour space are that more and more devices are now supporting DCI-P3 and other large gamuts (PC, TV, tablets, phones).

ProPhoto RGB will let you export to P3 and other wide gamuts without clipping, now and probably forever. sRGB will not.
 
Thank you Mr. 57. So with RAW there is no need to worry (I never print). I was talking about the colors that the camera can detect
Raw files typically can detect all colors to some degree or another (assuming a color filter array), and maybe radiation that isn't a color at all, like infrared.
and the color profile made by the manufacturer or some other company for each camera model.
The color profile converts the raw data to a standard color space, to a more or less accurate or more or less pleasing degree, where the color space defines colors objectively, as seen under controlled conditions by someone with young, healthy vision.

Profile creation is something of an art as there are a lot factors involved, not all of them objective.
When the user chooses “landscape”, the editing program applies some formula to interpret RAW data following that recipe (?)
It may adjust contrast, saturation, sharpness, and may also adjust specific or overall colors to a greater or lesser degree, or attempt to get some key colors more accurate than others, or keep noise to a minimum, etc. There is a lot that goes into a profile.

It's pretty fascinating stuff if you are mathematically and artistically inclined.
 
Hi. I have a few doubts. I’m using a Nikon D90. When I inspect my photos using the camera’s LCD, they look different -based on how the color space option was set. The manual says one mode is more vivid than the other one. Idk if my camera is bugged but Adobe RGB produces JPEGs with lower saturation (vs sRGB) in replay mode. In the "Nikon D90 Review", colors look more intense using Adobe RGB -according to my web browser.

https://www.dpreview.com/reviews/nikond90/24

0f9d5912e95f431d8482b38518c1924c.jpg.png

So, what is the "truth"? I’m interested in JPEG/RAW (I shoot both) + Nikon software. I ask this because, depending on how I set my monitor profile (I don’t have a custom made one but I can pay someone to make one for me), the RAW file looks different. What is true, what is false? My eyes deceive me, my own computer deceives me. If I choose sRGB in Windows, photos look more saturated when processing RAW (regardless of the color space setting in Nikon’s software. Adobe/sRGB look the same). But If I choose Adobe RGB (in Windows), photos look duller (I like that. And then sRGB/Adobe RGB look both the same).

More doubts/general stuff. Correct me if i’m wrong:

-There is a input space for every camera. Custom ones can be made. Input spaces are huge.

-The option "assign color profile" does not change color RGB numbers, but images can look altered.

-The "convert" option changes color numbers but it aims for the same colors.

Now, part of the confusion comes from the fact that I was playing with options in the operating system/viewing-editing programs, etc. So the ultimate question is: will a monitor profile (made for my own screen) solve my issues? Thanks.

Bonus question: when processing is done and one saves a photo (not RAW) with a color space. Is the program (Photoshop, etc) actually changing the color numbers or is is just a tag?
There are a few issues here.

Let's start with ColorSpace.

A digital image is fundamentally a big grid of squares (we call them pixels). Each square has the number of a crayon assigned to it. Think of a ColorSpace as a box of 16,777,216 numbered crayons.

Different ColorSpaces have different assortments of crayons. If you are working in 8 bot RGB, all ColorSpaces have the same number of Crayons (however, in some wide gamut color spaces, not all the crayons are available).

The important concept is that the ColorSpace specifies the colors that are allowed to appear in your image.

sRGB is the most common ColorSpace. That vast majority of images you see on the web are in sRGB. Adobe RGB increases the color difference between adjacent crayons, and fits in a few more greens. If you want your image to contain a neon green, then you need to use a ColorSpace that includes neon Green.

Keep in mind that if all of the colors in your image fit into sRGB, the image should look the same in wider gamut ColorSpaces. However, if proper color management isn't in place, the colors are more likely to look wrong if you use a wider gamut ColorSpace (hence the warning in the manual).

The next issue is the colors in your raw file.

As it turns out, raw files don't record full color at any of the pixels. Each pixel records only brightness. The pixels are behind a checkerboard pattern of colored filters. Half the pixels are behind green filters, 1/4 are behind blue filters, and 1/4 are behind red filters (this is called a Bayer Pattern Filter).

You need software to guess at what the colors should have been at each pixel. Typically this is done by looking the luminance of the pixel, and the luminance of nearby pixels that are behind other color filters. While it sounds like this can't possibly do a good job, it turns out that it works quite well. The algorithms do a very good job of guessing colors that look pleasing to the human eye. However, these are guesses. Different raw processors can yield different results.

In fact, most manufacturers strive to achieve pleasing color over accurate color. If you are shooting landscapes the camera may accentuate greens. if you are shooting portraits, it may work to get good looking skin tones. A common selling point of many brands is that the colors from that brand "look better", than colors from another brand. Note that the claim is not "more accurate".

Using the manufacturer's software is the best way to get something that matches the camera's jPEG conversion.

.

My advice is that you should work in sRGB. If AdobeRGB images look like they have muted colors, that suggests that your workflow is not properly color managed. In the long term, you can look into calibrating your monitor and your workflow. In the short term, I would suggest working in sRGB.



I would then suggest using the manufacturer's software for processing your raw files. Start with default setting, which should match the JPEGs produced by the camera. You can then make adjustments to control the images.

.

In terms of "accurate colors", that's a big can of worms. First of all, in the real world objects have texture. Texture is visible in the way the object looks different as you move (your eyes get slightly different views, and may see slightly different reflections off the surface). You can not match this with a typical digital image. You need to freeze a moment in time and capture the right reflections to make the viewer think the object has texture. In the extreme case, consider photographing a mirror. The mirror looks like whatever is being reflected in it. The appearance changes as the viewer moves. That doesn't happen in a photograph. Texture is in many ways like lots of tiny mirrors angled differently.

.

The next issue with color is that digital devices simulate color. In the real world an object might be emitting a single wavelength of yellow light. To the human eye that looks yellow. However, the typical digital display cannot emit yellow wavelengths of light. Your monitor emits red and green wavelengths mixed together, and the eye sees that as being the same as a single yellow wavelength. So while digital images can certainly look to the the human eye to be similar to the original color, they are unlikely to produce the same spectral response.

.

Of course the colors we see depends on the lighting. Consider shooting a photo of a neutral grey card outside at noon, and then again at sunset. At sunset, the light coming from the card will contain more yellow and less blue. Is it more "accurate" to record the card as neutral gray, or with the color cast of "magic hour"? What about shooting indoors under tungsten light? Should you record the card as neutral gray, or with the yellowish light of the tungsten bulb? The answer is that you can make a case that any of these options are "accurate". Which you use is usually an artistic, not a technical question.

.

Unless you are in a specific niche where accurate color is key, I wouldn't worry about absolute color accuracy. Go with pleasing color for your art. Let "magic hour" influence the tone of your portraits. Nudge your colors a little cooler or warmer to give emotion to the images. Adjust the color saturation up or down as you see fit. Create images that people will love.
 
Hi. I have a few doubts. I’m using a Nikon D90. When I inspect my photos using the camera’s LCD, they look different -based on how the color space option was set. The manual says one mode is more vivid than the other one. Idk if my camera is bugged but Adobe RGB produces JPEGs with lower saturation (vs sRGB) in replay mode. In the "Nikon D90 Review", colors look more intense using Adobe RGB -according to my web browser.

https://www.dpreview.com/reviews/nikond90/24

0f9d5912e95f431d8482b38518c1924c.jpg.png

So, what is the "truth"? I’m interested in JPEG/RAW (I shoot both) + Nikon software. I ask this because, depending on how I set my monitor profile (I don’t have a custom made one but I can pay someone to make one for me), the RAW file looks different. What is true, what is false? My eyes deceive me, my own computer deceives me. If I choose sRGB in Windows, photos look more saturated when processing RAW (regardless of the color space setting in Nikon’s software. Adobe/sRGB look the same). But If I choose Adobe RGB (in Windows), photos look duller (I like that. And then sRGB/Adobe RGB look both the same).

More doubts/general stuff. Correct me if i’m wrong:

-There is a input space for every camera. Custom ones can be made. Input spaces are huge.

-The option "assign color profile" does not change color RGB numbers, but images can look altered.

-The "convert" option changes color numbers but it aims for the same colors.

Now, part of the confusion comes from the fact that I was playing with options in the operating system/viewing-editing programs, etc. So the ultimate question is: will a monitor profile (made for my own screen) solve my issues? Thanks.

Bonus question: when processing is done and one saves a photo (not RAW) with a color space. Is the program (Photoshop, etc) actually changing the color numbers or is is just a tag?
There are a few issues here.

Let's start with ColorSpace.

A digital image is fundamentally a big grid of squares (we call them pixels). Each square has the number of a crayon assigned to it. Think of a ColorSpace as a box of 16,777,216 numbered crayons.

Different ColorSpaces have different assortments of crayons. If you are working in 8 bot RGB, all ColorSpaces have the same number of Crayons (however, in some wide gamut color spaces, not all the crayons are available).

The important concept is that the ColorSpace specifies the colors that are allowed to appear in your image.

sRGB is the most common ColorSpace. That vast majority of images you see on the web are in sRGB. Adobe RGB increases the color difference between adjacent crayons, and fits in a few more greens. If you want your image to contain a neon green, then you need to use a ColorSpace that includes neon Green.

Keep in mind that if all of the colors in your image fit into sRGB, the image should look the same in wider gamut ColorSpaces. However, if proper color management isn't in place, the colors are more likely to look wrong if you use a wider gamut ColorSpace (hence the warning in the manual).

The next issue is the colors in your raw file.

As it turns out, raw files don't record full color at any of the pixels. Each pixel records only brightness. The pixels are behind a checkerboard pattern of colored filters. Half the pixels are behind green filters, 1/4 are behind blue filters, and 1/4 are behind red filters (this is called a Bayer Pattern Filter).

You need software to guess at what the colors should have been at each pixel. Typically this is done by looking the luminance of the pixel, and the luminance of nearby pixels that are behind other color filters. While it sounds like this can't possibly do a good job, it turns out that it works quite well. The algorithms do a very good job of guessing colors that look pleasing to the human eye. However, these are guesses. Different raw processors can yield different results.

In fact, most manufacturers strive to achieve pleasing color over accurate color. If you are shooting landscapes the camera may accentuate greens. if you are shooting portraits, it may work to get good looking skin tones. A common selling point of many brands is that the colors from that brand "look better", than colors from another brand. Note that the claim is not "more accurate".

Using the manufacturer's software is the best way to get something that matches the camera's jPEG conversion.

.

My advice is that you should work in sRGB. If AdobeRGB images look like they have muted colors, that suggests that your workflow is not properly color managed. In the long term, you can look into calibrating your monitor and your workflow. In the short term, I would suggest working in sRGB.

I would then suggest using the manufacturer's software for processing your raw files. Start with default setting, which should match the JPEGs produced by the camera. You can then make adjustments to control the images.

.

In terms of "accurate colors", that's a big can of worms. First of all, in the real world objects have texture. Texture is visible in the way the object looks different as you move (your eyes get slightly different views, and may see slightly different reflections off the surface). You can not match this with a typical digital image. You need to freeze a moment in time and capture the right reflections to make the viewer think the object has texture. In the extreme case, consider photographing a mirror. The mirror looks like whatever is being reflected in it. The appearance changes as the viewer moves. That doesn't happen in a photograph. Texture is in many ways like lots of tiny mirrors angled differently.

.

The next issue with color is that digital devices simulate color. In the real world an object might be emitting a single wavelength of yellow light. To the human eye that looks yellow. However, the typical digital display cannot emit yellow wavelengths of light. Your monitor emits red and green wavelengths mixed together, and the eye sees that as being the same as a single yellow wavelength. So while digital images can certainly look to the the human eye to be similar to the original color, they are unlikely to produce the same spectral response.

.

Of course the colors we see depends on the lighting. Consider shooting a photo of a neutral grey card outside at noon, and then again at sunset. At sunset, the light coming from the card will contain more yellow and less blue. Is it more "accurate" to record the card as neutral gray, or with the color cast of "magic hour"? What about shooting indoors under tungsten light? Should you record the card as neutral gray, or with the yellowish light of the tungsten bulb? The answer is that you can make a case that any of these options are "accurate". Which you use is usually an artistic, not a technical question.

.

Unless you are in a specific niche where accurate color is key, I wouldn't worry about absolute color accuracy. Go with pleasing color for your art. Let "magic hour" influence the tone of your portraits. Nudge your colors a little cooler or warmer to give emotion to the images. Adjust the color saturation up or down as you see fit. Create images that people will love.
Yes. Things look better in real life. Then I check my photos with a puzzled face :-D But with pretty subjects/lighting, some of the magic is retained. I like colors like these:





I took this with an A850.
I took this with an A850.
 
Thank you Mr. 57. So with RAW there is no need to worry (I never print). I was talking about the colors that the camera can detect
Raw files typically can detect all colors to some degree or another (assuming a color filter array), and maybe radiation that isn't a color at all, like infrared.
and the color profile made by the manufacturer or some other company for each camera model.
The color profile converts the raw data to a standard color space, to a more or less accurate or more or less pleasing degree, where the color space defines colors objectively, as seen under controlled conditions by someone with young, healthy vision.

Profile creation is something of an art as there are a lot factors involved, not all of them objective.
When the user chooses “landscape”, the editing program applies some formula to interpret RAW data following that recipe (?)
It may adjust contrast, saturation, sharpness, and may also adjust specific or overall colors to a greater or lesser degree, or attempt to get some key colors more accurate than others, or keep noise to a minimum, etc. There is a lot that goes into a profile.

It's pretty fascinating stuff if you are mathematically and artistically inclined.
Yes, it is fascinating. I took the "input space" thingy from here:


"...The camera input space above is really big — much bigger than sRGB — and it has a funny shape. It actually goes way off the edges of the a-b grid, with a "green wing" angling upward and outward from the upper left corner, and a "magenta-red wing" angling downward and outward from the lower right corner.

On the one hand, the colors in the "wings" are imaginary colors, meaning they don't correspond to any actual colors you can see out there in the real world. On the other hand, there are colors out there in the real world that this camera-and-input-profile combination can't capture. In particular it misses the most saturated real-world reds and also the most saturated real-world greens and blue-greens."
 
Hi. I have a few doubts. I’m using a Nikon D90. When I inspect my photos using the camera’s LCD, they look different -based on how the color space option was set. The manual says one mode is more vivid than the other one. Idk if my camera is bugged but Adobe RGB produces JPEGs with lower saturation (vs sRGB) in replay mode. In the "Nikon D90 Review", colors look more intense using Adobe RGB -according to my web browser.

https://www.dpreview.com/reviews/nikond90/24

0f9d5912e95f431d8482b38518c1924c.jpg.png

So, what is the "truth"? I’m interested in JPEG/RAW (I shoot both) + Nikon software. I ask this because, depending on how I set my monitor profile (I don’t have a custom made one but I can pay someone to make one for me), the RAW file looks different. What is true, what is false? My eyes deceive me, my own computer deceives me. If I choose sRGB in Windows, photos look more saturated when processing RAW (regardless of the color space setting in Nikon’s software. Adobe/sRGB look the same). But If I choose Adobe RGB (in Windows), photos look duller (I like that. And then sRGB/Adobe RGB look both the same).

More doubts/general stuff. Correct me if i’m wrong:

-There is a input space for every camera. Custom ones can be made. Input spaces are huge.

-The option "assign color profile" does not change color RGB numbers, but images can look altered.

-The "convert" option changes color numbers but it aims for the same colors.

Now, part of the confusion comes from the fact that I was playing with options in the operating system/viewing-editing programs, etc. So the ultimate question is: will a monitor profile (made for my own screen) solve my issues? Thanks.

Bonus question: when processing is done and one saves a photo (not RAW) with a color space. Is the program (Photoshop, etc) actually changing the color numbers or is is just a tag?
There are a few issues here.

Let's start with ColorSpace.

A digital image is fundamentally a big grid of squares (we call them pixels). Each square has the number of a crayon assigned to it. Think of a ColorSpace as a box of 16,777,216 numbered crayons.

Different ColorSpaces have different assortments of crayons. If you are working in 8 bot RGB, all ColorSpaces have the same number of Crayons (however, in some wide gamut color spaces, not all the crayons are available).

The important concept is that the ColorSpace specifies the colors that are allowed to appear in your image.

sRGB is the most common ColorSpace. That vast majority of images you see on the web are in sRGB. Adobe RGB increases the color difference between adjacent crayons, and fits in a few more greens. If you want your image to contain a neon green, then you need to use a ColorSpace that includes neon Green.

Keep in mind that if all of the colors in your image fit into sRGB, the image should look the same in wider gamut ColorSpaces. However, if proper color management isn't in place, the colors are more likely to look wrong if you use a wider gamut ColorSpace (hence the warning in the manual).

The next issue is the colors in your raw file.

As it turns out, raw files don't record full color at any of the pixels. Each pixel records only brightness. The pixels are behind a checkerboard pattern of colored filters. Half the pixels are behind green filters, 1/4 are behind blue filters, and 1/4 are behind red filters (this is called a Bayer Pattern Filter).

You need software to guess at what the colors should have been at each pixel. Typically this is done by looking the luminance of the pixel, and the luminance of nearby pixels that are behind other color filters. While it sounds like this can't possibly do a good job, it turns out that it works quite well. The algorithms do a very good job of guessing colors that look pleasing to the human eye. However, these are guesses. Different raw processors can yield different results.

In fact, most manufacturers strive to achieve pleasing color over accurate color. If you are shooting landscapes the camera may accentuate greens. if you are shooting portraits, it may work to get good looking skin tones. A common selling point of many brands is that the colors from that brand "look better", than colors from another brand. Note that the claim is not "more accurate".

Using the manufacturer's software is the best way to get something that matches the camera's jPEG conversion.

.

My advice is that you should work in sRGB. If AdobeRGB images look like they have muted colors, that suggests that your workflow is not properly color managed. In the long term, you can look into calibrating your monitor and your workflow. In the short term, I would suggest working in sRGB.

I would then suggest using the manufacturer's software for processing your raw files. Start with default setting, which should match the JPEGs produced by the camera. You can then make adjustments to control the images.

.

In terms of "accurate colors", that's a big can of worms. First of all, in the real world objects have texture. Texture is visible in the way the object looks different as you move (your eyes get slightly different views, and may see slightly different reflections off the surface). You can not match this with a typical digital image. You need to freeze a moment in time and capture the right reflections to make the viewer think the object has texture. In the extreme case, consider photographing a mirror. The mirror looks like whatever is being reflected in it. The appearance changes as the viewer moves. That doesn't happen in a photograph. Texture is in many ways like lots of tiny mirrors angled differently.

.

The next issue with color is that digital devices simulate color. In the real world an object might be emitting a single wavelength of yellow light. To the human eye that looks yellow. However, the typical digital display cannot emit yellow wavelengths of light. Your monitor emits red and green wavelengths mixed together, and the eye sees that as being the same as a single yellow wavelength. So while digital images can certainly look to the the human eye to be similar to the original color, they are unlikely to produce the same spectral response.

.

Of course the colors we see depends on the lighting. Consider shooting a photo of a neutral grey card outside at noon, and then again at sunset. At sunset, the light coming from the card will contain more yellow and less blue. Is it more "accurate" to record the card as neutral gray, or with the color cast of "magic hour"? What about shooting indoors under tungsten light? Should you record the card as neutral gray, or with the yellowish light of the tungsten bulb? The answer is that you can make a case that any of these options are "accurate". Which you use is usually an artistic, not a technical question.

.

Unless you are in a specific niche where accurate color is key, I wouldn't worry about absolute color accuracy. Go with pleasing color for your art. Let "magic hour" influence the tone of your portraits. Nudge your colors a little cooler or warmer to give emotion to the images. Adjust the color saturation up or down as you see fit. Create images that people will love.
Yes. Things look better in real life. Then I check my photos with a puzzled face :-D But with pretty subjects/lighting, some of the magic is retained. I like colors like these:

I took this with an A850.
I took this with an A850.
Of course, the colors in your image don't match the colors in real life. I suspect the foreground and background objects were not actually black. If you white balance for the ambient light, the sky would lose that orange glow.

I am not suggesting there is anything wrong with you image. I am just reinforcing the idea that 100% accurate color is hardly a requirement for a wonderful image.
 
Last edited:
Hi. I have a few doubts. I’m using a Nikon D90. When I inspect my photos using the camera’s LCD, they look different -based on how the color space option was set. The manual says one mode is more vivid than the other one. Idk if my camera is bugged but Adobe RGB produces JPEGs with lower saturation (vs sRGB) in replay mode. In the "Nikon D90 Review", colors look more intense using Adobe RGB -according to my web browser.

https://www.dpreview.com/reviews/nikond90/24

0f9d5912e95f431d8482b38518c1924c.jpg.png

So, what is the "truth"? I’m interested in JPEG/RAW (I shoot both) + Nikon software. I ask this because, depending on how I set my monitor profile (I don’t have a custom made one but I can pay someone to make one for me), the RAW file looks different. What is true, what is false? My eyes deceive me, my own computer deceives me. If I choose sRGB in Windows, photos look more saturated when processing RAW (regardless of the color space setting in Nikon’s software. Adobe/sRGB look the same). But If I choose Adobe RGB (in Windows), photos look duller (I like that. And then sRGB/Adobe RGB look both the same).
You got a lot of "history of oil" answers from folk that are very versed in all this stuff, but I think there's a "mechanic's view" that makes it simple...

ALL of your displays have a specific color gamut they can display, and it's way smaller than what the camera can record. In the camera, the raw data is converted to either AdobeRGB or sRGB to make the JPEG, and looking at that on the camera's LCD is at the mercy of the LCD's gamut. My guess is the LCD gamut is closer to sRGB than anything, so the sRGB JPEG will look "more appropriate" than the AdobeRGB JPEG, That's what's behind the assertion that the AdobeRGB images will look less saturated than the sRGB ones.

Now, your desktop display has the same condition, a gamut it can display. Here, you have more control over how pictures are rendered on it, as you can choose to use software that is so-called "color-managed", where you can provide a custom display profile that the software can use to convert the image to the specific display gamut. With that setup, the sRGB and AdobeRGB images can look identical, if the software knows how to interpret the colorspace tags stored in the image.

For ANY media, a down-convert from the camera colorspace to a rendition colorspace is required if the image is expected to look decent. That rendition colorspace should match the capabilities of the medium; otherwise, you just need to expect things to look different on different media.
More doubts/general stuff. Correct me if i’m wrong:

-There is a input space for every camera. Custom ones can be made. Input spaces are huge.
Yes. That's the main part of adding support for specific cameras in raw processors, coming up with the camera primaries.
-The option "assign color profile" does not change color RGB numbers, but images can look altered.
Yes, "assign" is the term used to just associating the image with a profile that describes its gamut and tone. That doesn't in itself change the image, but if the profile doesn't match the image interesting things can happen in color-managed software trying to display it.
-The "convert" option changes color numbers but it aims for the same colors.
Yep, that's how profiles are constructed, to align colorimetrically with the CIE 1931 color-matching experiments.
Now, part of the confusion comes from the fact that I was playing with options in the operating system/viewing-editing programs, etc. So the ultimate question is: will a monitor profile (made for my own screen) solve my issues? Thanks.
Yes, if the image being displayed has an associated colorspace, either from an embedded profile or a metadata tag that names the colorspace. The displaying software needs that information to convert the image to the display colorspace.
Bonus question: when processing is done and one saves a photo (not RAW) with a color space. Is the program (Photoshop, etc) actually changing the color numbers or is is just a tag?
What the program needs to do to be correct is save the image with a color profile, either embedded or tagged, that represents the colorspace to which it is encoded. If the image already matches the intended output colorspace, the conversion isn't needed. But, I wouldn't count on software to be that smart; on export, it may just blindly convert a sRGB image to sRGB... :D
 
Last edited:
Hi. I have a few doubts. I’m using a Nikon D90. When I inspect my photos using the camera’s LCD, they look different -based on how the color space option was set. The manual says one mode is more vivid than the other one. Idk if my camera is bugged but Adobe RGB produces JPEGs with lower saturation (vs sRGB) in replay mode. In the "Nikon D90 Review", colors look more intense using Adobe RGB -according to my web browser.

https://www.dpreview.com/reviews/nikond90/24

0f9d5912e95f431d8482b38518c1924c.jpg.png

So, what is the "truth"? I’m interested in JPEG/RAW (I shoot both) + Nikon software. I ask this because, depending on how I set my monitor profile (I don’t have a custom made one but I can pay someone to make one for me), the RAW file looks different. What is true, what is false? My eyes deceive me, my own computer deceives me. If I choose sRGB in Windows, photos look more saturated when processing RAW (regardless of the color space setting in Nikon’s software. Adobe/sRGB look the same). But If I choose Adobe RGB (in Windows), photos look duller (I like that. And then sRGB/Adobe RGB look both the same).
You got a lot of "history of oil" answers from folk that are very versed in all this stuff, but I think there's a "mechanic's view" that makes it simple...

ALL of your displays have a specific color gamut they can display, and it's way smaller than what the camera can record. In the camera, the raw data is converted to either AdobeRGB or sRGB to make the JPEG, and looking at that on the camera's LCD is at the mercy of the LCD's gamut. My guess is the LCD gamut is closer to sRGB than anything, so the sRGB JPEG will look "more appropriate" than the AdobeRGB JPEG, That's what's behind the assertion that the AdobeRGB images will look less saturated than the sRGB ones.

Now, your desktop display has the same condition, a gamut it can display. Here, you have more control over how pictures are rendered on it, as you can choose to use software that is so-called "color-managed", where you can provide a custom display profile that the software can use to convert the image to the specific display gamut. With that setup, the sRGB and AdobeRGB images can look identical, if the software knows how to interpret the colorspace tags stored in the image.

For ANY media, a down-convert from the camera colorspace to a rendition colorspace is required if the image is expected to look decent. That rendition colorspace should match the capabilities of the medium; otherwise, you just need to expect things to look different on different media.
More doubts/general stuff. Correct me if i’m wrong:

-There is a input space for every camera. Custom ones can be made. Input spaces are huge.
Yes. That's the main part of adding support for specific cameras in raw processors, coming up with the camera primaries.
-The option "assign color profile" does not change color RGB numbers, but images can look altered.
Yes, "assign" is the term used to just associating the image with a profile that describes its gamut and tone. That doesn't in itself change the image, but if the profile doesn't match the image interesting things can happen in color-managed software trying to display it.
-The "convert" option changes color numbers but it aims for the same colors.
Yep, that's how profiles are constructed, to align colorimetrically with the CIE 1931 color-matching experiments.
Now, part of the confusion comes from the fact that I was playing with options in the operating system/viewing-editing programs, etc. So the ultimate question is: will a monitor profile (made for my own screen) solve my issues? Thanks.
Yes, if the image being displayed has an associated colorspace, either from an embedded profile or a metadata tag that names the colorspace. The displaying software needs that information to convert the image to the display colorspace.
Bonus question: when processing is done and one saves a photo (not RAW) with a color space. Is the program (Photoshop, etc) actually changing the color numbers or is is just a tag?
What the program needs to do to be correct is save the image with a color profile, either embedded or tagged, that represents the colorspace to which it is encoded. If the image already matches the intended output colorspace, the conversion isn't needed. But, I wouldn't count on software to be that smart; on export, it may just blindly convert a sRGB image to sRGB... :D
Hi ggbutcher, thanks! Everybody tried to help me and as a result I feel less confused (a lot less). So each display has it's own gamut. The color management software needs to work with a custom profile so it knows the colors that each screen can display and then it doesn't matter much if one is editing photos that were tagged as sRGB, Adobe RGB, etc. But it is a good idea to save the final image with a sRGB tag. If that image is stripped from it's color profile, the action of assigning other profiles to it can lead to funny results. (?)
 
I didn't trawl through all of that but it appears that there's a lot of good advice in there.

For your needs however; I think a lot of that is overkill.

You're using a D90; fourteen year old technology. (Nothing wrong with that, I still use mine sometimes) but it's hardly cutting edge.

My advice would be to simply set the camera to shoot sRGB by default and use sRGB for everything you do subsequently.

On nearly every monitor in the world, you'll never be able to tell the difference.


"It's good to be . . . . . . . . . Me!"
 
I didn't trawl through all of that but it appears that there's a lot of good advice in there.

For your needs however; I think a lot of that is overkill.

You're using a D90; fourteen year old technology. (Nothing wrong with that, I still use mine sometimes) but it's hardly cutting edge.

My advice would be to simply set the camera to shoot sRGB by default and use sRGB for everything you do subsequently.

On nearly every monitor in the world, you'll never be able to tell the difference.

"It's good to be . . . . . . . . . Me!"
Ok ʕ ⊃・ ◡ ・ ʔ⊃
 
Hi. I have a few doubts. I’m using a Nikon D90. When I inspect my photos using the camera’s LCD, they look different -based on how the color space option was set. The manual says one mode is more vivid than the other one. Idk if my camera is bugged but Adobe RGB produces JPEGs with lower saturation (vs sRGB) in replay mode. In the "Nikon D90 Review", colors look more intense using Adobe RGB -according to my web browser.

https://www.dpreview.com/reviews/nikond90/24

0f9d5912e95f431d8482b38518c1924c.jpg.png

So, what is the "truth"? I’m interested in JPEG/RAW (I shoot both) + Nikon software. I ask this because, depending on how I set my monitor profile (I don’t have a custom made one but I can pay someone to make one for me), the RAW file looks different. What is true, what is false? My eyes deceive me, my own computer deceives me. If I choose sRGB in Windows, photos look more saturated when processing RAW (regardless of the color space setting in Nikon’s software. Adobe/sRGB look the same). But If I choose Adobe RGB (in Windows), photos look duller (I like that. And then sRGB/Adobe RGB look both the same).
You got a lot of "history of oil" answers from folk that are very versed in all this stuff, but I think there's a "mechanic's view" that makes it simple...

ALL of your displays have a specific color gamut they can display, and it's way smaller than what the camera can record. In the camera, the raw data is converted to either AdobeRGB or sRGB to make the JPEG, and looking at that on the camera's LCD is at the mercy of the LCD's gamut. My guess is the LCD gamut is closer to sRGB than anything, so the sRGB JPEG will look "more appropriate" than the AdobeRGB JPEG, That's what's behind the assertion that the AdobeRGB images will look less saturated than the sRGB ones.

Now, your desktop display has the same condition, a gamut it can display. Here, you have more control over how pictures are rendered on it, as you can choose to use software that is so-called "color-managed", where you can provide a custom display profile that the software can use to convert the image to the specific display gamut. With that setup, the sRGB and AdobeRGB images can look identical, if the software knows how to interpret the colorspace tags stored in the image.

For ANY media, a down-convert from the camera colorspace to a rendition colorspace is required if the image is expected to look decent. That rendition colorspace should match the capabilities of the medium; otherwise, you just need to expect things to look different on different media.
More doubts/general stuff. Correct me if i’m wrong:

-There is a input space for every camera. Custom ones can be made. Input spaces are huge.
Yes. That's the main part of adding support for specific cameras in raw processors, coming up with the camera primaries.
-The option "assign color profile" does not change color RGB numbers, but images can look altered.
Yes, "assign" is the term used to just associating the image with a profile that describes its gamut and tone. That doesn't in itself change the image, but if the profile doesn't match the image interesting things can happen in color-managed software trying to display it.
-The "convert" option changes color numbers but it aims for the same colors.
Yep, that's how profiles are constructed, to align colorimetrically with the CIE 1931 color-matching experiments.
Now, part of the confusion comes from the fact that I was playing with options in the operating system/viewing-editing programs, etc. So the ultimate question is: will a monitor profile (made for my own screen) solve my issues? Thanks.
Yes, if the image being displayed has an associated colorspace, either from an embedded profile or a metadata tag that names the colorspace. The displaying software needs that information to convert the image to the display colorspace.
Bonus question: when processing is done and one saves a photo (not RAW) with a color space. Is the program (Photoshop, etc) actually changing the color numbers or is is just a tag?
What the program needs to do to be correct is save the image with a color profile, either embedded or tagged, that represents the colorspace to which it is encoded. If the image already matches the intended output colorspace, the conversion isn't needed. But, I wouldn't count on software to be that smart; on export, it may just blindly convert a sRGB image to sRGB... :D
Hi ggbutcher, thanks! Everybody tried to help me and as a result I feel less confused (a lot less). So each display has it's own gamut. The color management software needs to work with a custom profile so it knows the colors that each screen can display and then it doesn't matter much if one is editing photos that were tagged as sRGB, Adobe RGB, etc. But it is a good idea to save the final image with a sRGB tag. If that image is stripped from it's color profile, the action of assigning other profiles to it can lead to funny results. (?)
Yep, pretty much. That said, I'm writing this on a tablet for which I use a sRGB profile as the display profile. Close enough for the tablet's gamut, and I'm too lazy to saunter down to the basement for the ColorMunki... :D
 

Keyboard shortcuts

Back
Top