Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adobe RGB 1998 Color Profile Retention? #1114

Closed
hamiltondfp opened this issue Feb 5, 2018 · 3 comments
Closed

Adobe RGB 1998 Color Profile Retention? #1114

hamiltondfp opened this issue Feb 5, 2018 · 3 comments
Labels

Comments

@hamiltondfp
Copy link

I am converting an image that is using Adobe RGB (1998) as the color profile. After the conversion, the new image's color profile is sRGB.

After scouring the issues for this library, and looking at libvips, I am currently under the impression that Adobe RGB is not a supported ICC (because it's not supported in libvips yet?), and because the transformations are done in the sRGB space, that is the profile that is retained instead.

Could you please confirm or clarify? Thank you.

@lovell
Copy link
Owner

lovell commented Feb 5, 2018

Hello, if you didn't see it, #218 is the future possible feature that will allow this.

@lovell lovell added the question label Feb 5, 2018
@hamiltondfp
Copy link
Author

hamiltondfp commented Feb 5, 2018

Yes, thanks! That's what I based my assumption on.

Just for the sake of having a thorough understanding: #218 seems to be about converting from one colorspace to another.

The issue I am having is that my image starts as Adobe RGB (1998) and is then sRGB after the transformations.

My understanding is that this is expected behavior, and that the recommended solution is to wait for future functionality that will allow me to to convert the resulting sRGB output back to the original color space, right?

Thanks

@lovell
Copy link
Owner

lovell commented Feb 5, 2018

"the current behaviour is to always convert images to device-independent, non-linear sRGB colour space" #218 (comment)

I've updated the title of #218 as it had become confusing. The following two comments best reflect my thoughts on the possible API.

#218 (comment)
#218 (comment)

In summary, it will provide what you're looking for so perhaps subscribe to it for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants