Image compression. Noise in black areas of render. #86112

Closed
opened 2021-03-01 02:04:33 +01:00 by Pablo · 7 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40
test2.jpg
Blender Version
Broken: version: 2.92.0 Release Candidate, branch: master, commit date: 2021-02-19 18:02, hash: b1142858d4
All versions.

Output 8bit images contain noise in the black background areas. Default color management settings, Filmic, exposure 0, Gamma 1.0. I've know of this issue for a number of years.
The issue only seems to apply to 8bit outputs. The attached image shows the exposed black level in Photoshop.

To reproduce:
render an empty scene with black background
save to 8 bit png or jpg file
open in image editor to inspect

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40 ![test2.jpg](https://archive.blender.org/developer/F9854126/test2.jpg) **Blender Version** Broken: version: 2.92.0 Release Candidate, branch: master, commit date: 2021-02-19 18:02, hash: `b1142858d4` All versions. Output 8bit images contain noise in the black background areas. Default color management settings, Filmic, exposure 0, Gamma 1.0. I've know of this issue for a number of years. The issue only seems to apply to 8bit outputs. The attached image shows the exposed black level in Photoshop. To reproduce: render an empty scene with black background save to 8 bit png or jpg file open in image editor to inspect
Author

Added subscriber: @OtherRealms

Added subscriber: @OtherRealms
Member

Added subscriber: @filedescriptor

Added subscriber: @filedescriptor
Member

I don't think this is a bug. When you use the 8bit JPEG compressed image format, you are limited to 256 shades of grey. That's just how it is. If you want more color information (especially for dark images), you should use a higher bit depth. You could also use an uncompressed format like PNG which will give you fewer repeating patches and more uniform noise.

I don't think this is a bug. When you use the 8bit JPEG compressed image format, you are limited to 256 shades of grey. That's just how it is. If you want more color information (especially for dark images), you should use a higher bit depth. You could also use an uncompressed format like PNG which will give you fewer repeating patches and more uniform noise.
Author

Hi.
Surely values of 0,0,0 should just produce black though?
I work with large scale LED displays that only deal with an 8bit source, an rgb value of 1 in any channel is clearly visible. I've been flooring the black level in editing software and playing back as 8bit h264/h265. When using doing so in other software, a zero value will effectively mean off. However if I'm not careful a video will slip through that hasn't been floored, since its not visible and hard to detect, anything produced in Blender will result in flickering. I could output 16bit png's in all cases ( I do 50% of cases usually depending on efficiency, some diplays have extreme specs) but was thinking that there must something up on Blenders end. Here's a comparison of 8bit PNG's output and exposed from Cinema 4D and Blender. Blender.png

C4d.png

Hi. Surely values of 0,0,0 should just produce black though? I work with large scale LED displays that only deal with an 8bit source, an rgb value of 1 in any channel is clearly visible. I've been flooring the black level in editing software and playing back as 8bit h264/h265. When using doing so in other software, a zero value will effectively mean off. However if I'm not careful a video will slip through that hasn't been floored, since its not visible and hard to detect, anything produced in Blender will result in flickering. I could output 16bit png's in all cases ( I do 50% of cases usually depending on efficiency, some diplays have extreme specs) but was thinking that there must something up on Blenders end. Here's a comparison of 8bit PNG's output and exposed from Cinema 4D and Blender. ![Blender.png](https://archive.blender.org/developer/F9856196/Blender.png) ![C4d.png](https://archive.blender.org/developer/F9856198/C4d.png)
Member

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Member

I also saw the noise when saving out the image. Per default, Blender applies some dithering as a post-processing step.
If you turn that down to 0.0, you get the expected result.
image.png

Closing this, as it seems to be the expected behavior.

I also saw the noise when saving out the image. Per default, Blender applies some [dithering](https://docs.blender.org/manual/en/latest/render/output/properties/post_processing.html) as a post-processing step. If you turn that down to 0.0, you get the expected result. ![image.png](https://archive.blender.org/developer/F9856376/image.png) Closing this, as it seems to be the expected behavior.
Author

Ah yes makes sense, cheers.

Ah yes makes sense, cheers.
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#86112
No description provided.