I don't know how useful or even smart would be to rely on image data to debug
renders where the problem is probably the actual image. You may end up with
frames where not even a single pixel is written and yet the file is there.
Best thing to do is use a decent render manager that provides you
Yes, these are all pretty clever ideas!
As for the logs, uh, no. Succesfully completing jobs don't leave a
trail, unless you ask to keep the log before rendering. At least
that's for logs I can get at. So that frame that took an hour still
rendered successfully
You're right about the logs on successfully rendered files, but at least in
Qube (and most render managers that I know of) you still have access to
which node rendered which frame. So a bit of digging around should suffice
even if the manager flags that frame as successful.
Metadata for sure is
I know it will sound inappropriate and semi-arrogant (and of course it IS after
all an issue in Nuke that it has no support for TIFF metadata, yes) but just to
recap:
- you are having sour frames in your render
- the likely problem is some machine which has corrupt RAM sticks (we've had
this)
while i appreciate everone's help, you pegged it: your response is
sort of inappropriate and semi-arrogant.
This thread concerns accessing a basic function that I figured nuke
was capable of: metadata/tagging in a tiff format.
the reasons are really
Hey guys,
I've been compositing CG backgrounds with green screen live plates. I've
attached a screenshot of one of the working scripts, where the grain on the
CG background is working fine.
For some reason, this technique isn't working anymore even though it's working
on other scripts.
A
You probably have Apply only through alpha turned on in the grain node and
then have no alpha coming through. That's the first thing I'd check.
Sent from my iPhone
On Jan 30, 2013, at 9:54 AM, Todd Groves t...@nulightfx.com wrote:
Sorry guys, I forgot to add the screen shot….here it is…..
The default for the grain node is to apply only through the incoming
alpha. Check your alpha and make sure it's correct?
On Wed, Jan 30, 2013 at 1:03 PM, Joe Laude loudn...@gmail.com wrote:
You probably have Apply only through alpha turned on in the grain node
and then have no alpha coming
Thanks, Joe! That was it!
On Jan 30, 2013, at 10:03 AM, Joe Laude wrote:
You probably have Apply only through alpha turned on in the grain node and
then have no alpha coming through. That's the first thing I'd check.
Sent from my iPhone
On Jan 30, 2013, at 9:54 AM, Todd Groves
Thanks, John. :)
On Jan 30, 2013, at 10:23 AM, John Mangia wrote:
The default for the grain node is to apply only through the incoming alpha.
Check your alpha and make sure it's correct?
On Wed, Jan 30, 2013 at 1:03 PM, Joe Laude loudn...@gmail.com wrote:
You probably have Apply only
This is definitely helpful, though it would be nice if there were a built
in function. Thanks guys.
On Mon, Jan 28, 2013 at 6:42 PM, Nathan Rusch nathan_ru...@hotmail.comwrote:
Ah yes, great catch Ben. Seems there's still no way to correlate track
names with tracks, or even determine how many
Now, is there a way to get the name of a particular tracker in the new
tracker node without parsing the node out? I'm guessing again that there
is no built in function for this.
On Wed, Jan 30, 2013 at 11:30 PM, John Mangia j...@johnmangia.com wrote:
This is definitely helpful, though it would
12 matches
Mail list logo
