-
Notifications
You must be signed in to change notification settings - Fork 129
Blender: output node and EXR #6086
Blender: output node and EXR #6086
Conversation
Task linked: OP-7120 Blender: output node and EXR |
Besides basic functionality I have tried to add some Error shown during Publish Create of the Render Instance>
|
Also because of fully automated approach speaking of output of AOVs, we need to incorporate the missing AOVs into Addon Settings too (manually created AOVs by user get swiped so the only way to create those are via predefined ones in settings) It probably depends which render engine being used (these below in Eevee only?) ...I would just ignore those if for ie Cycles renderer being chosen by user and not these AOVs available? And vice verse if Cycles AOV not present in Eevee...just ignoring it during Node tree creation for output. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even tho it successfully creates the desired outputs (also work when "Combined" added) it fails due to wrong output file path (if version mismatching as usual) but the Repair
action fails and its impossible to Publish
if not corrected by manually entering file path correct to DB. See attached scrngrab and check output file node and global output path on the right (the Repair does not fix the path and stays empty). Small note, my global file path was empty before too...but should work either imho
Small note: My assumption being that the Validator kicks in even tho the global file path shouldnt matter when using just But I could be wrong... |
The render job renders fine on DL then, but gives me errors during
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Speaking of function of this PR, it works when speaking about Blender itself but fails on Deadline Publish Job.
In Blender all working Fine and Validates ok. All AOVs being correctly premade in Compositor and File Output node sets correct output names and paths. It also produces all render sequences as supposed to into work render folder. So this part works fine, but the issue comes when publish job starting...
After some discussion with @antirotor it seems that the reason of failure being the JSON not being created correctly and that some render sequences being present there more than once thus causing issues when doing reviewables and burnins...
Im attaching the JSON for your inspection and also DL job publish log with the failure...
Its quite certain that this PR causing the DL issues so it needs resolution before merging this PR.
DL_PublishJob_LOG.txt
@simonebarbieri we'll nee ayon port for this too. |
@simonebarbieri is this ready for another round of testing? |
@tokejepsen I've got one last request from @LiborBatek and then it should be ready! Thanks :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changelog Description
Output node now works correctly for Multilayer EXR and keeps existing links. The output now is handled entirely by the compositor node tree.
Additional info
Output node in the compositing node tree wasn't working correctly for Multilayer EXR. Now existing links are recreated when creating an instance. Moreover, now the output is handled only by the compositor tree. Finally, when creating a render instance, a new version of the workfile is created, instead of overwriting the current one.
Testing notes: