Hello,
I have been dealing with a similar problem in my studio. Many times we need to deliver to our clients using ProRes4444 (or any other format they request really, usually multiple at once) and generating these reviews can be quite a pain if we do it on every publish. Because of this, I have been working on allowing to run the OpenPype extract + review plugins on-demand in the farm.
First, the way we are generating these reviews isn’t like @jiri.sin is. We aren’t using the ExtractReviewDataMov Nuke plugin, we are using a combination of Extract OIIO Transcode and Extract Review. With the former, we generate the different transcoded sequences with oiiotool that we later use for creating the reviews with ffmpeg.
Here’s a screenshot of a part of the settings on Extract Oiio Transcode:
Then on Extract Review, we have an h264 representation that we use to upload to Shotgrid:
But also we have other output definitions for prores422 and prores4444 and so on:
You will notice how I make use of custom tags in order to choose which transcoded sequence to use for what.
With this setup, I am able to generate the client review data automatically for every publish of the artists… however, that’s not ideal as it’s quite a lot of overhead and as you pointed out on this other thread Nuke - Publish on Farm with Existing Frames, not being able to submit “Use existing frames” to the farm makes this process quite painful.
As a quick fix to allow artists to publish without the overhead of transcoding + generating the big reviews on every publish I added an extra checkbox in the publisher so they can manually choose whether they just want a review for Shotgrid or they also want it to generate the ProRes reviews:
This offsets a bit the pain for now but as I said at the beginning of this, we would rather have a different way to trigger the review generations on-demand. The review generations + delivery is usually handled by another department (editorial) and not something our compositors or other artists should care about.
As for the publish (transcode + extract plugins) on-demand in the farm I have been thinking on doing it through one of these frameworks (which I could later automate or wrap on a CLI once the framework is in place):
- Add support to submit publishes to the farm from Traypublisher. That way I could for example use the
renderfamily to pick the files from an existing publish as representations + reviewable representations and delegate the rest of the publish workflow to the farm - Use the
Source (read)publish type and also add support to publish in the farm with the proper plugins enabled - Manually create the json file required to run a
headlesspublish of a given source and submit to the farm (this is what the other two would already kind of be doing without me needing to reverse engineer how to set this up)
Anyway, hopefully someone from the Ynput team can shed some light to this