Render files saved with wrong color profiles #112345

Closed
opened 2023-09-13 19:21:33 +02:00 by Christopher Tyler · 3 comments

System Information
Operating system: macOS-13.4.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M1 Pro 1.2

Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-11 20:52, hash: dd9f196c2e2e
Worked: (newest version of Blender that worked as expected)

Short description of error
4.0 has new color profiles. Renderings, depending on the file type, save/embed either the wrong color profile or none is saved when one should be.

Exact steps for others to reproduce the error
Set the Display Profile to one of the new profiles, such as Display P3. My laptop uses P3 natively so I've been testing it. But this also happens with Rec2020.

After a rendering is done, save the rendering to one of the formats that's capable of embedding an ICC color profile such as JPG, JPG2000, PNG or TIFF. Depending on the format, the Display Profile is ignored, with sRGB being saved for some, or no profile being embedded for others.

So for instance, with Display P3 set for the Display device this is how each of the following formats behaves upon saving:

• JPEG200 --> sRGB embedded (should be P3)
• JPEG --> sRGB embedded (should be P3)
• PNG --> No color profile embedded (should be P3)
• TIFF --> No color profile embedded (should be P3)

In Photoshop's color management is set to 'Preserve Embedded Profiles' and to 'Ask When Opening' for mismatched profiles. Set the RGB working space to something like Adobe RGB (1998) so it's different from sRGB and Display P3 and will therefore notify the user of a mismatch when opening a render file.

In fact something doesn't seem right about how even sRGB is being saved with JPG because the finder shows it has have sRGB as the embedded color profile, but when you open it in Photoshop it doesn't recognize that profile.

In Photoshop, I can resave each of the files once I've assigned the P3 color profile, save it and then upon reopening in Photoshop, they behave correctly. Meaning Photoshop correctly recognizes the file has Display P3 which is a mismatch to the color management settings.

I've uploaded a working Blender file and some saved renderings.

https://drive.google.com/drive/folders/1964tiCotmUZni2e2vKmyXjVjOnh45anc?usp=sharing

**System Information** Operating system: macOS-13.4.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M1 Pro 1.2 **Blender Version** Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-11 20:52, hash: `dd9f196c2e2e` Worked: (newest version of Blender that worked as expected) **Short description of error** 4.0 has new color profiles. Renderings, depending on the file type, save/embed either the wrong color profile or none is saved when one should be. **Exact steps for others to reproduce the error** Set the Display Profile to one of the new profiles, such as Display P3. My laptop uses P3 natively so I've been testing it. But this also happens with Rec2020. After a rendering is done, save the rendering to one of the formats that's capable of embedding an ICC color profile such as JPG, JPG2000, PNG or TIFF. Depending on the format, the Display Profile is ignored, with sRGB being saved for some, or no profile being embedded for others. So for instance, with Display P3 set for the Display device this is how each of the following formats behaves upon saving: • JPEG200 --> sRGB embedded (should be P3) • JPEG --> sRGB embedded (should be P3) • PNG --> No color profile embedded (should be P3) • TIFF --> No color profile embedded (should be P3) In Photoshop's color management is set to 'Preserve Embedded Profiles' and to 'Ask When Opening' for mismatched profiles. Set the RGB working space to something like Adobe RGB (1998) so it's different from sRGB and Display P3 and will therefore notify the user of a mismatch when opening a render file. In fact something doesn't seem right about how even sRGB is being saved with JPG because the finder shows it has have sRGB as the embedded color profile, but when you open it in Photoshop it doesn't recognize that profile. In Photoshop, I can resave each of the files once I've assigned the P3 color profile, save it and then upon reopening in Photoshop, they behave correctly. Meaning Photoshop correctly recognizes the file has Display P3 which is a mismatch to the color management settings. I've uploaded a working Blender file and some saved renderings. https://drive.google.com/drive/folders/1964tiCotmUZni2e2vKmyXjVjOnh45anc?usp=sharing
Christopher Tyler added the
Type
Report
Severity
Normal
Status
Needs Triage
labels 2023-09-13 19:21:33 +02:00
Member

Can confirm, identify -v file.png does only indicate a gamma of 0.4545 on png without srgb tagging or icc profile.

It seems to save post-transform colors to these images.

Can confirm, `identify -v file.png` does only indicate a gamma of 0.4545 on png without srgb tagging or icc profile. It seems to save post-transform colors to these images.
YimingWu added
Module
Render & Cycles
Status
Needs Info from Developers
and removed
Status
Needs Triage
labels 2023-09-14 05:52:31 +02:00

I'm following up with this report. I downloaded the latest release candidate build, and I'm still seeing issues here.

If I set my color management so P3 is my display device, file formats like JPG still save as sRGB. Shouldn't they be saved with P3?

I'm following up with this report. I downloaded the latest release candidate build, and I'm still seeing issues here. If I set my color management so P3 is my display device, file formats like JPG still save as sRGB. Shouldn't they be saved with P3?

I've added this to the To Do list here now: #68926

This is not considered a bug, but a missing feature.

I've added this to the To Do list here now: #68926 This is not considered a bug, but a missing feature.
Blender Bot added
Status
Archived
and removed
Status
Needs Info from Developers
labels 2023-11-13 19:45:39 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#112345
No description provided.