I’ve got custom ENV paths (ex: os.environ["JOB”] ) in all read and write
nodes throughout the Nuke workflow.
In a Nuke Studio timeline these .nk scripts work fine. However, Nuke Studio
cannot reference through to the rendered files for playback as it obviously
can’t interpret the path.
The write node could end up describing something like:
$env(JOB)/renders/movie_v01.####.dpx
or
[python {os.environ[‘JOB’]}]/renders/movie_v01.####.dpx
I could fix the issue with a Nuke render-time callback to create an absolute
write path but for flexibility I’d really like Nuke Studio to have the ability
to interpret the path (os.path environment) properly.
However, due to the written syntax I can’t figure out how to set a environ
variables for Hiero/Nuke Studio to reinterpret the path correctly.
Any ideas?
Michael
PS As a side note I did discover that Nuke Studio derives the rendered file
paths not from the write nodes themselves but from the the " #write_info"
description on the second line of the nuke script.
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
