Dither affects 'File Output' image even when "save as render" is disabled #99651

Open
opened 2022-07-12 17:47:38 +02:00 by Mario Tovirac · 11 comments

Short description of error
The dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when "save as render" is disabled, when disabled it should not touch the output image, when "save as render" is enabled it makes sense to dither.

image.png
noise in output file
image.png

Exact steps for others to reproduce the error

  • Open attached file
  • Optionally change the Dither in {nav Output Properties > Post Processing}
  • hit render
    It will generate an image in the directory pointed to by the node File Output.
    Note that Dither also affects this image.
    Maybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data.

gradient.blend

**Short description of error** The dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when "save as render" is disabled, when disabled it should not touch the output image, when "save as render" is enabled it makes sense to dither. ![image.png](https://archive.blender.org/developer/F13293201/image.png) noise in output file ![image.png](https://archive.blender.org/developer/F13293206/image.png) **Exact steps for others to reproduce the error** - Open attached file - Optionally change the Dither in {nav Output Properties > Post Processing} - hit render It will generate an image in the directory pointed to by the node `File Output`. Note that Dither also affects this image. Maybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data. [gradient.blend](https://archive.blender.org/developer/F13293203/gradient.blend)
Author

Added subscriber: @MarioTovirac

Added subscriber: @MarioTovirac
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Do you have any simple file showing this problem?

Due to the number of daily bug reports, it is preferable for the bug reporter to track down the issue and demonstrate it through a .blend file in order to optimize confirmation.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Do you have any simple file showing this problem? Due to the number of daily bug reports, it is preferable for the bug reporter to track down the issue and demonstrate it through a .blend file in order to optimize confirmation. A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports
Author

Just hit render and it will generate the texture, maybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data

image.png
noise in output file
image.png

gradient.blend

Just hit render and it will generate the texture, maybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data ![image.png](https://archive.blender.org/developer/F13293201/image.png) noise in output file ![image.png](https://archive.blender.org/developer/F13293206/image.png) [gradient.blend](https://archive.blender.org/developer/F13293203/gradient.blend)

I can confirm that the Dither option affects both the render result and the resulting image in the output of the File Output node.
It is indeed a confusing interface, but to fix it would need a design discussion and I'm not sure if it can be considered a bug.

However I encountered another problem. The file attached crashes in the last daily build. Needs investigation...

I can confirm that the Dither option affects both the render result and the resulting image in the output of the `File Output` node. It is indeed a confusing interface, but to fix it would need a design discussion and I'm not sure if it can be considered a bug. However I encountered another problem. The file attached crashes in the last daily build. Needs investigation...
Germano Cavalcante changed title from Dither affects file output image even when "save as render" is disabled to Dither affects 'File Output' image even when "save as render" is disabled 2022-07-15 23:39:06 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

As currently defined in the Manual:

"Save As Render" refers to applying the View Transform, Look, Gamma, Exposure, and RGB Curves under the Color Management panel when saving an image.
https://docs.blender.org/manual/en/3.3/render/color_management.html#image-files

Dithering is a post process effect to break up banding when saving a low bit depth image.
https://docs.blender.org/manual/en/3.3/render/output/properties/post_processing.html#bpy-types-rendersettings-dither-intensity

I don't think that this could be considered a bug, but a feature request.

As currently defined in the Manual: "Save As Render" refers to applying the View Transform, Look, Gamma, Exposure, and RGB Curves under the Color Management panel when saving an image. https://docs.blender.org/manual/en/3.3/render/color_management.html#image-files Dithering is a post process effect to break up banding when saving a low bit depth image. https://docs.blender.org/manual/en/3.3/render/output/properties/post_processing.html#bpy-types-rendersettings-dither-intensity I don't think that this could be considered a bug, but a feature request.

Added subscriber: @Sergey

Added subscriber: @Sergey

The option is indeed only affects color management. Dither is something more global throughout the render pipeline, and is not really considered a color management from the file IO perspective.

I can see how it is confusing, I do not think there is a quick solution to the UI which makes it clear without introducing other kinds of confusion. In a more ideal world it will be somehow better integrated with the selection of Scene Color management, or override, together with the file color management but this requires bigger design changes which is not really part of the bug tracking process,

The option is indeed only affects color management. Dither is something more global throughout the render pipeline, and is not really considered a color management from the file IO perspective. I can see how it is confusing, I do not think there is a quick solution to the UI which makes it clear without introducing other kinds of confusion. In a more ideal world it will be somehow better integrated with the selection of Scene Color management, or override, together with the file color management but this requires bigger design changes which is not really part of the bug tracking process,
Philipp Oeser removed the
Interest
VFX & Video
label 2023-02-10 09:31:30 +01:00
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
5 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#99651
No description provided.