Doubled Animation Render Output using only File Output Nodes #57699

Open
opened 2018-11-08 14:50:10 +01:00 by G. Krause · 33 comments

System Information
Windows 7

Blender Version
Broken: 2.79. 5bd8ac9,
Worked: presumably never?

Short Explanation
When rendering an animation while using compositing output nodes, you get doubled output because of the "write_still=True", when the ".base_path" of the output nodes and "bpy.data.scenes["Scene"].render.filepath" differ.

Exact steps for others to reproduce the error
In a new scene, go into the node editor, tick on "use nodes" and switch to the "compositing nodes" view.
Replace the "Composite" node with a "File Output" node.
Change its base path to "[...]\folder1"

Go into the "properties" area, into the render tab.
Under "output", change the folder to "[...]\folder2"

Render an animation, you will get an output in both folders.

I would suggest turning off the properties panel output path when "use nodes" is True and output nodes are present?

**System Information** Windows 7 **Blender Version** Broken: 2.79. 5bd8ac9, Worked: presumably never? **Short Explanation** When rendering an animation while using compositing output nodes, you get doubled output because of the "write_still=True", when the ".base_path" of the output nodes and "bpy.data.scenes["Scene"].render.filepath" differ. **Exact steps for others to reproduce the error** In a new scene, go into the node editor, tick on "use nodes" and switch to the "compositing nodes" view. Replace the "Composite" node with a "File Output" node. Change its base path to "[...]\folder1" Go into the "properties" area, into the render tab. Under "output", change the folder to "[...]\folder2" Render an animation, you will get an output in both folders. I would suggest turning off the properties panel output path when "use nodes" is True and output nodes are present?
Author

Added subscriber: @morph3us

Added subscriber: @morph3us

#102447 was marked as duplicate of this issue

#102447 was marked as duplicate of this issue

#96767 was marked as duplicate of this issue

#96767 was marked as duplicate of this issue

#79645 was marked as duplicate of this issue

#79645 was marked as duplicate of this issue
Member

Added subscribers: @brecht, @lichtwerk

Added subscribers: @brecht, @lichtwerk
Member

Agree this is a little weak.
It is not a bug though, it is still working as intended.
Not having a Compositing output Node used to complain and refuse to render, but that rule was softened in the fix for #35269.

Maybe we can keep this as TODO? (would kindly ask @brecht for his opinion though).
If we do, then I dont think it is a good idea to not write to the output panel output path if File Output nodes are present though (these can be meant as extra outputs next to the regular render).
Instead I would suggest to only skip writing there if no Compositing output node is present...

I'll put this as a normal prio TODO (@brecht: please close this if this is not such a good idea...)

Agree this is a little weak. It is not a bug though, it is still working as intended. Not having a Compositing output Node used to complain and refuse to render, but that rule was softened in the fix for #35269. Maybe we can keep this as TODO? (would kindly ask @brecht for his opinion though). If we do, then I dont think it is a good idea to **not** write to the output panel output path if File Output nodes are present though (these can be meant as extra outputs next to the regular render). Instead I would suggest to only skip writing there if no Compositing output node is present... I'll put this as a normal prio TODO (@brecht: please close this if this is not such a good idea...)

Agree it could skip writing if the Composite node is removed (or has nothing linked), and that making it do that would be a To Do.

Agree it could skip writing if the Composite node is removed (or has nothing linked), and that making it do that would be a To Do.

Added subscriber: @KalyanS

Added subscriber: @KalyanS

Is this open to be worked on? If so, a few questions since I'm somewhat new to the code base:

  1. Should I disable the output panel output path, and how do I do this?
  2. Where is the code that writes image output?
  3. Where would I actually place the code that implements this issue?
Is this open to be worked on? If so, a few questions since I'm somewhat new to the code base: 1) Should I disable the output panel output path, and how do I do this? 2) Where is the code that writes image output? 3) Where would I actually place the code that implements this issue?

We haven't agreed on an exact UI design for this yet, it's not really ready to be picked up by someone.

We haven't agreed on an exact UI design for this yet, it's not really ready to be picked up by someone.

Added subscriber: @OtherRealms

Added subscriber: @OtherRealms

Hi, I'm the author of an add-on called Shot Manager (free and paid) which deals specifically with complex render path setups. However I've had a number of customers who have complained about the extra file outputs which results in unnecessary memory consumption and awkward file management. Just hoping this issues is a priority. Thanks.

