• Please use real names.

    Greetings to all who have registered to OPF and those guests taking a look around. Please use real names. Registrations with fictitious names will not be processed. REAL NAMES ONLY will be processed

    Firstname Lastname

    Register

    We are a courteous and supportive community. No need to hide behind an alia. If you have a genuine need for privacy/secrecy then let me know!
  • Welcome to the new site. Here's a thread about the update where you can post your feedback, ask questions or spot those nasty bugs!

Converting web images into sRGB and also embedding the profile

Asher Kelman

OPF Owner/Editor-in-Chief
Edit by CU: This technical discussion has been separated from this picture thread in the Photography as Art forum.


Just a reminder, folks: don't strip the EXIF and make sure that the © statement is in the IPTC statements. If you are lucky, Nestlé or someone else rich will use it! The other point is, ideally, a color profile should be embedded with the file, and generally sRGB for web use.
 
Last edited by a moderator:

Doug Kerr

Well-known member
Hi, Asher,

]Just a reminder, folks: . . . and make sure that the © statement is in the IPTC statements.

Indeed, preferably in both IPTC forms , 'legacy" ("IIM", essentially an Exif extension) and "core" (XML based). (Some "viewing" applications will only read one or the other.)

Some applications, perversely, identify these as "IPTC" and "XML"! (even ExifToolGUI).

The other point is, ideally, a color profile should be embedded with the file, and generally sRGB for web use.

Remind me why that is useful if the color space is a standardized one, such as sRGB (and the image is tagged to show that).

Are we concerned that the displaying application will be sophisticated enough to deal with an embedded profile, but does not have the sRGB profile in its "library"?

Did you perhaps mean to recommend that generally the image should be in the sRGB color space, and be tagged to indicate that?

Thanks.

Best regards,

Doug
 

Asher Kelman

OPF Owner/Editor-in-Chief
Remind me why that is useful if the color space is a standardized one, such as sRGB (and the image is tagged to show that).

Are we concerned that the displaying application will be sophisticated enough to deal with an embedded profile, but does not have the sRGB profile in its "library"?

Did you perhaps mean to recommend that generally the image should be in the sRGB color space, and be tagged to indicate that?

Hi Doug,

The issue is that our software assumes sRGB and all numbers are mapped to that space. Often, the space is that of the camera or a wider RGB space and so colors are not seen as expected in other people's calibrated monitors. Color should be converted to sRGB and never just assigned to sRGB before sending it on the web.

Asher
 

Doug Kerr

Well-known member
Hi, asher,

Hi Doug,

The issue is that our software assumes sRGB and all numbers are mapped to that space. Often, the space is that of the camera or a wider RGB space and so colors are not seen as expected in other people's calibrated monitors. Color should be converted to sRGB and never just assigned to sRGB before sending it on the web.

Sure.

But why would we need to embed the sRGB profile? That is not the same thing as converting the image to be in the sRGB color space.

When we embed a profile, we are sending with the image a definition of the color space the image is recorded in (not just naming it), in case the displaying app never heard of that one.

Best regards,

Doug
 

Asher Kelman

OPF Owner/Editor-in-Chief
Hi, asher,



Sure.

But why would we need to embed the sRGB profile? That is not the same thing as converting the image to be in the sRGB color space.

When we embed a profile, we are sending with the image a definition of the color space the image is recorded in (not just naming it), in case the displaying app never heard of that one.

reread:

Hi Doug,

The issue is that our software assumes sRGB and all numbers are mapped to that space. Often, the space is that of the camera or a wider RGB space and so colors are not seen as expected in other people's calibrated monitors. Color should be converted to sRGB and never just assigned to sRGB before sending it on the web.

So it's pretty simple. Nothing to think about. Just convert to sRGB before sending it off and then embed that with the file.

Asher
 

Cem_Usakligil

Well-known member
So it's pretty simple. Nothing to think about. Just convert to sRGB before sending it off and then embed that with the file.
Hi Asher,

I think that there might be some slight confusion as there are three things here:
1) Converting the colors of an image into a color space (e.g. sRGB in this case).
2) Tagging the image as being in a specific color space, such as sRGB, so that any external application will know that it is sRGB rather than perhaps assume that it might be sRGB. In this case, only a tag for the color profile used is added to the image, not the color profile itself.
3) Embedding the color profile of an image in the image itself, which is the act of putting the technical characteristics of the color space of the sRGB profile into the image.

There is a good discussion about this subject here.

Cheers,
 

Tom Robbins

Active member
A motivated thief can clone out a copyright mark from a photo downloaded from the internet. This is probably a dumb question, but can such an individual (or corporation) also erase or alter the original IPTC statements?
 

Cem_Usakligil

Well-known member
A motivated thief can clone out a copyright mark from a photo downloaded from the internet. This is probably a dumb question, but can such an individual (or corporation) also erase or alter the original IPTC statements?
Unfortunately, yes it is very easy to do so. The copyright notice is not a protection, it is a warning sign which states that you claim to be the owner of this picture. If somebody else changes the IPTC and does the same using your picture, you may have to go to court to claim your rights. If my understanding is correct, you are strongly recommended to register the image copyright with the copyright office in the USA before going to court (for court cases to be handled in USA, that is).

