Hello,
For renders from Nuke, we have configured the template path for the temporary rendering output. However, we are unsure how to set up a temporary rendering path template for renders coming from Photoshop and Silhouette.
Could you please guide us on how to configure this for those applications?
Thank you.
Are you looking for setting staging directory for render product in Photoshop and Silhouette hosts?
We’re looking to implement a temporary rendering path template, similar to the existing functionality in the Nuke Addon Creator plugins, for setting or creating render path templates. Additionally, we’re exploring how to apply a similar approach for Photoshop and Silhouette applications as well. Any guidance or suggestions would be greatly appreciated.
I think what you looks for is to:
define default output/render path
support staging directories (to override the default path per product type)
This PR can be an example
ynput:develop ← ynput:enhancement/130-ay-6965_rop-default-output-path-update-pyblish-to-something-less-legacy
opened 10:41PM - 18 Dec 24 UTC
## Changelog Description
This PR adds a main setting for configuring output dir… ectory for created ROP nodes via AYON creator plugins.
- [x] Add settings toggle to enable/disable path control completely (to allow a studio to completely manage it themselves)
- [x] If enabled,
- we use the default path as follows ```{staging_dir}/hardcoded_file_name.{ext}```
- intermediate render directories get a hardcoded folder name as follows```{staging_dir}/intermediate_file_type/hardcoded_file_name```
- [x] However, **if** matching custom staging dir profile is specified in `ayon-core` settings then we use that custom staging dir directory instead. (This also _only_ applies if "directory management" is enabled" as per the first point).
- [x] Expand Houdini vars when enabled, vars like `$HIP` will be expanded while not expanding any expressions.

resolve #130 and resolve #21
## Demo
- staging templates

- custom staging directories


1. follows `houdini_cache` template
2. follows `houdini_Render` template
3. follows the default value in Houdini settings as it doesn't match any profile.
## Testing notes:
1. Create new instances in Houdini, you should find the new output paths.
4. Publishing new and old instances should work without issues.