- Posts: 88
- Joined: Sat Dec 17, 2016 2:51 pm
Mon Nov 13, 2023 1:04 pm
The problem is simple:
We have Rec709 projects those have Gamma 2.4-encoded luma.
When we want to make a screenshot to a client, we make a screenshot or a still and send it.
The client opens the received file on a image viewer and gets all shadows boosted, because ICM for still images interpret the image as an sRGB-image with an equivalent gamma 2.2.
So colors are changed, because no gamma 2.4 to 2.2 correction is applied.
My current workaround is:
1) I create a screenshot for a clean feed.
2) I search the screenshot file and add to them an icc profile that contains Rec709 curve. I use a batch script to embed it to the file, because I use a command line software to embedding.
3) I send the file to the client.
The better solution is to create a correct image file directly from Resolve.
Because the most projects are Rec709, only embed a Rec709 icc profile is sufficient for most cases.
We have Rec709 projects those have Gamma 2.4-encoded luma.
When we want to make a screenshot to a client, we make a screenshot or a still and send it.
The client opens the received file on a image viewer and gets all shadows boosted, because ICM for still images interpret the image as an sRGB-image with an equivalent gamma 2.2.
So colors are changed, because no gamma 2.4 to 2.2 correction is applied.
My current workaround is:
1) I create a screenshot for a clean feed.
2) I search the screenshot file and add to them an icc profile that contains Rec709 curve. I use a batch script to embed it to the file, because I use a command line software to embedding.
3) I send the file to the client.
The better solution is to create a correct image file directly from Resolve.
Because the most projects are Rec709, only embed a Rec709 icc profile is sufficient for most cases.