Extend Horizontal (RGB Curves Node) does not work outside the Clipping boundaries #67981

Closed
opened 2019-07-31 08:56:13 +02:00 by Yevgeny Makarov · 10 comments

Blender Version
Broken: 2.80, 2.79

Short description of error

The Extend Horizontal option of the Compositor's RGB Curves Node
does not work (acts as Extrapolated) outside the boundaries set by the Clipping option.

In the Shader Editor, Extend Horizontal works if the endpoint is in the range [0,1],
but if the endpoint is outside [0,1] it acts as the Extrapolated.

compositor:

extend-horizontal-compositor.png

shader editor:

extend-horizontal-shader.png

extend-horizontal-shader-out.png

curve-visualizer-compositor.blend

curve-visualizer-shader.blend

**Blender Version** Broken: 2.80, 2.79 **Short description of error** The **Extend Horizontal** option of the Compositor's **RGB Curves Node** does not work (acts as Extrapolated) outside the boundaries set by the Clipping option. In the Shader Editor, Extend Horizontal works if the endpoint is in the range [0,1], but if the endpoint is outside [0,1] it acts as the Extrapolated. compositor: ![extend-horizontal-compositor.png](https://archive.blender.org/developer/F7638869/extend-horizontal-compositor.png) shader editor: ![extend-horizontal-shader.png](https://archive.blender.org/developer/F7638870/extend-horizontal-shader.png) ![extend-horizontal-shader-out.png](https://archive.blender.org/developer/F7638931/extend-horizontal-shader-out.png) [curve-visualizer-compositor.blend](https://archive.blender.org/developer/F7638902/curve-visualizer-compositor.blend) [curve-visualizer-shader.blend](https://archive.blender.org/developer/F7638903/curve-visualizer-shader.blend)
Author
Member

Added subscriber: @jenkm

Added subscriber: @jenkm
Member

Added subscribers: @Jeroen-Bakker, @lichtwerk

Added subscribers: @Jeroen-Bakker, @lichtwerk
Member

Can confirm for the compositor.
@Jeroen-Bakker: mind having a look here?

Having trouble reproducing the shader example, seems to work fine here (2.8 af4dcc6073)?
curve-visualizer-shader-no-repro.blend
@jenkm: mind attaching a file (already set up to show the failing in the shader case -- might have done something wrong in my file...)

Can confirm for the compositor. @Jeroen-Bakker: mind having a look here? Having trouble reproducing the shader example, seems to work fine here (2.8 af4dcc6073)? [curve-visualizer-shader-no-repro.blend](https://archive.blender.org/developer/F7639281/curve-visualizer-shader-no-repro.blend) @jenkm: mind attaching a file (already set up to show the failing in the shader case -- might have done something wrong in my file...)
Jeroen Bakker was assigned by Philipp Oeser 2019-07-31 11:34:50 +02:00
Author
Member

curve-visualizer-shader-2.blend

set the endpoint to 1.25

extend-horizontal-shader-node.png

it looks correctly in the Look Dev:

extend-horizontal-shader-lookdev.png

but Render wrong:

extend-horizontal-shader-render.png


System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26

Blender Version
Broken: version: 2.81 (sub 0), branch: master, commit date: 2019-07-30 20:50, hash: 5359b7a033

[curve-visualizer-shader-2.blend](https://archive.blender.org/developer/F7639336/curve-visualizer-shader-2.blend) set the endpoint to 1.25 ![extend-horizontal-shader-node.png](https://archive.blender.org/developer/F7639339/extend-horizontal-shader-node.png) it looks correctly in the Look Dev: ![extend-horizontal-shader-lookdev.png](https://archive.blender.org/developer/F7639337/extend-horizontal-shader-lookdev.png) but Render wrong: ![extend-horizontal-shader-render.png](https://archive.blender.org/developer/F7639338/extend-horizontal-shader-render.png) *** **System Information** Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26 **Blender Version** Broken: version: 2.81 (sub 0), branch: master, commit date: 2019-07-30 20:50, hash: `5359b7a033`
Member

Ah, OK, get it, thx for getting back

Ah, OK, get it, thx for getting back
Member

Seems to be a dual state problem.

The CRGB curves stores the horizontal extension per curve C, R, G and B. when evaluating the curves only the horizontal extension of the R, G and B channels are checked. The setting in the C-curve is ignored completely. In the files provided the C channel only has the horizontal extension turned on the rest of the channels are turned off hence the extension is not available. I would suggest that this is not a small change, but we needs some overall guidance how this control needs to work. And based on the outcome of this we should make sure all users use the component the same manner.

an option would be to always draw all curves in the control, so the user sees better what happens. Another option would be to only have a single horizontal extension stored that is used by all 4 curves (limits current implementation, but perhaps easier to understand). The second option will break current files.

Seems to be a dual state problem. The CRGB curves stores the `horizontal extension` per curve C, R, G and B. when evaluating the curves only the horizontal extension of the R, G and B channels are checked. The setting in the C-curve is ignored completely. In the files provided the C channel only has the horizontal extension turned on the rest of the channels are turned off hence the extension is not available. I would suggest that this is not a small change, but we needs some overall guidance how this control needs to work. And based on the outcome of this we should make sure all users use the component the same manner. an option would be to always draw all curves in the control, so the user sees better what happens. Another option would be to only have a single `horizontal extension` stored that is used by all 4 curves (limits current implementation, but perhaps easier to understand). The second option will break current files.
Member

Added subscriber: @brecht

Added subscriber: @brecht
Member

@brecht how can we move forward with this issue? I checked with Bastien, he proposed to check with you.

@brecht how can we move forward with this issue? I checked with Bastien, he proposed to check with you.

Another option would be to only have a single horizontal extension stored that is used by all 4 curves (limits current implementation, but perhaps easier to understand). The second option will break current files.

To me this seems like the right solution, even if it breaks compatibility.

> Another option would be to only have a single horizontal extension stored that is used by all 4 curves (limits current implementation, but perhaps easier to understand). The second option will break current files. To me this seems like the right solution, even if it breaks compatibility.
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' 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
4 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#67981
No description provided.