>>hmm, that might be out of my league :)
I can have a play and send you the result.
>>I looked for that, but the pre comp node “read file for output”
doesn’t have it
Yeah, I think I ran into that before as well.
I don't think the Precomp node has received much love since it's
inception, would be good to report this.
On 21/01/16 5:28 am, Gary Jaeger wrote:
On Jan 19, 2016, at 2:02 PM, Frank Rueter|OHUfx <fr...@ohufx.com
<mailto:fr...@ohufx.com>> wrote:
Instead of referencing root.name() which obviously is a moving target
in this sot of workflow, you could try (auto) creating a NoOp node in
the shots with a user knob that holds the shot's root.name(). You
could auto-update this knob upon script save to keep in in sync, then
reference that in your Write nodes.
hmm, that might be out of my league :)
>>“Cannot read from file; file does not match input” What does that mean?
Sounds like you are using exrs and Nuke thinks the upstream is more
up-to-date than the rendered output.
Try unchecking "check file matches input”
Thanks Frank. I looked for that, but the pre comp node “read file for
output” doesn’t have it. I had to go back to the original write node
in the shot script. Then I had to check “read file”, uncheck the
"check file matches input”, then uncheck “read file”. Seems a bit
flaky. Might be easier to just use straight up read nodes...
Gary Jaeger // Core Studio
249 Princeton Avenue
Half Moon Bay, CA 94019
650.728.7957 (direct)
650.728.7060 (main)
http://corestudio.com
Cheers,
frank
On 20/01/16 10:36 am, Gary Jaeger wrote:
We're having a couple issues with Precomps and wanted to see if
anybody has any experience with these. We have a series of shots we
want to combine in one master nuke, but keep the shots separate so
we can keep revving and working on them. We’re doing some additional
comping in the master script.
Creating precomp nodes and pointing them to the scripts for the
shots works fine and as expected. But it’s when we get into using
renders that the issues arise.
For context, we typically use something like this in our write nodes:
[file dirname [value root.name]]/../renders/nuke/[lindex [split
[lindex [split [value root.name] /] end] .] 0]/[lindex [split
[lindex [split [value root.name] /] end] .] 0].%04d.exr
So that we never have to worry about output names as they always
match the script. Also, folders get created if none exist, etc. It’s
a pretty foolproof way of working.
The problems:
1. The first problem is that the master nuke script now thinks it’s
looking for paths relative to ITSELF, rather than the individual
shot script. So when we click the “read file for output” nuke
complains that it can’t see a file, but the error is looking for
relative paths to master, not the shot. Any way around that anybody
can think of? Currently we’re just hard coding the path and filename
for the write node that goes into the Output node. However…
2. When we hard code the path and file name, Precomps in the master
now see the file when we tick that box, but now it complains “Cannot
read from file; file does not match input” What does that mean?
any suggestions? thanks!
Gary Jaeger // Core Studio
249 Princeton Avenue
Half Moon Bay, CA 94019
650.728.7957 (direct)
650.728.7060 (main)
http://corestudio.com
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk,http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
<ohufxLogo_50x50.png> <http://www.ohufx.com/> *vfx compositing
<http://ohufx.com/index.php/vfx-compositing> | *workflow
customisation and consulting
<http://ohufx.com/index.php/vfx-customising>* *
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk
<mailto:Nuke-users@support.thefoundry.co.uk>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
--
ohufxLogo 50x50 <http://www.ohufx.com> *vfx compositing
<http://ohufx.com/index.php/vfx-compositing> | *workflow customisation
and consulting <http://ohufx.com/index.php/vfx-customising>* *
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
