Maniphest T66099

Color Balance node
Closed, Resolved
Actions

Assigned To
Sergey Sharybin (sergey)
Authored By
Chris Clawson (meloware)
Jun 25 2019, 4:12 AM
Tags
  • BF Blender
Subscribers
Brecht Van Lommel (brecht)
Chris Clawson (meloware)
Sebastian Parborg (zeddb)

Description

Color Balance node will not update Render Result in Image Window, once a Keyframe is set.

bug.zip1 MBDownload

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
  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 T66073, 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.

Related Objects

Mentioned In
rB91e00bd7032e: Fix compositor preview not respecting un-keyed changes
Mentioned Here
rBb3a2de9d181a: Fix T65951 Saving project right before rendering (Cycles) causes empty render…
rB91e00bd7032e: Fix compositor preview not respecting un-keyed changes
rBc3f00d787962: Fix T65447: Mask doesn't update in compositor unless there's motion blur on
T66073: Blender 2.8 Compositor: Viewer broken

Event Timeline

Chris Clawson (meloware) created this task.Jun 25 2019, 4:12 AM
Sebastian Parborg (zeddb) claimed this task.Jun 27 2019, 12:54 PM
Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.
Sebastian Parborg (zeddb) added a subscriber: Sebastian Parborg (zeddb).

I can reproduce the issue, bisecting...

Sebastian Parborg (zeddb) reassigned this task from Sebastian Parborg (zeddb) to Sergey Sharybin (sergey).Jun 27 2019, 2:29 PM

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

Sergey Sharybin (sergey) mentioned this in rB91e00bd7032e: Fix compositor preview not respecting un-keyed changes.Jun 27 2019, 4:22 PM
Sergey Sharybin (sergey) lowered the priority of this task from 50 to 30.Jun 27 2019, 4:22 PM

Unkeyed changes should be fixed by rB91e00bd7032.

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 (brecht) changed the task status from Unknown Status to Resolved.Jun 27 2019, 4:28 PM
Brecht Van Lommel (brecht) added a subscriber: Brecht Van Lommel (brecht).

That one should be fixed by rBb3a2de9d181a: Fix T65951 Saving project right before rendering (Cycles) causes empty render….

Chris Clawson (meloware) added a comment.EditedJun 27 2019, 4:31 PM

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.