Nuke - Farm Reviews with Distributed Extract Review Data Mov

Hey everyone,

We’re finishing up ia plug-in that does practically the same as extract oiio transcode but with the added ability of reading the full effect chain from hiero/nukestudio and render it out.

We started it on 3.14 so we didn’t notice there was already a plug-in that could extract oiio stuff inside the new 3.15 codebase, ooops!

Basically it reads the effectPlateMain, splits repo and color operations, does matrix calculations on the fly for transform node concats, create a temp ocio config based on the studio wide one with a look named after the context (shot) and renders out a new sequence with all this baked in in whatever final resolution needed.
We also added the ability to add burnins on top using oiio just to try that out, but that would be probably be better left to the current ffmpeg based one. Still the classes are there.

Right now it’s implemented as a pure python package with no integration in op. Reason for that is that we would like to actually create a new family which is not “effect” but something akin to “reviewSetup” to store the transform data, the custom per shot config.ocio, and in the future being able to export that from resolve (nukestudio is way too much pricey).
The aim was to have published overrides of ocio configs directly available on dcc viewports and have them versioned for traceability.

ExtractReview is very extensive and stable, but it feels to me that using ffmpeg to do imaging is not the way forward, and your efforts on the extract oiio transcode validate this thought, especially since that can be sent to farm pretty safely while ffmpeg not so much (yes you could chunk it but then you need to use exrs and color control flies out the window).

If it’s of anyone interest I could probably upload all that stuff on a repo and share with you guys, the op integration is gonna take some time from me to finish since I’m really low on time these days. Maybe you could get a head start? Especially the repo stuff, which was a bit of a hassle to do since I coded it in pure python to avoid numpy imports.
The reposition itself works flawlessly in both oiio using the warp filter and ffmpeg using the perspective filter.

Let me know your thoughts.