Blender adds frame number suffix to image files not rendered during animation. #123944

New Issue

Ludvik Koutny · 2024-06-29T13:47:22+02:00

Ludvik Koutny commented

2024-06-29 13:47:22 +02:00

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 552.22

Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270
Worked: (newest version of Blender that worked as expected)

Short description of error
According to official docs:
https://docs.blender.org/manual/en/latest/render/output/properties/output.html

When rendering an animation, the frame number is appended at the end of the file name with four padded zeros (e.g. image0001.png). You can set a custom padding size by adding the appropriate number of # anywhere in the file name (e.g. image_##_test.png translates to image_01_test.png).

It clearly implies the frame number should only be appended during animation.

Exact steps for others to reproduce the error

Open any existing Blender scene that has a camera so it can render image.
Enable compositing nodes, and add File Output node
Plug any render layer into the Image input of the File Output node
In the File Output node properties, specify base path
In main window menu bar, go to Render->Render Image

Result: The rendered image has frame number appended despite not rendering animation. This is not desirable and will also cause rendering of the still image to override animation frame file if exists in the target location.
Expected: Images rendered using Render Image operation will not have frame numbers appended.

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 552.22 **Blender Version** Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270` Worked: (newest version of Blender that worked as expected) **Short description of error** According to official docs: https://docs.blender.org/manual/en/latest/render/output/properties/output.html > When rendering an animation, the frame number is appended at the end of the file name with four padded zeros (e.g. image0001.png). You can set a custom padding size by adding the appropriate number of # anywhere in the file name (e.g. image_##_test.png translates to image_01_test.png). It clearly implies the frame number should only be appended during animation. **Exact steps for others to reproduce the error** 1. Open any existing Blender scene that has a camera so it can render image. 2. Enable compositing nodes, and add File Output node 3. Plug any render layer into the Image input of the File Output node 4. In the File Output node properties, specify base path 5. In main window menu bar, go to Render->Render Image Result: The rendered image has frame number appended despite not rendering animation. This is not desirable and will also cause rendering of the still image to override animation frame file if exists in the target location. Expected: Images rendered using Render Image operation will not have frame numbers appended.

Ludvik Koutny added the

labels 2024-06-29 13:47:23 +02:00

Cedric Steiert commented

2024-06-29 16:21:43 +02:00

Not a bug, it's expected behaviour of the File Output Node

This node writes out an image, for each frame range specified, to the filename entered, as part of a frameset sequence. [...] Unlike the render output filepath, this node uses a base directory and an image name, by default the output path is composed of: {base path}/{file name}{frame number}.{extension}.

As for your other part:

This is not desirable and will also cause rendering of the still image to override animation frame file if exists in the target location.

Unfortunetaly it seems there is no Overwrite checkbox. So that's how it is...

Not a bug, it's expected behaviour of the [File Output Node](https://docs.blender.org/manual/en/latest/compositing/types/output/file.html) > This node writes out an image, for each frame range specified, to the filename entered, as part of a frameset sequence. [...] Unlike the render output filepath, this node uses a base directory and an image name, by default the output path is composed of: {base path}/{file name}{frame number}.{extension}. As for your other part: > This is not desirable and will also cause rendering of the still image to override animation frame file if exists in the target location. Unfortunetaly it seems there is no `Overwrite` checkbox. So that's how it is...

Ludvik Koutny commented

2024-06-29 16:40:57 +02:00

Not a bug, it's expected behaviour of the File Output Node

This node writes out an image, for each frame range specified, to the filename entered, as part of a frameset sequence. [...] Unlike the render output filepath, this node uses a base directory and an image name, by default the output path is composed of: {base path}/{file name}{frame number}.{extension}.

As for your other part:

This is not desirable and will also cause rendering of the still image to override animation frame file if exists in the target location.

Unfortunetaly it seems there is no Overwrite checkbox. So that's how it is...

But it makes no sense:

Why would it not be consistent with scene output?
What's the purpose if having frame number when not rendering an animation.
Why would you want to override a frame of rendered animation when you press "Render Image" button and are using file output node. Imagine you've spent all night rendering some animation, just to destroy some frames by forgetting to disable file output node and rendering single image for preview?

> Not a bug, it's expected behaviour of the [File Output Node](https://docs.blender.org/manual/en/latest/compositing/types/output/file.html) > > This node writes out an image, for each frame range specified, to the filename entered, as part of a frameset sequence. [...] Unlike the render output filepath, this node uses a base directory and an image name, by default the output path is composed of: {base path}/{file name}{frame number}.{extension}. > > As for your other part: > > This is not desirable and will also cause rendering of the still image to override animation frame file if exists in the target location. > > Unfortunetaly it seems there is no `Overwrite` checkbox. So that's how it is... But it makes no sense: 1. Why would it not be consistent with scene output? 2. What's the purpose if having frame number when not rendering an animation. 3. Why would you want to override a frame of rendered animation when you press "Render Image" button and are using file output node. Imagine you've spent all night rendering some animation, just to destroy some frames by forgetting to disable file output node and rendering single image for preview?

YimingWu commented

2024-07-01 04:22:14 +02:00

I think this is the case where the manual needs to be updated to clarify the reason and behaviour.

Ludvik Koutny commented

2024-07-01 09:15:44 +02:00

I think this is the case where the manual needs to be updated to clarify the reason and behaviour.

Is there a reason though? I can't think of any. The non-optional suffix for single image, non animation renders is both unsafe, destructive and adds unnecessary work. It will require some pro level mental gymnastics to justify this as a feature.

> I think this is the case where the manual needs to be updated to clarify the reason and behaviour. Is there a reason though? I can't think of any. The non-optional suffix for single image, non animation renders is both unsafe, destructive and adds unnecessary work. It will require some pro level mental gymnastics to justify this as a feature.

YimingWu added

Module

Render & Cycles

Status

Needs Info from Developers

and removed

Status

Needs Triage

labels 2024-07-01 11:08:42 +02:00

Ludvik Koutny commented

2024-07-02 08:13:04 +02:00

It makes it especially painful to use Blender's compositing nodes as either:
A: Static image editor (for texture mixing, channel packing and so on)
B: Saver of AOVs, for example for PBR texture sets rendered from orthographic camera
When the file output node destroys the desired filenames by appending frame numbers, every single iteration between Blender and external software requires painful chore of manually renaming the files to remove the number suffix. I can't begin to describe how bad of an idea appending frame numbers to static images is.

It makes it especially painful to use Blender's compositing nodes as either: A: Static image editor (for texture mixing, channel packing and so on) B: Saver of AOVs, for example for PBR texture sets rendered from orthographic camera When the file output node destroys the desired filenames by appending frame numbers, every single iteration between Blender and external software requires painful chore of manually renaming the files to remove the number suffix. I can't begin to describe how bad of an idea appending frame numbers to static images is.

👀 1

Bart van der Braak added

and removed

labels 2024-08-14 12:58:12 +02:00

Sign in to join this conversation.