Tilt Posted February 18, 2014 Report Share Posted February 18, 2014 Hi, We would like to publish finished composites with the version number of the Nuke script that generated that render. But publishing it will always start at v1 and we'll lose the connection to the Nuke script version. Can we force the version number somehow? So we get a v5 if the artist never published versions 1 through 4, then a v10 if he decides to not release versions 6 through 9. We don't need to use or extend your Nuke plugin for this. If the API supports it, we could roll our own publish script for this. Thanks Stefan Link to comment Share on other sites More sharing options...
Björn Rydahl Posted February 18, 2014 Report Share Posted February 18, 2014 Hi Stefan, you can update he version number after a version has been published like this from the api:version.set('version', 10)Next version will then be given 11 as its number. If you try to set the version number to an existing one on the same asset it will raise an error. I can see two possible ways to do this, either roll your own publish script if you want more control. Or listen to events when a version is published and update it to match the version on the nuke script for example. Cheers Link to comment Share on other sites More sharing options...
Tilt Posted February 19, 2014 Author Report Share Posted February 19, 2014 cool! We're currently rolling our own publish tool for quick mass-publishing of renders. So that api call is the way to go I think. Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.