![]() My apologies for not having more definitive things to say. When I use GIMP I edit in GIMP’s built-in sRGB color space unless I’m helping to test GIMP-2.99, which has taken some important steps towards “any RGB”, which I think will also be ported to GIMP-2.10 once it’s working properly. I don’t even try to keep up with these sorts of issues - the situation is very complex and in a constant state of change. The phase of the moon and the day of the week (just kidding ).Whether you are using the “Advanced Color Options” to “assume sRGB” or “convert” - which option you should choose depends on the operation and you’d have to know GIMP and GEGL code better than I do to know which choice is actually correct under what circumstances.Whether the TRC of your profile is “in step” with GIMP’s internal code for switching from linear RGB to RGB encoded using the sRGB TRC.The specific editing operation(s) you happen to use. ![]() ![]() Whether the image’s ICC profile is a “pretty close version” of GIMP’s built-in sRGB profile, in which case just assign the built-in profile upon opening the image file with GIMP and then assign whatever “from disk” sRGB profile you want when you are ready to export back to disk.Rephrasing as a question that’s just about using GIMP: Are results technically correct when editing images in RGB color spaces other than GIMP’s built-in sRGB color space? ![]() Hmm, there’s a great big gap between “what you see on the screen when editing using GIMP or any other image editor” and “what you get when making a print” - room for many issues that have nothing to do with the image editor, and depending on your monitor and the next person’s monitor, there are similar gaps between the image you post to the web and the image someone else sees. If I choose to open a file, keep the embedded profile, edit it in GIMP, then save it to disk for printing or web display, will the colors turn out correctly when displayed/printed? Submitted by Elle Stone Link to original bug (#751030) See this bug report for workarounds and the current state of “when will GIMP finally embed GIMP’s built-in sRGB profile”: GitLab Add the ability to embed the GIMP built-in sRGB profile upon exporting an. Unfortunately assigning (or converting) to GIMP’s built-in sRGB profile currently means this built-in sRGB profile isn’t embedded when you export from GIMP, which can and does cause issues when opening the image with another application. Otherwise there are issues to face and decisions to make. Try just assigning GIMP’s built-in sRGB profile - if you don’t see any color changes in your image, probably all is good. GIMP’s built-in sRGB color space is a functional match to the ArgyllCMS “sRGB.icm”, which as far as I can tell is the real, true, original sRGB profile - see the Addendum to the above article.Īs noted in the article (I wrote the article fwiw) there are actual changes between the various sRGB profiles. It would be nice if all profile vendors distributed the exact same version of the sRGB ICC profile. What are the consequences of converting to the GIMP built-in color space? Is this just a semantic issue or are there are actual changes to the colors in the file happening when I import in this way? My impression is that sRBG is a uniform color space that should allow me to work different applications without color management issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |