compositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image. #111846

New Issue

Open

opened 2023-09-03 15:54:57 +02:00 by michael campbell · 5 comments

michael campbell commented

2023-09-03 15:54:57 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99

Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-01 21:43, hash: de09bdb510a0
Worked: (4.0 alpha from a few weeks ago not sure of version as deleted now)

Short description of error
Compositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.

Exact steps for others to reproduce the error

Open a new blend file.
Go to the compositor.
Drag in the image file attached below.
Connect the resulting image node's 0_Image output to a viewer node and turn on the backdrop.
Image will be shown.
Now place a blur node between the image node and the viewer node.
Set the x and y values of the blur node to 1 and the size to 1.
Image will blur.
Now change the blur mode to fast gaussian.
Image will go completely black.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99 **Blender Version** Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-09-01 21:43, hash: `de09bdb510a0` Worked: (4.0 alpha from a few weeks ago not sure of version as deleted now) **Short description of error** Compositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image. **Exact steps for others to reproduce the error** 1. Open a new blend file. 2. Go to the compositor. 3. Drag in the image file attached below. 4. Connect the resulting image node's 0_Image output to a viewer node and turn on the backdrop. 5. Image will be shown. 6. Now place a blur node between the image node and the viewer node. 7. Set the x and y values of the blur node to 1 and the size to 1. 8. Image will blur. 9. Now change the blur mode to fast gaussian. 10. Image will go completely black. [test-image](https://projects.blender.org/attachments/e6bf2291-54f5-432f-9aaa-cec845001681)

michael campbell added the

labels 2023-09-03 15:54:58 +02:00

Iliya Katushenock added the

EEVEE & Viewport

labels 2023-09-03 16:06:23 +02:00

Pratik Borhade commented

2023-09-04 06:43:46 +02:00

Member

Hi, thanks for the report. Unable to redo this locally in today's buildbot build (4.0, 30de3d7c1a79)
Any chance you've add-on or an experimental feature activated?

Compositor output

Hi, thanks for the report. Unable to redo this locally in today's buildbot build (4.0, `30de3d7c1a79`) Any chance you've add-on or an experimental feature activated? [Compositor output](/attachments/64e15b40-dea6-4161-bdfa-03984513658c)

236 KiB

Pratik Borhade added

Needs Information from User

and removed

labels 2023-09-04 06:43:56 +02:00

michael campbell commented

2023-09-04 14:26:00 +02:00

Author

Hi, sorry you're right, I forgot I had enabled the experimental compositors in the preferences. I was using Tiled mode when the problem happened, but I may have been using GPU and Full Frame mode previously in the same session.

I also attached the wrong EXR file. Try this:

Open exr attached below
go to compositor
turn on experimental compositor in preferences but leave it as tiled in compositor
drag in the exr below
connect to viewer from the 0_Image socket.
place blur node set fast guasian in between and set it to 1 for x,y and size.
should work
now switch to gpu
should still work
now switch back to tiled or full frame
now produces black image
turn back off experimental compositor
remains black.

I'm not sure if it's caused by something going wrong with Cycles during rendering of the sequence, that has somehow corrupted the output, because there's also a strange black line on the image in both the ffmpg output and the file output node multilayer EXR output. I say this because re-rendering the same frames didn't reproduce the black lines, and also the blur node doesn't output black images with the newer frames.

Hi, sorry you're right, I forgot I had enabled the experimental compositors in the preferences. I was using Tiled mode when the problem happened, but I may have been using GPU and Full Frame mode previously in the same session. I also attached the wrong EXR file. Try this: 1. Open exr attached below 2. go to compositor 3. turn on experimental compositor in preferences but leave it as tiled in compositor 4. drag in the exr below 5. connect to viewer from the 0_Image socket. 6. place blur node set fast guasian in between and set it to 1 for x,y and size. 7. should work 8. now switch to gpu 9. should still work 10. now switch back to tiled or full frame 11. now produces black image 12. turn back off experimental compositor 13. remains black. I'm not sure if it's caused by something going wrong with Cycles during rendering of the sequence, that has somehow corrupted the output, because there's also a strange black line on the image in both the ffmpg output and the file output node multilayer EXR output. I say this because re-rendering the same frames didn't reproduce the black lines, and also the blur node doesn't output black images with the newer frames.

RL_d8eac157b29b0e94093edd7d5fc8201f_0019.exr

14 MiB

RL_d8eac157b29b0e94093edd7d5fc8201f_0019.exr

michael campbell commented

2023-09-04 14:27:08 +02:00

Author

If you repeat the above again but with this image, then the issue doesn't happen. Use 0_image on both this and the exr from the previous comment.

If you repeat the above again but with this image, then the issue doesn't happen. Use 0_image on both this and the exr from the previous comment.

RL_d8eac157b29b0e94093edd7d5fc8201f_0019.exr

10 MiB

RL_d8eac157b29b0e94093edd7d5fc8201f_0019.exr

michael campbell commented

2023-09-04 14:34:52 +02:00

Author

I've tried the same file (2 comments above) with experimental compositor feature disabled, and the issue still happens. So I think Cycles must have done something strange to the pixel data during the rendering of those frames.

I've tried the same file (2 comments above) with experimental compositor feature disabled, and the issue still happens. So I think Cycles must have done something strange to the pixel data during the rendering of those frames.

Pratik Borhade commented

2023-09-15 08:03:47 +02:00

Member

Yes, can confirm actually without experimental feature.

Yes, can confirm actually without experimental feature.

Pratik Borhade added

and removed

Needs Information from User

labels 2023-09-15 08:04:42 +02:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

2 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#111846

No description provided.