I go publish a bunch of openclips from graded sources, everyones starts working (in flame) rendering out new comp versions and updating the openclips as per usual - all is well.
Now client says they really hate the colorists stepuncles friends car and want to re-grade at Factory4 in Los Angeles.
So they do…
Now i get the new sources, i would love to be able to publish the shots as a new version so compers can update their clip node in batch and have the new v002 grading and bobs your uncle.
also whatbwiuld be nifty is to have both patternbrowsed versions and regular openclips combined - imagine having a something named nuke_version and a batch_version in case you are doing both flame and nuke work on the same shot (or maya or whatever). I know this works right now but i cant have all my nuke versions appear by patternbrowsing, its either or, right?
When you publish content with Open Clips, you get two Open Clips: one for the source and one for the sequence. You just need to add a version to the Clip Node and voila! You would need to do this either by updating your scene in Batch or programmatically.
You might not be aware of this BUT instead of defining an actual path to file in Open Clip, you can set a pattern. In this case, everytime you load the batch scene, the clip node will automagically update the scene to the latest version.
@finnjaeger you will have to do some R+D on this but yes you should be able to define both path and pattern IF you manually edit the published Open Clip since Publishing does not allow defining a pattern at publish time. NOTE that the last time I have look at this was many versions ago so not sure where we stand now and I sadly cannot validate that today since I am going away for 2 weeks. Have fun
For sure and @Slabrie answered @ALan’s question which kinda nullifies my excitement a tad. So now we just need a clever bit of python to edit the pub’d source clip’s open clips to allow for a version component in the file name… seems like someone should be able to parse the pub template and make the adjustments with a little bit of python know-how…
Many people have requested Pattern Browse based Publish for years and the answer has always been “It’s coming”. Now just the other day I said I’ll be retired before Teradici fixes their shit, and then this morning they notified me they fixed their shit. So I’m gonna double down and say I or @Slabrie be retired before we get a Pattern Browsed based Publish.