- Fri May 18, 2018 2:13 pm
I'll try to help you as much as I can with the problems with Denoiser + Network.
There are some things you have to take into account until we fix or remove these hurdles:
-Thiemo is right about naming the denoised image as %scenename%_denoised.png (for example) when launching an animation job; otherwise, one frame will overwrite the previous one.
-When you launch a single job, the denoised image is calculated by the node computer and what is more important, the resulting image is stored by it (instead of sending it to the manager to save it), so it should be able to understand the output path. In the case of Macs, this is sometimes hard to achieve.
-On the other hand, when you launch a cooperative job with denoiser, the nodes do not compute the denoised image; they just launch a normal render (with the required passes) and send the mxi files to the manager; this merges the different mxi files down to two and generates the denoised image from those; then it saves the denoised image in the specified path. So in this case, the output path has to be accessible from the manager computer.
-Additionally, there's a bug when using three nodes in a cooperative job with denoiser; one of the renders gets black and the denoised image gets blurred; this doesn't happen with two, four, or any other amount of nodes.
-The amount of memory is important, so if the GPU cannot host the whole scene, it is recommended to use the CPU to calculate the denoised image.
I hope this information helps.