Blender: Deadline support

[simonebarbieri]

Changelog Description

Add Deadline support for Blender.

[ynbot]

Task linked: OP-6372 Blender submitting to Deadline

[LiborBatek]

I have prepared lighting scene with loaded pointcache animation, created renderLayerMain instance and hit Publish

I m getting following errors during Collect Render Layers phase:

Instance: 
sh004_renderlayerMain
Message: 
'bpy_prop_collection[key]: key "sh004_renderlayerMain" not found'
Line: 
76
Traceback: 
Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 527, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\blender\plugins\publish\collect_render.py", line 76, in process
KeyError: 'bpy_prop_collection[key]: key "sh004_renderlayerMain" not found'

Also I have experienced that user has to select camera when trying to create render instance if not anything selected I get following during creation error:

This differs from Maya host OP integration so not sure if it should be mandatory. I can imagine that there should be present validator for render camera during publishing process so it wouldnt be neccesary to pre select the camera when creating.

[LiborBatek]

There is small glitch with Validate Render Output for Deadline that max being shown even this being in blender host...need to be changed

[LiborBatek]

All working fine and without any glitches, producing desired renders and reviewables with burnins...

[LiborBatek]

So there actually some issues regarding using other file formats besides EXR...need to be addressed first

[LiborBatek]

fully support other file formats besides EXR, like PNGs, Tiff etc.

Now not fully working.

[LiborBatek]

So I have tested to set Blender and its OP Render Setttings to other format than Exr to PNG and created few AOVs as seen on pic

...in blender all good and properly setup when creating fresh new Render instance

Job is successfuly rendered on DL as seen here:

Problem being that DL Publish Job didnt correctly produced review mp4 just rendered frames in publish folder.

Also question being wether we should version each AOVs separately....

In my case, Im having these:

Main_beauty_v06
Main_Normal_v01
Main_Depth_v01
etc.

IMHO not very practical to have different version even the rendered frames originating from the same workfile lighting scene. Should be united under same version...

Lastly, we should also have option if Noisy Image being produced when rendering too....not very practical to have it everytime even when not having accompanying AOVs turned on for later possibility to perform denoise. Most of the cases not desired to produce just Noisy Image without those additional passes needed for post denoise.

This being only valid when turned on Denoising Data in Passes tab so it produces these then:

I vote for even not output Noisy Image at all if not set in OP Settings for Blender Render Settings.

Right now its not even possible to turn on these in OP:

Denoising Data producing Denoising Normal, Denoising Albedo, Denoising Depth

[LiborBatek]

Here is the Publish job on DL log:
Job_2023-09-21_08-37-12_650be498530d594b3d552485.txt

[BigRoy]

Didn't do a review - but just wanted to say it's a massive achievement this work has been implemented. Great job! 🥳

[LiborBatek]

@BigRoy I hope this one will serve for good! Let' s see how this one works in prod!