Channels are incorrect when saving out a transparent render of volumes #89894

Closed
opened 2021-07-16 10:00:00 +02:00 by Kasper Arnklit Frandsen · 8 comments

System Information
Operating system: Windows 10
Graphics card: GTX 970

Blender Version
Broken: 2.93

Short description of error
Channels are incorrect when saving out a transparent render of volumes.
Render looks correct in Render preview, but when saving the file, the channels are misaligned and alpha seems to be missing.
For some reason it's is different with Cycles and Eevee, though both have issues.
image.png
I have tried saving out as different formats and bitdepth, PNG, TIFF, OpenEXR with no improvement.
Turning off "transparent" there are no issues.
Issues occur both when saving from the render preview and when outputting renders directly from a batch render.
I have tried creating a new file from scratch and get the exact same issue.

Exact steps for others to reproduce the error
Open the below file and try to render and save.
firepuff.blend

**System Information** Operating system: Windows 10 Graphics card: GTX 970 **Blender Version** Broken: 2.93 **Short description of error** Channels are incorrect when saving out a transparent render of volumes. Render looks correct in Render preview, but when saving the file, the channels are misaligned and alpha seems to be missing. For some reason it's is different with Cycles and Eevee, though both have issues. ![image.png](https://archive.blender.org/developer/F10225761/image.png) I have tried saving out as different formats and bitdepth, PNG, TIFF, OpenEXR with no improvement. Turning off "transparent" there are no issues. Issues occur both when saving from the render preview and when outputting renders directly from a batch render. I have tried creating a new file from scratch and get the exact same issue. **Exact steps for others to reproduce the error** Open the below file and try to render and save. [firepuff.blend](https://archive.blender.org/developer/F10225764/firepuff.blend)

Added subscriber: @Arnklit

Added subscriber: @Arnklit

Hmm it appears Krita is having issues displaying channels and making it worse. The main problem might just be that the alpha is way too dark and I don't understand why.

Hmm it appears Krita is having issues displaying channels and making it worse. The main problem might just be that the alpha is way too dark and I don't understand why.

Looking more into this. I assume this is the same issue as described here https://developer.blender.org/T73152. I can indeed see in the viewer as well that the alpha channel is black.

I however don't understand how you are supposed to work around this. Why is the alpha black if the volume is dense enough that it would block an object behind it if it were in the scene.

Looking more into this. I assume this is the same issue as described here https://developer.blender.org/T73152. I can indeed see in the viewer as well that the alpha channel is black. I however don't understand how you are supposed to work around this. Why is the alpha black if the volume is dense enough that it would block an object behind it if it were in the scene.
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

Thank you for the report. This isn't a bug in Blender, but Krita's inability to handle associated (premultiplied) alpha.
Compositing software such as Blender's compositor, Nuke/Natron, and DaVinci Resolve do accurately handle associated alpha.

Nuke:
Nuke-EEVEE-merge.jpg

Why is the alpha black if the volume is dense enough that it would block an object behind it if it were in the scene.

Ah, but it isn't dense at all. ☺ You set the simulation to be only fire, which is pure emissive light. Light doesn't block light. There isn't anything to occlude (block) what is behind the fire. Setting the density to 1,000 just results in 0, since there is 0 density to begin. Had you set the simulation to be fire + smoke, there would be some smoke to absorb and scatter the light coming from behind the simulation. How much depends on the settings of course.

Suzanne behind the fire Frame 2:
Suzanne-cycles-Metal.jpg
Suzanne behind the fire Frame 2 with exposure down 10 stops. Suzanne is visible behind the fire:
Suzanne-cycles-Metal-neg-10.jpg

We can even make Suzanne glow brighter than the fire with an emission shader, which shines right through the fire showing you that the fire doesn't block anything.

Emission of 250 iirc.
Suzanne-cycles-bright.jpg
Same but exposure down 5 stops.
Suzanne-cycles-bright-neg-5stops-flimicLog.jpg

See #78578 (Blender does not save the alpha channel correctly for volumetric flames / fire with no smoke) for more details. I will merge this report into that one as a duplicate.

Thank you for the report. This isn't a bug in Blender, but [Krita's inability to handle associated (premultiplied) alpha.](https://forum.kde.org/viewtopic.php?f=139&t=151553) Compositing software such as Blender's compositor, Nuke/Natron, and DaVinci Resolve do accurately handle associated alpha. Nuke: ![Nuke-EEVEE-merge.jpg](https://archive.blender.org/developer/F10227204/Nuke-EEVEE-merge.jpg) >Why is the alpha black if the volume is dense enough that it would block an object behind it if it were in the scene. Ah, but it isn't dense at all. ☺ You set the simulation to be only fire, which is pure emissive light. Light doesn't block light. There isn't anything to occlude (block) what is behind the fire. Setting the density to 1,000 just results in 0, since there is 0 density to begin. Had you set the simulation to be fire + smoke, there would be some smoke to absorb and scatter the light coming from behind the simulation. How much depends on the settings of course. Suzanne behind the fire Frame 2: ![Suzanne-cycles-Metal.jpg](https://archive.blender.org/developer/F10227189/Suzanne-cycles-Metal.jpg) Suzanne behind the fire Frame 2 with exposure down 10 stops. Suzanne is visible behind the fire: ![Suzanne-cycles-Metal-neg-10.jpg](https://archive.blender.org/developer/F10227191/Suzanne-cycles-Metal-neg-10.jpg) We can even make Suzanne glow brighter than the fire with an emission shader, which shines right through the fire showing you that the fire doesn't block anything. Emission of 250 iirc. ![Suzanne-cycles-bright.jpg](https://archive.blender.org/developer/F10227194/Suzanne-cycles-bright.jpg) Same but exposure down 5 stops. ![Suzanne-cycles-bright-neg-5stops-flimicLog.jpg](https://archive.blender.org/developer/F10227196/Suzanne-cycles-bright-neg-5stops-flimicLog.jpg) See #78578 (Blender does not save the alpha channel correctly for volumetric flames / fire with no smoke) for more details. I will merge this report into that one as a duplicate.
Member

I forgot to mention: I didn't get any channel misalignment when saving images from your file, and opening them in Blender, Nuke, and GIMP.

I forgot to mention: I didn't get any channel misalignment when saving images from your file, and opening them in Blender, Nuke, and GIMP.
Member

Closed as duplicate of #78578

Closed as duplicate of #78578

Ahhh this all makes so much more sense now. Thanks so much for clearing it up. I really couldn't wrap my head around it.

Ahhh this all makes so much more sense now. Thanks so much for clearing it up. I really couldn't wrap my head around it.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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, Assets & 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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
2 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#89894
No description provided.