When a denoiser is used, there are many unnecessary layers in the output raw exr file - Color.RGBA, albedo.RGB, bumpNormals.XYZ.
I need only EffectsResults.RGB. Is there any way to avoid saving others? I just dont have enough disk space for this…
Or maybe is there any way to save RGB_color to non-clamped .hdr file?
Yes, that’s a popular concern, however, those elements are necessary if you wish to do further denoising (through the vdenoise.exe tool) - better safe than sorry. There used to be a workaround for this - by using the vdenoise.exe, which used to output only the Denoised RGB, however, there’s still an issue active about it (internal bug-tracker id: VMAX-10760). Otherwise, from what you’re asking - saving the RGB through the VFB should be an option.
They aren’t junk layers, they’re saved so to enable post-render denoising (including multi-frame, temporal one).
There currently is no way to not save them with a thick Exr.
You can save split channels instead, denoise, and delete what you don’t need later, if you don’t have access to ways of extracting individual REs from the Exr.
EDIT: or as Aleks mentioned, you can surely just save the actual channel from the VFB.
Can you Denoise split layers with the standalone denoiser? I didn’t see how to do that. Will it work if you use separate folders per element?
I think saving split layers would be ideal. Then the denoised output would be just RGBA, rather than a second sequence of large, monolithic EXRs
The standalone Denoiser really needs to let you choose which elements to save in the out file. Perhaps this is simply something like “Export only denoised elements.” Then you wouldn’t have any duplicate data from the original exr sequence.
I’ll log the request for improvement.
No, i meant he’d save the splits to keep the rest of the REs, denoise the thick EXR (which will produce the denoised image), and delete the layers not needed from the split save, along with the thick Exr.
It’s all a LOT easier with something like nuke or fusion.
I do not need that. So for me their only function is to occupy disk space. Why am I being made happy by force?
Maybe it should be up to the user to decide whether to save these layers or not?
There are constraints to how a file save happens when rendering.
It’s impossible to raw-file save and not save *everything* in the image.
You have options if the image is displayed in the VFB (then you can save the layer you want, after it’s been denoised.), or through the split-file saver, with a post-delete action.
Otherwise, like others do, get Fusion or Nuke, and then you can remove what you don’t need from the thick exr saved through whatever means (load → extract the REs → recompose the EXR → save. highly scriptable.)
Great for those of us with scripting or programming acumen, but for the average user I can se how saving ONLY the RGBA after a denoise would be helpful. (Even if the standalone denoiser is far better and lets you experiment after the fact).
Yeah, pretty much.
I understand, and have been making use of, the extra data, but many people may just want to save what they were perfectly happy with in the VFB (the RGBA denoised to their satisfaction).
So, yes, throw the rest of it in the bin and save the RGBA. After, all you are proposing people do that after the fact. Why make the user do it manually (or through scripting that probably 90% of the userbase can’t do)?
For those of us that like scripting and getting everything JUST SO through scripting, etc. please see my thread here:
One word: agency.
Checkboxes, particularly if they are in render settings, are shown to be massive issues as people drag those settings along for years on end.
Alas, i just tried it, the split file save does what is being requested in the OP, the thread is exhausted. 
Lol. Maybe give the user agency by trusting the user to make the decision before rendering, rather than after.
Pedantic? Perhaps. But software is for the users.
That agency you speak of has shown time and again to be highly fallacious, by the sheer count of support requests involving such setups.
We never got *one* support request blaming us for user-initiated manual deletion of files from disk.
Ha! Well, I don’t have access to your support request data, but I can understand the OP’s desire not to waste disk space if they are happy with the denoised results they got.
I get that a company has to take into account the financial impact of their decisions. Increased support requests=increased costs.
But something tells me you get more requests about how to save ONLY the denoised result than not, given hermit crab saying it is a common request.
It’s kinda like how when the client says it needs to look like X. You make it look like X, even though it should really look like Y.
Of course, I’m with you and would rather have the flexibility.
what is wrong with split save?
Split save is great if you want to post denoise, or try various settings. If you are happy with the result in the VFB, as the OP seemed to be then it still wastes disk space until you delete the channels you don’t want.
I get it, lele. It’s better, more powerful, allows adjusting later, etc.
But if users just want the RGBA saved then why not let them? It’s pretty clear you are getting more support requests to save JUST the RGBA than you are from people asking how they can change their denoise settings after the fact. So just let users save ONLY the RGBA, and nothing else. Seems pretty simple, and obviously clear. Why are we even discussing this? 8)
I love your input, and I love your desire to tweak and enhance. I see myself in those goals. (Heck, I am the guy who says over and over NEVER *REMOVE* FEATURES.) But sometimes users just want simple and unencumbered.
No, the OP specifically mentioned raw file save (> output raw exr file): that is an impossibility.
I’d have zero issues if we added an option to the VFB, even just in the general options, out of the main UI, to not save denoiser-bound layers.
But that’s easy work done on a memory framebuffer, that the raw file save is not.
Semantics… really? The OP says, “I need only EffectsResults.RGB.”
We all know what they want and why (denoised RGBA *ONLY* … to save disk space).
It’s really quite simple. Why is it being made so complex? It’s an oversight that should be corrected.
I love you, lele, for all your insight, and for your trouble stirring. It’s good, and I think it benefits us all in the end.. But in this case it’s very simple-- give the man (person whatever) what he (she, it, they) wants.