Wow that is a big comp. If you insert Write nodes after the rotos, you
can render it out and then set it to read the files just written using
the 'read' check box. It then becomes a Read/Write and none of the
nodes above it should be evaluated while the 'read' box is checked.
Lars
On 22/05/2012 9:44 p.m., Marc Gutowski wrote:
Hey Phong,
'doin' good, indeed! Smile
okay the rotos are big in textsize, but nuke seems to "evaluate" or cache
every roto/rotopaint on script load. doing this on render time would
save a lot of
time and ram when loading heavy scenes files - but this is only a guess.
i can imagine, writing a routine to automatically render rotos to
files and get
them imported and linked as mask again. this routine would not that
difficult to write,
but keeping the masks editable and up-to-date within work on the comp
seems a bad change for faster scene loading.
i never heard of baking roto's in nuke,
@nhat, what do mean exactly ?
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
