Although it's listed as a node in the scene when batch rendering the scene the oidn imager is not doing anything. The images are the same as the ones without the imager. Running the same scene under Windows in Arnold Render View works very well.
I've checked the CPU capabilites of the Linux blades using the oidnTest and they passed all tests.
Solved! Go to Solution.
Solved by Stephen.Blair. Go to Solution.
Does batch render on Windows work?
No. Tested in on my Windows 10 machine with MtoA 5.0.0.1
Although the node is listed when the scene is parsed it's not used. The output is the noisy one. Setting an output suffix in the imager node results in a black layer in the final exr.
I got it to work after I remembered a solution I created a while ago when various imagers created black AOVs.
The workaround is to create a custom AOV with an LPE that contains the beauty (C.*) and use this custom AOV as an input for the imager. This works in batch under Windows and Linux.
I couldn't reproduce the problem, at least not with a default oidn imager that worked on the RGBA.
I've created 2 simple scenes. The working one is using my LPE workaround the other one has the imager attached as it comes out of the box which should be cleaning the RGBA AOV. But it isn't.
If I turn off Output Denoising AOVs, then I get OIDN to work.
Output Denoising AOVs is for the Arnold Denoiser aka noice