Hi, I'm the author of an add-on called Shot Manager (free and paid) which deals specifically with complex render path setups. However I've had a number of customers who have complained about the extra file outputs which results in unnecessary memory consumption and awkward file management. Just hoping this issues is a priority. Thanks.
Member

Added subscriber: @dawidwizor

Added subscriber: @dawidwizor

Added subscriber: @Macilvoy

Added subscriber: @Macilvoy
Member

Added subscribers: @Benjamin-Round, @OmarEmaraDev

Added subscribers: @Benjamin-Round, @OmarEmaraDev
Philipp Oeser changed title from Doubled Animation Render Output using Output Nodes to Doubled Animation Render Output using only File Output Nodes 2022-03-25 10:02:51 +01:00

Added subscriber: @Asger

Added subscriber: @Asger

This would make it a lot easier to implement blender into a pipeline, and getting renders to compers working in other software like Nuke, fusion etc.

This would make it a lot easier to implement blender into a pipeline, and getting renders to compers working in other software like Nuke, fusion etc.

Added subscriber: @Jones-B

Added subscriber: @Jones-B

Hi, here is also a Right-Click Select Feature request to this Issue: https://blender.community/c/rightclickselect/5xgbbc/?sorting=hot#

Hi, here is also a Right-Click Select Feature request to this Issue: https://blender.community/c/rightclickselect/5xgbbc/?sorting=hot#
Member

Added subscriber: @L0Lock

Added subscriber: @L0Lock

Added subscriber: @VupliDerts-2

Added subscriber: @VupliDerts-2

Added subscriber: @ElijahG

Added subscriber: @ElijahG

This is indeed a very desired feature and I was surprised it hasn't been implemented yet.

The most sensible workaround if you're saving into multiple files is to use the normal output as one of them, but that doesn't work for OpenEXR Multilayer, and using that for normal renders (without File Output) with Cycles includes the Noisy Image pass, which is not always desirable and can make the files considerably larger.

This is indeed a very desired feature and I was surprised it hasn't been implemented yet. The most sensible workaround if you're saving into multiple files is to use the normal output as one of them, but that doesn't work for OpenEXR Multilayer, and using that for normal renders (without File Output) with Cycles includes the Noisy Image pass, which is not always desirable and can make the files considerably larger.
Member

