sobol gives nonuniform noise #41143

Closed
opened 2014-07-22 13:51:30 +02:00 by lopata · 10 comments

System Information
win7 x64

Blender Version
blender-2.71-2e43617-win64.zip 87M Tue Jul 22 02:19:39 2014

I do not know, this is bug or feature of algorithm, but in this scene on left side always more lighted. Position of light source into box is irrelevant. Multijitter pattern works normal

sobol.jpg multijitter.jpg

sobol_bug.blend

**System Information** win7 x64 **Blender Version** blender-2.71-2e43617-win64.zip 87M Tue Jul 22 02:19:39 2014 I do not know, this is bug or feature of algorithm, but in this scene on left side always more lighted. Position of light source into box is irrelevant. Multijitter pattern works normal ![sobol.jpg](https://archive.blender.org/developer/F99054/sobol.jpg) ![multijitter.jpg](https://archive.blender.org/developer/F99056/multijitter.jpg) [sobol_bug.blend](https://archive.blender.org/developer/F99058/sobol_bug.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @lopataasdf

Added subscriber: @lopataasdf

Added subscriber: @mont29

Added subscriber: @mont29
Sergey Sharybin self-assigned this 2014-07-22 17:04:36 +02:00

Added subscriber: @brecht

Added subscriber: @brecht

This is a known issue, the Sobol pattern currently has some correlation between pixels in some cases. If you take more samples both will converge to the right result, I would not consider this a bug at the moment.

Perhaps this could be improved by making it so the Cranley-Patterson rotation is different for different dimensions, so you would do something like cmj_hash(*rng, dimension/2) and use that instead of *rng in path_rng_1D. I've tried that before to solve a correlation issue in another scene but it didn't help then, maybe in this case it does.

Sobol is using the same sequence in every pixel, just randomized a bit. Correlated Multi Jitter has a different sequence in every pixel which avoids correlation issues.

This is a known issue, the Sobol pattern currently has some correlation between pixels in some cases. If you take more samples both will converge to the right result, I would not consider this a bug at the moment. Perhaps this could be improved by making it so the Cranley-Patterson rotation is different for different dimensions, so you would do something like `cmj_hash(*rng, dimension/2)` and use that instead of `*rng` in `path_rng_1D`. I've tried that before to solve a correlation issue in another scene but it didn't help then, maybe in this case it does. Sobol is using the same sequence in every pixel, just randomized a bit. Correlated Multi Jitter has a different sequence in every pixel which avoids correlation issues.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

@brecht, using hashed rng seems to help in this particular case, that even doesn't seem to introduce huge amount of slowdown.

But since it didn't work for the scene you've been investigating a while ago, this isn't a reliable solution, unfortunately. So would think of making CMJ more production ready (move it out from experimental, enable for GPU, likely optimize) is the way to go.

So thanks for the report, but to the TODO it goes. Stay tuned!

@brecht, using hashed rng seems to help in this particular case, that even doesn't seem to introduce huge amount of slowdown. But since it didn't work for the scene you've been investigating a while ago, this isn't a reliable solution, unfortunately. So would think of making CMJ more production ready (move it out from experimental, enable for GPU, likely optimize) is the way to go. So thanks for the report, but to the TODO it goes. Stay tuned!

This issue was referenced by blender/cycles@6bcca3d526

This issue was referenced by blender/cycles@6bcca3d5268ae41931cbe47840018a57f22fdc05

This issue was referenced by 9d50175b6c

This issue was referenced by 9d50175b6cc5860926f0974fafd9e8e7868eb805

Changed status from 'Archived' to: 'Resolved'

Changed status from 'Archived' to: 'Resolved'
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#41143
No description provided.