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

ProPhoto RGB images converted to WebP have incorrect colors #2293

Closed
4 tasks done
SigmundurMorkore opened this issue Nov 8, 2022 · 2 comments
Closed
4 tasks done

Comments

@SigmundurMorkore
Copy link

SigmundurMorkore commented Nov 8, 2022

Prerequisites

  • I have written a descriptive issue title
  • I have verified that I am running the latest version of ImageSharp
  • I have verified if the problem exist in both DEBUG and RELEASE mode
  • I have searched open and closed issues to ensure it has not already been reported

ImageSharp version

v2.1.3

Other ImageSharp packages and versions

ImageSharp.Web 2.0.2

Environment (Operating system, version and so on)

Linux and Mac

.NET Framework version

6

Description

When converting this original image:
betri
to WebP using the query: ?format=webp, the resulting image has incorrect colors:
image
(GitHub doesn't allow me to upload WebP images. Have included a URL to the WebP image later on below)

This, as far as I have been able to tell, only happens when the original image is using the color profile "ProPhoto RGB".

Steps to Reproduce

Run a ProPhoto RGB image through ImageSharp.Web with the ?format=webp query.

Images

Original:
betri
WebP Image: https://sansir.cdn.fo/savn/55mi1lvk/betri10.webp?s=lZJR46jg-2NEldLYbPBj_T-Eibs

@brianpopow
Copy link
Collaborator

The issue is, that the color profile is not preserved with version 2.1.3. This was already fixed with PR-2109, but is not yet released with a stable version.

You can try our nightly builds from MyGet

@SigmundurMorkore
Copy link
Author

Aah awesome, we have implemented a work around for now (detecting "KODA" somewhere in the metadata, and then just not converting those to webp), so we'll likely just wait for version 3.0.0 😄 Which I understand should be released sometime in December.

If it has already been fixed, then this issue can be closed.

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

No branches or pull requests

2 participants