I wonder if a solution to this could be to only rely on File Output nodes here (and basically ditch the concept of the Composite node)?

  • would need a bunch of rewrite (making sure some things are in sync with the Output tab Output panel if desired)
  • this way we never get duplicate/additional/unwanted outputs
  • would need to make sure everything gets properly written in File Output nodes (investigating #109956 as we speak)
I wonder if a solution to this could be to **only** rely on `File Output` nodes here (and basically ditch the concept of the `Composite` node)? - would need a bunch of rewrite (making sure some things are in sync with the `Output` tab `Output` panel if desired) - this way we never get duplicate/additional/unwanted outputs - would need to make sure everything gets properly written in `File Output` nodes (investigating #109956 as we speak)

That wouldn't work for the viewport compositor or when the compositor feeds into the sequencer.. The compositor is not the endpoint for file output, it's one step in a bigger pipeline.

That wouldn't work for the viewport compositor or when the compositor feeds into the sequencer.. The compositor is not the endpoint for file output, it's one step in a bigger pipeline.
Member

That wouldn't work for the viewport compositor or when the compositor feeds into the sequencer.. The compositor is not the endpoint for file output, it's one step in a bigger pipeline.

Ah, OK, lost the overall picture, thx for the input!

> That wouldn't work for the viewport compositor or when the compositor feeds into the sequencer.. The compositor is not the endpoint for file output, it's one step in a bigger pipeline. Ah, OK, lost the overall picture, thx for the input!

As far as I can tell there is no issue disabling compositor file output, this is unrelated to the pipeline. If the issue is UI, why not just make the main output save path optional? Keeping the settings for output node defaults.

As far as I can tell there is no issue disabling compositor file output, this is unrelated to the pipeline. If the issue is UI, why not just make the main output save path optional? Keeping the settings for output node defaults.

As far as I can tell there is no issue disabling compositor file output, this is unrelated to the pipeline.

It's not the compositor that outputs that file. It is the render pipeline that does.

If the issue is UI, why not just make the main output save path optional? Keeping the settings for output node defaults.

Yes such an option is possible. It's pretty confusing what happens then when not using the compositor, using the sequencer, doing a viewport render, doing rendered animation playback, opening a cached render in the image editor, etc. These issues could be worked through, or a more elegant solution could be found. It just hasn't been a priority so far.

> As far as I can tell there is no issue disabling compositor file output, this is unrelated to the pipeline. It's not the compositor that outputs that file. It is the render pipeline that does. > If the issue is UI, why not just make the main output save path optional? Keeping the settings for output node defaults. Yes such an option is possible. It's pretty confusing what happens then when not using the compositor, using the sequencer, doing a viewport render, doing rendered animation playback, opening a cached render in the image editor, etc. These issues could be worked through, or a more elegant solution could be found. It just hasn't been a priority so far.

As far as I can tell there is no issue disabling compositor file output, this is unrelated to the pipeline.

It's not the compositor that outputs that file. It is the render pipeline that does.

What I mean to say is the pipeline doesn't depend on file output

If the issue is UI, why not just make the main output save path optional? Keeping the settings for output node defaults.

Yes such an option is possible. It's pretty confusing what happens then when not using the compositor, using the sequencer, doing a viewport render, doing rendered animation playback, opening a cached render in the image editor, etc. These issues could be worked through, or a more elegant solution could be found. It just hasn't been a priority so far.

I think its not so different to saying for example, disabling all Render Layers or not having Render Layer nodes will result in a black image. Not elegant if someone is unfamiliar with software and changes random settings. I add a warnings in my render tools for this. Besides not being elegant, its importance as a function still takes priority. So if the compositor isn't enabled or doesn't have have output nodes, I wouldn't expect any files to output with this option also disabled. It could even be useful for benchmarking/pre-render tests.

Currently we have to export the smallest possible file format from main output and cleanup after every render, when we really want a custom Multi-layered EXR for example. If Blender is to prioritize the compact size of distributions, why not extend this philosophy to output disk space?

> > As far as I can tell there is no issue disabling compositor file output, this is unrelated to the pipeline. > > It's not the compositor that outputs that file. It is the render pipeline that does. What I mean to say is the pipeline doesn't depend on file output > > If the issue is UI, why not just make the main output save path optional? Keeping the settings for output node defaults. > > Yes such an option is possible. It's pretty confusing what happens then when not using the compositor, using the sequencer, doing a viewport render, doing rendered animation playback, opening a cached render in the image editor, etc. These issues could be worked through, or a more elegant solution could be found. It just hasn't been a priority so far. I think its not so different to saying for example, disabling all Render Layers or not having Render Layer nodes will result in a black image. Not elegant if someone is unfamiliar with software and changes random settings. I add a warnings in my render tools for this. Besides not being elegant, its importance as a function still takes priority. So if the compositor isn't enabled or doesn't have have output nodes, I wouldn't expect any files to output with this option also disabled. It could even be useful for benchmarking/pre-render tests. Currently we have to export the smallest possible file format from main output and cleanup after every render, when we really want a custom Multi-layered EXR for example. If Blender is to prioritize the compact size of distributions, why not extend this philosophy to output disk space?

Just for info:
Not only have to clean up the second part of output files after rendering, but the medium to store get's used twice (read/write).
This cut's down the lifetime for the storage medium if HDD or SSD. Not a problem for hobbyists but for studios and renderfarms, if I'm not wrong.

Just for info: Not only have to clean up the second part of output files after rendering, but the medium to store get's used twice (read/write). This cut's down the lifetime for the storage medium if HDD or SSD. Not a problem for hobbyists but for studios and renderfarms, if I'm not wrong.

Wouldn't be possible to have a checkbox in the File Output node to basically make it override the scene's output? Or have a "master" file output node that acts as such and can be present only once in the node tree?
And if enabled, grey out the scene's output panel with a red message explaining why.

Wouldn't be possible to have a checkbox in the File Output node to basically make it override the scene's output? Or have a "master" file output node that acts as such and can be present only once in the node tree? And if enabled, grey out the scene's output panel with a red message explaining why.
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2024-01-24 12:01:04 +01:00
Omar Emara added
Status
Confirmed
and removed
Status
Resolved
labels 2024-05-14 10:19:44 +02:00

Shouldn't this issue be re-opened in accordance with #117129 (comment)?

Shouldn't this issue be re-opened in accordance with https://projects.blender.org/blender/blender/pulls/117129#issuecomment-1188181?
Omar Emara removed the
Legacy
Blender 2.8 Project
label 2024-07-23 08:27:45 +02:00

Please consider this as an alternative solution to the problem:
https://blender.community/c/rightclickselect/KYpn/

Please consider this as an alternative solution to the problem: https://blender.community/c/rightclickselect/KYpn/
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
FBX
Interest
Freestyle
Interest
Geometry Nodes
Interest
glTF
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
17 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#57699
No description provided.