EXR files being duplicated upon publishing

Pipeline Integrations
1

Hello,

I have a pipeline that is working, but still needs a few tweaks. The biggest issue I am having right not is that when compositors publish a shot to ShotGrid the exr files are being copied into another directory which takes up twice as much memory on disk. The studio is used to working with the renders in a path like X:\LSDS\SOSPECHA_DE_SOFIA\01\LSDS_01_010_90-RENDER\LSDS_01_010_COMP_v001. The FlowProductionTrackingWrite node saves the render in this path, but when they publish the shot the exr files are duplicated into X:\lsds\sequences\01\LSDS_01_010\COMP\publish\elements\LSDS_01_010\v001.

Right now we have a “small” amount of shots so it is not a huge problem, but as we continue to use the pipeline then the problem will get exponentiolly bigger. I would like the renders to exist only in the “_90-RENDER” folder and for this to be referenced in the “Path to Frames”. Currently this field is referencing the exr files in X:\lsds\sequences\01\LSDS_01_010\COMP\publish\elements\LSDS_01_010\v001. Another issue I noticed is that editorial is loading the clips using the Loader feature, and the exr files referenced are the ones from X:\lsds\sequences\01\LSDS_01_010\COMP\publish\elements\LSDS_01_010\v001.

I need the exr files to exist only in one directory so save space on the disk, and not be duplicated during the publish. Also, for the loader to still work after any modifications done to the toolkit, and “Path to Frames” field to reference the correct directory. How can I accomplish this? I tried pointing the nuke_shot_render_stereo and nuke_shot_render_pub_stereo to the same template so they wont duplicate but then the publish process fails.

Please let me know if there is any documentation on this as I still have not found any, and thank you in advance for any help you can provide.

Best regards,
Sergio Pizzolante

2

Hi Sergio,

It sounds like the issue might be related to how the FlowProductionTrackingWrite node and the ShotGrid publishing process handle file paths. Here are a few suggestions you can try:

Adjust Template Configuration:
Since pointing both nuke_shot_render_stereo and nuke_shot_render_pub_stereo to the same template caused the publish to fail, ensure that the templates are correctly set up to differentiate between working and final published directories. If possible, use a single directory for renders and reference this consistently in the “Path to Frames.”

Override Publish Hook:
If you have access to the ShotGrid Toolkit configuration, consider overriding the publish hooks. You can customize the publish process to skip copying the EXR files and instead create a reference link to the existing “_90-RENDER” directory.

Modify Loader Configuration:
Update the Loader configuration to prioritize the “_90-RENDER” folder when fetching EXR files. This ensures that editorial loads the right files without duplicating them.

Explore Symbolic Links:
If your operating system supports symbolic links, you can create a link from the publish directory to the “_90-RENDER” folder. This way, you won’t consume extra disk space while maintaining compatibility.

If none of these work, it might help to check Autodesk’s official documentation or reach out to their support for more tailored guidance.

Best of luck with optimizing your pipeline!