To answer my own question, it seems the solution is to use the multi format export for jpeg and exr Write nodes, but to manually add my own CDL and burn-in setup when opening the freshly generated Nuke script rather than figure out how to procedurally build it in.
The burn-in timeline soft effect also does not seem to accept hard coded text so it's slightly limited. I found the burn-in gizmo for the export build came in with a font error on Linux (Ubuntu), so that didn't help. I noticed that custom nodes can be added, which is nice, but you can't for example add an OCIOCDL reader in the side branch for the jpeg render, it just gets thrown in the main pipe. I like the feature that allows existing comps to be associated with an imported comp render, so there is also the possibility to create a "dummy" first pass comp render to import to the timeline, then associate the existing comp with that, allowing whatever setup I want. Cheers, Michael On 13 April 2016 at 13:03, Michael Garrett <[email protected]> wrote: > Still fairly new with NS here. I would like NS to fit in with existing > conventions so I'm building an output template that mirrors the existing > (very basic) shot directory structure on the current show. > > What I am not clear on is how to migrate the functionality of the two > Write nodes in the comp: I have the typical setup of a Write node > outputting uncompressed full res exr's and another one outputting HD jpegs > with burn-in and baked CDL. > > Looking at the NS docs, it seems there are multiple approaches. One is to > just render exr's as the output of a comp container, then rebuild my > burn-in/CDL at the timeline level where I can then output the HD version > from the timeline. > > Another is to use multi-format exports, ie. procedurally build in two > Write nodes into the shot template. What I'm not immediately clear on, is > if I'm building this procedurally it seems there is no way to use my > existing burn-in set-up, and how do I assign the CDL? I am sure there is a > solution to this, but I have not figured it out yet. Ideally, there would > be a way of creating a hand-made template that has some customisation > beyond the procedural options. > > Thanks, > Michael >
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
