Here:
nuke_update_openclip.zip (2.9 KB)
No promises is going to work for you… works here.
I am using a modified variant of the createClip.py script from some years ago. Honestly I think it can be better, but dont have much time for this now. I’ll write something more robust eventually.
You need to use the included custom Nuke write node. I have set it up with some flexibility to adapt, but taking into account a folder structure similar to what Flame spits out from the Sequence Publisher.
The rendered image will default to this path
<render dir>/<version>/<shot>_<name>.<version>.<padding>.<extension>
The createClip.py will look in this folder by default:
<render dir>/<version>
The openclip path will default to:
<render dir>/<version>/<shot>.clip
Unless specified in the write node
One of the things the createClip will do is to keep adding version to the openclip, even if its the same version and path. This is one of the things it should be fixed eventually. So I have included an option to enable the update.
Hope at least it give you some ideas.
BTW the createClip.py it works as a standalone tool… just pass the --help flag for instructions.
A