File Output nodes output gets overwritten by "standard" output (if the same filename is used) #109794

New Issue

Adam · 2023-07-06T19:16:55+02:00

Adam commented

2023-07-06 19:16:55 +02:00

I have a scene with simple animation.
I'm rendering muilti-layer open exr with an composite output node with the passes as in them.
The standard file 5 year old output bug is still here, where your file saves twice, once from the main file output tab and again on your composite output, normally I don't care whatever, it will just overwrite and I'll end up with one file.

After setting up my render output with all the layers I want, normally I just let the overwrite button on regular output be set and it's fine. However all my passes in the exr file were changed to VeiwLayer.(pass), and I'm missing passes like image and alpha or others I might composite into the composite output node.

My work around is to make the file name something different than my composite output vs the normal file output name.
But now I'm saving twice and having to deal with deleting 100s of gigs of junk EXR files from the main file output tab.

If you render one frame from the file I uploaded, then drop it into a compositor like nuke, fusion or cough cough AE, you'll see the passes are different.
P.S. You can kill the textures, sorry I didn't pack them for size sake

Thank you

blender 3.6
File SYS - (although it seems to be the case on multiple machines, so I thinks it's just an overlook bug):
ryzen 9 5950x
128 gigs ddr4
rtx 4090

And
M1max 64 gig integrated

I have a scene with simple animation. I'm rendering muilti-layer open exr with an composite output node with the passes as in them. The standard file 5 year old output bug is still here, where your file saves twice, once from the main file output tab and again on your composite output, normally I don't care whatever, it will just overwrite and I'll end up with one file. After setting up my render output with all the layers I want, normally I just let the overwrite button on regular output be set and it's fine. However all my passes in the exr file were changed to VeiwLayer.(pass), and I'm missing passes like image and alpha or others I might composite into the composite output node. My work around is to make the file name something different than my composite output vs the normal file output name. But now I'm saving twice and having to deal with deleting 100s of gigs of junk EXR files from the main file output tab. If you render one frame from the file I uploaded, then drop it into a compositor like nuke, fusion or cough cough AE, you'll see the passes are different. P.S. You can kill the textures, sorry I didn't pack them for size sake Thank you blender 3.6 File SYS - (although it seems to be the case on multiple machines, so I thinks it's just an overlook bug): ryzen 9 5950x 128 gigs ddr4 rtx 4090 And M1max 64 gig integrated

terarra-2.blend

18 MiB

Adam added the

labels 2023-07-06 19:16:55 +02:00

Pratik Borhade commented

2023-07-07 08:39:10 +02:00

Hi, thanks for the report. Maybe I misunderstood but this report is about overwritten results of existing render or about missing render passes?

Evan Wilson commented

2023-07-07 11:51:56 +02:00

I have uploaded a pair of EXRs from rendering your file. I am not clear as to what the issue is that you are trying to report. Can you clarify it please?

Standard_output0002.exr

423 KiB

Output_comp0002.exr

188 KiB

Evan Wilson added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-07-07 11:52:29 +02:00

Adam commented

2023-07-07 14:32:54 +02:00

If you extract the passes from each of the those files, you'll see that the standard output ignores the passes from the compositor.
There's no image, alpha, or denoised normal node composites, no alpha for shadow catcher, ect.. from the compositor. It only gives you the selected passes and ignores everything you make in the compositor. The other one will give you the passes from the compositor that most people in industry pipeline needs, like an alpha for the shadow catcher, the standard pass output needs to be tweaked for production.

So if you don't save them twice the standard output will overwrite your composite node and you'll loose the passes you need.

This is a serious issue for those that need multilayer exr workflow.

Here's an image you can see the standard just gave raw passes and bunch of not useful ones, and the comp version gave my clean composite rgba passes even for shadow catcher.

If you extract the passes from each of the those files, you'll see that the standard output ignores the passes from the compositor. There's no image, alpha, or denoised normal node composites, no alpha for shadow catcher, ect.. from the compositor. It only gives you the selected passes and ignores everything you make in the compositor. The other one will give you the passes from the compositor that most people in industry pipeline needs, like an alpha for the shadow catcher, the standard pass output needs to be tweaked for production. So if you don't save them twice the standard output will overwrite your composite node and you'll loose the passes you need. This is a serious issue for those that need multilayer exr workflow. Here's an image you can see the standard just gave raw passes and bunch of not useful ones, and the comp version gave my clean composite rgba passes even for shadow catcher.

passes.png

55 KiB

Adam commented

2023-07-11 00:11:11 +02:00

I've found a work around.

If you set the standard output to a different type of file, like png, and check off overwrite.
The system won't overwrite nor save the other file.

Would a simple UI fix for this be a checkbox in the standard output that says use composite output that would make a null file output and grey out the area?

I've found a work around. If you set the standard output to a different type of file, like png, and check off overwrite. The system won't overwrite nor save the other file. Would a simple UI fix for this be a checkbox in the standard output that says use composite output that would make a null file output and grey out the area?

YimingWu referenced this issue

2023-07-11 10:44:22 +02:00

Compositor, Using File Output Node and writing EXR multilayer file format is not writing ViewLayer Information. #109956

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-07-18 07:25:41 +02:00

Philipp Oeser commented

2023-07-18 15:05:46 +02:00

Isnt this just requesting to not write to the "standard" (Output Properties > Output) output if the Composite node is not connected (or if there is just no Composite node whatsoever) -- this should eliminate the root problem here, right?

This would be the same as #57699 though.

Or are you saying that having the same file specified in the Output Properties > Output panel and the File Output node was working at some point (in the way that File Output would overwrite Output Properties > Output) and is now working in a different way (Output Properties > Output overwrites File Output)?

And just to be clear: #57699 should really be tackled, this comes up all the time again.

Isnt this just requesting to `not` write to the "standard" (`Output Properties` > `Output`) output if the `Composite` node is not connected (or if there is just no `Composite` node whatsoever) -- this should eliminate the root problem here, right? This would be the same as #57699 though. Or are you saying that having the same file specified in the `Output Properties` > `Output` panel and the `File Output` node was working at some point (in the way that `File Output` would overwrite `Output Properties` > `Output`) and is now working in a different way (`Output Properties` > `Output` overwrites `File Output`)? And just to be clear: #57699 should really be tackled, this comes up all the time again.

Philipp Oeser added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-07-18 15:05:55 +02:00

Adam commented

2023-07-18 16:27:45 +02:00

I'm not entirely sure what your asking?
I believe it was the second thing you wrote, when doing test and setting up the file I usually just start with the standard file output which will give basic passes in the multilayer. Then I'll make a composite node to dial in the passes with an output node. If I don't change the file output on the standard to something else then I loose all my passes from the composite node. On a side note, is the overwrite on the standard tab also mean not just old files but overwrite the composite node output as well? That doesn't sound right but maybe that's how it was made now, but I don't remember ever having this issue before.

I'm not entirely sure what your asking? I believe it was the second thing you wrote, when doing test and setting up the file I usually just start with the standard file output which will give basic passes in the multilayer. Then I'll make a composite node to dial in the passes with an output node. If I don't change the file output on the standard to something else then I loose all my passes from the composite node. On a side note, is the overwrite on the standard tab also mean not just old files but overwrite the composite node output as well? That doesn't sound right but maybe that's how it was made now, but I don't remember ever having this issue before.

Philipp Oeser commented

2023-07-19 09:59:30 +02:00

Thx getting back.

Let me try to understand again:

if you "start" and use the "standard" file output (Output Properties > Output) -- all is fine
then you refine your passes and output them with File Output node(s)
-- this is also fine when the File Output node uses a different filepath (but then you get the additional output from Output Properties > Output which you dont really need and that just wastes disk space and time)
-- this is not fine when the File Output node uses the same filepath (it just gets overwritten by the "standard" Output Properties > Output which might be totally different than what you want from the File Output node)

So my question was, if everything would be solved for you if Blender worked like this:

if you disconnect everything from the Composite node (or just delete it), then you only get the output from File Output node(s)
-- then you dont get additional output from Output Properties > Output (if a different filepath is used there, no disk space wasted etc)
-- then the output of the File Output nodes would never be overwritten (if the same filepath is used)

On a side note, is the overwrite on the standard tab also mean not just old files but overwrite the composite node output as well?

You mean "does the Overwrite option also apply for File Output nodes?" Will check on this

Thx getting back. Let me try to understand again: - if you "start" and use the "standard" file output (`Output Properties` > `Output`) -- all is fine - then you refine your passes and output them with `File Output` node(s) -- this is also fine when the `File Output` node uses a different filepath (but then you get the additional output from `Output Properties` > `Output` which you dont really need and that just wastes disk space and time) -- this is not fine when the `File Output` node uses the same filepath (it just gets overwritten by the "standard" `Output Properties` > `Output` which might be totally different than what you want from the `File Output` node) So my question was, if everything would be solved for you if Blender worked like this: - if you disconnect everything from the `Composite` node (or just delete it), then you only get the output from `File Output` node(s) -- then you dont get additional output from `Output Properties` > `Output` (if a different filepath is used there, no disk space wasted etc) -- then the output of the `File Output` nodes would never be overwritten (if the same filepath is used) >On a side note, is the overwrite on the standard tab also mean not just old files but overwrite the composite node output as well? You mean "does the `Overwrite` option also apply for `File Output` nodes?" Will check on this

Philipp Oeser changed title from ~~Exr Output conflicts 3.6~~ to File Output nodes output gets overwritten by "standard" output (if the same filename is used)

2023-07-19 10:21:57 +02:00

Philipp Oeser referenced this issue

2023-07-19 10:42:11 +02:00

Compositor, Using File Output Node and writing EXR multilayer file format is not writing ViewLayer Information. #109956

Pratik Borhade commented

2023-08-31 08:48:29 +02:00

@AdamTemple hi, any updates?

You mean "does the Overwrite option also apply for File Output nodes?" Will check on this

I guess some options are shared between "file output" node and standard render output (example: #109601)

@AdamTemple hi, any updates? > You mean "does the Overwrite option also apply for File Output nodes?" Will check on this I guess some options are shared between "file output" node and standard render output (example: #109601)

Pratik Borhade commented

2023-12-29 07:53:22 +01:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

Pratik Borhade closed this issue

2023-12-29 07:53:25 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-12-29 07:53:27 +01:00

Sign in to join this conversation.