So the wise thing to do is to never post a full sized picture on the net to start with. And if you cannot even stand the thought of somebody stealing your image (even when it is merely 400 pixels wide), then do not post at all. Otherwise, we all have to live with the consequences <sigh>.

Cheers,
 

Doug Kerr

Well-known member
Hi, Asher,

So it's pretty simple. Nothing to think about. Just convert to sRGB before sending it off and then embed that with the file.

Embed that what?

The process of tagging the file to show what color space is used is called "color space tagging". Is that what you mean? It is not called "embedding" of anything.

"Embedding" in this context refers to the matter of including in the file a complete description (not just the "name") of the color space in use.

Which do you have in mind? Once we know, we can recognize the proper way to describe it.

"Nothing to think about" is sure a dangerous observation (especially in this particular discussion, where clearly there is some serious ambiguity afoot).

"Nothing to think about: although the Moon is smaller than the Earth, it is farther away."

Best regards,

Doug
 

Doug Kerr

Well-known member
Hi, Cem,
Hi Asher,

I think that there might be some slight confusion as there are three things here:
1) Converting the colors of an image into a color space (e.g. sRGB in this case).
2) Tagging the image as being in a specific color space, such as sRGB, so that any external application will know that it is sRGB rather than perhaps assume that it might be sRGB. In this case, only a tag for the color profile used is added to the image, not the color profile itself.
3) Embedding the color profile of an image in the image itself, which is the act of putting the technical characteristics of the color space of the sRGB profile into the image.
Thanks so much.

In the more general, case, I would change your third item to read:

Embedding the color profile of an image in the image itself, which is the act of putting the technical characteristics (profile) of the color space in which the image is recorded into the image.​

Best regards,

Doug
 

Tom Robbins

Active member
Unfortunately, yes it is very easy to do so. The copyright notice is not a protection, it is a warning sign which states that you claim to be the owner of this picture. If somebody else changes the IPTC and does the same using your picture, you may have to go to court to claim your rights. If my understanding is correct, you are strongly recommended to register the image copyright with the copyright office in the USA before going to court (for court cases to be handled in USA, that is).

So the wise thing to do is to never post a full sized picture on the net to start with. And if you cannot even stand the thought of somebody stealing your image (even when it is merely 400 pixels wide), then do not post at all. Otherwise, we all have to live with the consequences <sigh>.

Thanks Cem, I was afraid this might be so. Good thing including a copyright statement is as easy to do as it is.
 
Hi, Cem,

Thanks so much.

In the more general, case, I would change your third item to read:

Embedding the color profile of an image in the image itself, which is the act of putting the technical characteristics (profile) of the color space in which the image is recorded into the image.​

Actually, it doesn't even have to be recorded in that color space. Just publishing it in that color space will do just fine ... ;-)

Cheers,
Bart
 

Asher Kelman

OPF Owner/Editor-in-Chief
Actually, it doesn't even have to be recorded in that color space. Just publishing it in that color space will do just fine ... ;-)

Cheers,
Bart
Bart,

That caught my attention, LOL! If the image is recorded in something other than sRGB, to get as close to the "same" appearance, one needs to convert the pictures color space by reassigning their numbers to what would be perceptually the same in the smaller sRGB space. Merely to publish a Profoto RGB created image in an sRGB print space would seem questionable. Aren't we supposed to always convert first?

Asher
 

Mike Bailey

pro member
Good conversation... In case it was overlooked in the heat of the moment, the link mentioned by Cem yesterday "good conversation about... here" was quite informative. It had comments by Andrew Rodney and even the late, great Bruce Fraser. So, if you haven't read it, it'd be good to backtrack for a moment and check it out.

Mike
____________________________

http://bluerockphotography.com
 
Bart,

That caught my attention, LOL! If the image is recorded in something other than sRGB, to get as close to the "same" appearance, one needs to convert the pictures color space by reassigning their numbers to what would be perceptually the same in the smaller sRGB space. Merely to publish a Profoto RGB created image in an sRGB print space would seem questionable. Aren't we supposed to always convert first?

Hi Asher,

Yes, if we want to display colors like we intended them, we need to both convert (if not already in the output colorspace) to an output space (usually a generic one like sRGB if intended for the web) and preferably publish with the correct tag (or even embed the profile if it's not common) so that it can be displayed correctly in a colormanaged environment.

Cheers,
Bart
 

Doug Kerr

Well-known member
Hi, Bart,
Actually, it doesn't even have to be recorded in that color space. Just publishing it in that color space will do just fine

I meant "recorded in the image that is published", not "recorded at the camera".

Probably "represented" would have been a better term.

When we "publish an image in sRGB", we of course mean that, in that image file, the image is represented under the sRGB color space.

Best regards,

Doug
 
Top