Maniphest T93561

Single image is not autosaved, while image sequence can be autosaved. They should be unified!!
Closed, Archived
Actions

Assigned To
None
Authored By
Marco Hoo (MarcoHoo)
Dec 2 2021, 4:08 AM
Tags
  • BF Blender
Subscribers
Marco Hoo (MarcoHoo)
Philipp Oeser (lichtwerk)

Description

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-11-29 23:15, hash: rBac447ba1a3f2
Worked: (newest version of Blender that worked as expected)

Short description of error
I regard this as a bug.


Here is the situation: I try to render a 75 frames animation. Before I render final video, I render a single image as test to compositing. So in this same compositing nodetree,
here is the question: when I use file output node to save some passes, should I connet the "render layers' image" socket or not?
If not connect, when I render single image, I miss the combined image, other passes left.
If connect, when I render image sequence, OMG, I get massive repeated image.
This makes me confused and uncomfortable. They should be unified. The single image should be autosaved as well.

A more common case is that: even though I render single image without other passes, when I set up the output location happily, I get nothing finally. I feel bad. If you don't save the image, why you ask me to setup the location? Can't blender save single image automatically like image sequence and video clip? Please, please autosave the single image.

Another better solution I think is that mix composite node and file output node into ONE node. Don't seperate them. In this case, images connectted to this new one node can be saved automatically.

Look forward to your reply!

Sincerely.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

Related Objects

Event Timeline

Marco Hoo (MarcoHoo) created this task.Dec 2 2021, 4:08 AM
Marco Hoo (MarcoHoo) updated the task description.Dec 2 2021, 4:26 AM
Philipp Oeser (lichtwerk) closed this task as Archived.Feb 3 2022, 12:07 PM
Philipp Oeser (lichtwerk) added a subscriber: Philipp Oeser (lichtwerk).

Here is the situation: I try to render a 75 frames animation. Before I render final video, I render a single image as test to compositing. So in this same compositing nodetree,
here is the question: when I use file output node to save some passes, should I connet the "render layers' image" socket or not?
If not connect, when I render single image, I miss the combined image, other passes left.
If connect, when I render image sequence, OMG, I get massive repeated image.
This makes me confused and uncomfortable. They should be unified. The single image should be autosaved as well.
A more common case is that: even though I render single image without other passes, when I set up the output location happily, I get nothing finally. I feel bad. If you don't save the image, why you ask me to setup the location? Can't blender save single image automatically like image sequence and video clip? Please, please autosave the single image.

Rendering a single image does not automatically save it. The File Output node will though.
This is the current design, it has caused confusion before, yes, but this has not resulted in a decision to change the behavior.
This is all documented, the tooltip for the Output path will also tell you this is for animations.

https://docs.blender.org/manual/en/dev/render/output/animation.html#rendering-animations
https://docs.blender.org/manual/en/dev/compositing/types/output/file.html
https://docs.blender.org/manual/en/dev/render/output/properties/output.html

Another better solution I think is that mix composite node and file output node into ONE node. Don't seperate them. In this case, images connectted to this new one node can be saved automatically.

That might be a nice idea, but this is also not a bug, but a request for improved behavior

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

has also been reported before (e.g. see T71215: 2.81 Output image not working)