Compositor/Stereoscopy with view switch and file output generate extra files #72171

New Issue

ADI SAMSONOFF · 2019-12-04T17:01:01+01:00

ADI SAMSONOFF commented

2019-12-04 17:01:01 +01:00

Blender Version
Broken: 2.79, 2.81, ...
Worked: ?

Short description of error
when using Stereoscopy to render a scene from multiple cameras simultaneously, and using the compositor 'Switch View' node to save each camera output separately - unwanted files are saved with each output file.

Simpler version of the report

The combination of the switch view node, mix RGB node and rgb node is creating the problem, disabling even just one of those three nodes produces normal results.
The bug is reproduced only when all mix nodes are connected to the same RGB node, but connecting each node the a duplicate of the same rgb node seems to resolve the problem (see screenshots attached)

Sample file:

Compositor bug.blend

For the records the issue also happens in 2.79.

stereo279.blend

Original description of error

In the attached .blend are 9 cameras set up with sterescopy. The compositor separates and saves each camera output to a different directory.
For some reason, with every file output from a certain camera there's another file output from a different camera (lets call it parasite camera) , only this one is black with no data (see attached screenshot).
a few charasteristics:

The parasite camera output is added to every output of the other cameras, but not to its own
Rendering again changes the parasite camera to a different one (in the screenshot it was 'Cam006', in other renders it was a different one)
It's not clear how the parasite camera is "chosen", it isn't selected or active, and it's not the scene's camera
There's no file output in the compositor that suggests this output

TemplateScenePopulated_001.blend

