@Blazej Floch (bfloch) great catch, a patch is definitely welcome.

Hello,
We had problems with Cryptomatte in production on Linux only. This may also be related to other issues I see around here like: https://developer.blender.org/T67712

So if I understand correctly:
1 "Use for Rendering" OFF for a layer of scene A means "keep previous render for that layer" when compositing that layer from a different scene B
2 "Use for Rendering" OFF for a layer of scene A means "dont use that layer in composition" when compositing that layer in the same scene A

In T74082#877812, @Evan Wilson (EAW) wrote:

If you want to hide the cube, hide it in the "cube" scene and rerender with "use to for rendering" ON in that now empty scene.

! In T74082#877847, @thierrry kobyleski (tkobyl) wrote:

The whole point is not to hide the cube with "use to for rendering" ON.
The property "use to for rendering" OFF is very efficient when you know that some layer will not be seen for a given point of view.
It is efficient both in term of rendering time and memory usage.

The idea of D6546 and D6544 is to replace the current bright/contrast node. Before I get into fixing these patches how would this work as far as compatibility? The compatibility will likely be broken, the old node should be removed, it is broken and unfunctional and leaving it in the UI will confuse users.

The idea of D6546 and D6544 is to replace the current bright/contrast node. Before I get into fixing these patches how would this work as far as compatibility? The compatibility will likely be broken, the old node should be removed, it is broken and unfunctional and leaving it in the UI will confuse users.

In T73932#875824, @Evan Wilson (EAW) wrote:

Note @Christoph Werner (Taros) & @Fahad Hasan (cgvirus) : As a non-optimal work around in the meantime, you can keyframe the second frame with the same value, and adjust it to the desired value using the sliders in the dopesheet and the sliders and sidebar in the graph editor. That is if you really want to still use 2.82 or 2.83 before this is fixed.

Note @Christoph Werner (Taros) & @Fahad Hasan (cgvirus) : As a non-optimal work around in the meantime, you can keyframe the second frame with the same value, and adjust it to the desired value using the sliders in the dopesheet and the sliders and sidebar in the graph editor. That is if you really want to still use 2.82 or 2.83 before this is fixed.

Might be a Dupe
https://developer.blender.org/T73932

@ Dani Fraudling (El_Fraudo) please leave the task assignment to the developers '-)

Whoops. I hereby re-assign Brecht as assigned.

I hereby remove Antonio Vazquez as assigned.

A bisect shows that this was caused by rB5d36a2e587590515fb38b4dee71f49b47a339178.

In T73932#874366, @Aaron Carlisle (Blendify) wrote:

Seems to be related to Image sequences, single images work fine.

Seems to be related to Image sequences, single images work fine.

I can confirm

Current file does not load correctly (there is a link between the Value node and the rotate node.

The result of bilinear scaling = nearest scaling for negative integer powers of 2.

No bug here, this is just a consequence of using exact 0.5 factor (other factors do give different results with bilinear vs nearest point methods).

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Do existing files with a rotate node load correctly? I expect this needs some versioning code to convert them?

Also reconfirmed with @Jeroen Bakker (jbakker) that this is only correctly working with the C curve.
So fix is a UI thing: will hide the Film like option when in R G or B curves, and hide R G B when in Film like...

In T60940#867434, @Philipp Oeser (lichtwerk) wrote:

Not knowing the internals well, this really looks "off".

Hi, I think it was explained that the film option is only designed to work with adjustments to the 'C' (luminance) channel.

Maybe it is also expected to break if done on a particular channel [and not done on the "master" C curve only]?

Not knowing the internals well, this really looks "off".
It is especially apparent with soft, gradient like areas, so it breaks quickly with Bloom (like in this case), Glare, Blur and such...

I don't think this will be fixed anytime soon.
Marking as Known Issue then.

Note: The issue you have may be because of Blender not auto-focusing on the windows. You need to click on them before being able to edit things there. I couldn't tell from your video.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Can still confirm if the Render Result is shown anywhere (doesnt have to be a separate window, you can also change the 3DView to an image Editor with the Render Result showing)