Color Balance node #66099

New Issue

Chris Clawson · 2019-06-25T04:12:55+02:00

Chris Clawson commented

2019-06-25 04:12:55 +02:00

Color Balance node will not update Render Result in Image Window, once a Keyframe is set.
bug.zip
System Information
Threadripper 2990WX 64GB Ram
Operating system: Windows 10 64 bit pro
Graphics card: NVIDIA Quadro P2000

Tested with blender-2.80-25772c9e1d2d-win64
Bug appears regardless of CUDA or CPU settings, same effect in both Cycles and Eevee

Directories:

  bug/ has .blend file
  bug/images  has image frames to process
  bug/render is output directory for render

Press F12 to render current image. Notice rendered image in Image Edit window

 and that frames advance when Timeline is advanced to later frames.

Move sliders in Color Balance node. Note interactive changes in Image Edit window.
Set a keyframe for Lift/Gamma/Gain in Color Balance node.
Advance to later frame and then try and adjust Color Balance sliders.

.. at this point, any change to a previously keyframed value will have no effect in
the Image Edit (Render Result) window. New keyframes may still be set, but the user
is unable to see the effect until after a new keyframe is set and manually
re-rendered.

This feature worked properly at and before June 1 (blender-2.80.0-git.b3f96da2e605-windows64)
I use a more advanced version of this setup for movie film restoration. It is very important
to be able to adjust Color Balance sliders and preview results before setting keyframes.

It is possible that this bug is similar to report #66073, but I haven't investigated. The attached file reliably demonstrated this first problem.

Important
The Image Result view (in Image Editor) is also now unstable. Render Result will now disappear
and will not return until program is closed and then re-loaded. Scopes seem unaffected.

Color Balance node will not update Render Result in Image Window, once a Keyframe is set. [bug.zip](https://archive.blender.org/developer/F7546720/bug.zip) **System Information** Threadripper 2990WX 64GB Ram Operating system: Windows 10 64 bit pro Graphics card: NVIDIA Quadro [P2000](https://archive.blender.org/developer/P2000.txt) Tested with blender-2.80-25772c9e1d2d-win64 Bug appears regardless of CUDA or CPU settings, same effect in both Cycles and Eevee Directories: ``` bug/ has .blend file bug/images has image frames to process bug/render is output directory for render ``` 1. Press F12 to render current image. Notice rendered image in Image Edit window ``` and that frames advance when Timeline is advanced to later frames. ``` 2. Move sliders in Color Balance node. Note interactive changes in Image Edit window. 3. Set a keyframe for Lift/Gamma/Gain in Color Balance node. 4. Advance to later frame and then try and adjust Color Balance sliders. .. at this point, any change to a previously keyframed value will have no effect in the Image Edit (Render Result) window. New keyframes may still be set, but the user is unable to see the effect until after a new keyframe is set and manually re-rendered. This feature worked properly at and before June 1 (blender-2.80.0-git.b3f96da2e605-windows64) I use a more advanced version of this setup for movie film restoration. It is very important to be able to adjust Color Balance sliders and preview results before setting keyframes. It is possible that this bug is similar to report #66073, but I haven't investigated. The attached file reliably demonstrated this first problem. ***Important*** The Image Result view (in Image Editor) is also now unstable. Render Result will now disappear and will not return until program is closed and then re-loaded. Scopes seem unaffected.

Chris Clawson commented

2019-06-25 04:12:55 +02:00

Added subscriber: @ChrisClawson

Sebastian Parborg commented

2019-06-27 12:54:55 +02:00

Added subscriber: @ZedDB

Sebastian Parborg self-assigned this 2019-06-27 12:54:55 +02:00

Sebastian Parborg commented

2019-06-27 12:54:55 +02:00

I can reproduce the issue, bisecting...

Sebastian Parborg removed their assignment 2019-06-27 14:29:22 +02:00

Sergey Sharybin was assigned by Sebastian Parborg

2019-06-27 14:29:22 +02:00

Sebastian Parborg commented

2019-06-27 14:29:22 +02:00

It seems like it was this commit that broke it: c3f00d7879

It seems like it was this commit that broke it: c3f00d7879

Sergey Sharybin commented

2019-06-27 16:22:54 +02:00

Unkeyed changes should be fixed by 91e00bd703.

The Image Result view (in Image Editor) is also now unstable. Render Result will now disappear
and will not return until program is closed and then re-loaded. Scopes seem unaffected.

This is not clear to me how to reproduce, please provide more details,

Unkeyed changes should be fixed by 91e00bd703. > The Image Result view (in Image Editor) is also now unstable. Render Result will now disappear > and will not return until program is closed and then re-loaded. Scopes seem unaffected. This is not clear to me how to reproduce, please provide more details,

Brecht Van Lommel commented

2019-06-27 16:28:05 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-06-27 16:28:05 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-06-27 16:28:05 +02:00

Brecht Van Lommel commented

2019-06-27 16:28:05 +02:00

That one should be fixed by b3a2de9d18.

That one should be fixed by b3a2de9d18.

Chris Clawson commented

2019-06-27 16:31:33 +02:00

The detailed bug is repeatable, as was verified by Sebastian.
The second problem (complete loss of the Image Edit view) is very unpredictable. I am unable to create a specific fail scenario. My hope is this second problem may go away, once the detailed bug is fixed. If I am able to create a repeatable example of the disappearing image, I will post it as a new bug and refer to this current report.

I now see Brecht has closed this bug. I will download and re-test my problem after the builder produces another version this evening. If the problem persists, I will re-open this bug.

The detailed bug is repeatable, as was verified by Sebastian. The second problem (complete loss of the Image Edit view) is very unpredictable. I am unable to create a specific fail scenario. My hope is this second problem may go away, once the detailed bug is fixed. If I am able to create a repeatable example of the disappearing image, I will post it as a new bug and refer to this current report. I now see Brecht has closed this bug. I will download and re-test my problem after the builder produces another version this evening. If the problem persists, I will re-open this bug.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Color Balance node #66099