**Blender Version** Broken: 2.79, 2.81, ... Worked: ? **Short description of error** when using Stereoscopy to render a scene from multiple cameras simultaneously, and using the compositor 'Switch View' node to save each camera output separately - unwanted files are saved with each output file. **Simpler version of the report** The combination of the switch view node, mix RGB node and rgb node is creating the problem, disabling even just one of those three nodes produces normal results. The bug is reproduced only when all mix nodes are connected to the same RGB node, but connecting each node the a duplicate of the same rgb node seems to resolve the problem (see screenshots attached) Sample file: [Compositor bug.blend](https://archive.blender.org/developer/F8281321/Compositor_bug.blend) ![noproblem.png](https://archive.blender.org/developer/F8281320/noproblem.png) ![problem.png](https://archive.blender.org/developer/F8281319/problem.png) For the records the issue also happens in 2.79. [stereo279.blend](https://archive.blender.org/developer/F8281380/stereo279.blend) **Original description of error** In the attached .blend are 9 cameras set up with sterescopy. The compositor separates and saves each camera output to a different directory. For some reason, with every file output from a certain camera there's another file output from a different camera (lets call it parasite camera) , only this one is black with no data (see attached screenshot). a few charasteristics: - The parasite camera output is added to every output of the other cameras, but not to its own - Rendering again changes the parasite camera to a different one (in the screenshot it was 'Cam006', in other renders it was a different one) - It's not clear how the parasite camera is "chosen", it isn't selected or active, and it's not the scene's camera - There's no file output in the compositor that suggests this output ![compositor bug.png](https://archive.blender.org/developer/F8189516/compositor_bug.png) [TemplateScenePopulated_001.blend](https://archive.blender.org/developer/F8189520/TemplateScenePopulated_001.blend)

ADI SAMSONOFF commented

2019-12-04 17:01:01 +01:00

Added subscriber: @Adi.samso

Serj Maiorov commented

2019-12-05 10:35:50 +01:00

Added subscriber: @SerjMaiorov

Jacques Lucke commented

2020-01-08 11:57:09 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-01-08 11:57:09 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Jacques Lucke commented

2020-01-08 11:57:09 +01:00

I can reproduce this issue. However, could you please provide a simpler file that has the same issue? Just two output nodes should be enough, right?

Dalai Felinto commented

2020-01-10 15:29:16 +01:00

Added subscriber: @dfelinto

Dalai Felinto commented

2020-01-10 15:29:16 +01:00

Changed status from 'Confirmed' to: 'Needs User Info'

Dalai Felinto commented

2020-01-10 15:29:16 +01:00

Not confirmed if we still don't have all the information to fix the issue (in this case we do need a simpler file).
Also, is this happening in 2.79 or not? The sample file can be made in 2.79 even.

Not confirmed if we still don't have all the information to fix the issue (in this case we do need a simpler file). Also, is this happening in 2.79 or not? The sample file can be made in 2.79 even.

ADI SAMSONOFF commented

2020-01-16 11:02:08 +01:00

alright, so I've been trying to reproduce the bug in a simpler file and may have discovered exactly what causes it and how to avoid it!
It seems like It's the combination of the switch view node, mix RGB node and rgb node is creating the problem, disabling even just one of those three nodes produces normal results.
The surprising fact is the bug is reproduced only when all mix nodes are connected to the same RGB node, but connecting each node the a duplicate of the same rgb node seems to resolve the problem (see screenshots attached)

(attached is a simpler file that reproduces the bug)

Compositor bug.blend

alright, so I've been trying to reproduce the bug in a simpler file and may have discovered exactly what causes it and how to avoid it! It seems like It's the combination of the switch view node, mix RGB node and rgb node is creating the problem, disabling even just one of those three nodes produces normal results. The surprising fact is the bug is reproduced only when all mix nodes are connected to the same RGB node, but connecting each node the a duplicate of the same rgb node seems to resolve the problem (see screenshots attached) (attached is a simpler file that reproduces the bug) [Compositor bug.blend](https://archive.blender.org/developer/F8281321/Compositor_bug.blend) ![noproblem.png](https://archive.blender.org/developer/F8281320/noproblem.png) ![problem.png](https://archive.blender.org/developer/F8281319/problem.png)

Philipp Oeser commented

2020-01-16 12:07:57 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-16 12:07:57 +01:00

Changed status from 'Needs User Info' to: 'Confirmed'

Philipp Oeser commented

2020-01-16 12:07:57 +01:00

Thx for digging deeper @Adi.samso , can confirm.

Dalai Felinto changed title from ~~Compositor/Stereoscopy bug~~ to Compositor/Stereoscopy with view switch and file output generate extra files

2020-01-16 12:22:14 +01:00

Dalai Felinto commented

2020-01-16 12:24:22 +01:00

Thanks indeed, it helps a lot this sort of simplification. I updated the report to contain all the updated information. Also making sure the proper module (VFX & Video in this case) is tagged.

Jeroen Bakker commented

2020-05-26 11:40:34 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2020-05-26 11:40:34 +02:00

when using the file I see it creates the next files

Saved: Output/Cam1/Image0001_Cam01.png
Saved: Output/Cam2/Image0001_Cam01.png
Saved: Output/Cam3/Image0001_Cam01.png
Saved: Output/Cam2/Image0001_Cam02.png
Saved: Output/Cam3/Image0001_Cam03.png

So it seems to be faulty when rendering the first view.
The file output node saves an image when its resolution is set to something else than [0,0]. In these cases it gets the resolution of the MixRGB -> RGB node.

Issue is also that the Switch View node isn't designed to split the graph, but for joining the graph. I will set this to known issue I don't see any solutions without breaking other setups.

A solution could be to have a view-filter in the file output node and not based on the dimension. but that is a workaround.

when using the file I see it creates the next files ``` Saved: Output/Cam1/Image0001_Cam01.png Saved: Output/Cam2/Image0001_Cam01.png Saved: Output/Cam3/Image0001_Cam01.png Saved: Output/Cam2/Image0001_Cam02.png Saved: Output/Cam3/Image0001_Cam03.png ``` So it seems to be faulty when rendering the first view. The file output node saves an image when its resolution is set to something else than [0,0]. In these cases it gets the resolution of the MixRGB -> RGB node. Issue is also that the Switch View node isn't designed to split the graph, but for joining the graph. I will set this to known issue I don't see any solutions without breaking other setups. A solution could be to have a view-filter in the file output node and not based on the dimension. but that is a workaround.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Compositor/Stereoscopy with view switch and file output generate extra files #72171