Ability to comp frames that are being rendered on Deadline

General
1

Hi,

An artist in our studio have the following issue:

when he launches a V-Ray job on Deadline through AYON, the frames are being rendered in the shot / work folder like work/lighting/renders/maya/<shot>/<layer>/...

since the render might take a while, he is viewing the images in Nuke while the images are being rendered but then the Publish job will copy those images in the publish folder and deleting the ones in the work folder, therefore breaking the Nuke connection.

I understand that it’s not possible to Load the render with AYON as it’s being rendered since it’s not published but how could it be better?

2

This has come up before - and usually the final recommendation is to disable the “automatic deletion” of the intermediate work renders on publish.

However, I keep forgetting myself how your turn these off.
I believe it should be: ayon+settings://core/publish/CleanUp/remove_temp_renders

Just wanting to link these references:

  • Somewhat related about the moving of the renders on publish: Discord
  • @antirotor mentioning it deletes all renders on farm due to some lines in the codebase, here: Discord
1 Like
3

I wonder if we can solve it the other way by having some settings in the read node to read from the temp/staging location and switch to the publish location once its finished.

4

The “temporary directory” being rendered to can be heavily customized (and is not necessarily always managed by AYON itself completely). So even if we do, it’s not guaranteed to work. Plus technically, AYON itself does not yet know about those “unpublished versions” either so it wouldn’t really know which folders/files may be there.

One may crawl the work renders folder “hoping” to get the right path, but nothing ensures it’ll actually work as needed + it’d quite specific to that particular path setup.

The better approach may be publishing frames directly as they finish, as came up here: Discord and has been in the backlog before. I recall discussing it with @milan in the past.

1 Like
5

there was a discussion in OpenPype days about version status (that is now a thing) but at that point it had slightly different meaning:

the idea was to publish the version immediately when the job is created on the farm with the status “in progress”. This will expose it to the loaders and the loader can implement it’s own logic to deal with the fact that the files might not be there yet. There are renderers that support file formats that are being rendered in that you can load in nuke and start comping while the renderer is still working.

I guess that with the repreentation traits, we would be able to mark that representation for the loader correctly.

2 Likes
6

Thank you for your answer and the links.

I noticed that the setting ayon+settings://core?project=<my_project> was disabled for my project (and globally), is it really doing something?

@antirotor having a “in progress” status for a publish could solve those issues! Having the ability to use a loader in Nuke to load frames that are being rendered.