thanks guys.
yes, that's how I have been generating grain plates, but I found I got
better results using F_Regrain live - when and if it works.
cheers,
frank
On 09/08/13 15:12, Ben Dickson wrote:
I've always found the F_Regrain unreliable, for various reasons:
* it used to redo the analysis on each frame when on the farm, so you
had to HoldFrame the grain-src input. This may have been fixed, but I
still do this out of paranoia
* sometimes, the grain seed seems to change - e.g when packaging shots
up for sending to other vendors, several times I've noticed the
F_Regrain was producing slightly different results.
* Bug 34939 - F_ReGrain - negative Grain input crashes Nuke
Probably others too.. but, all these problems go away if you precomp
the generated grain, something like this:
http://i.imgur.com/2dSTW2I.png
Not exactly the same as applying the Regrain node directly to the
image, but much less troublesome
On 09/08/13 12:18, Frank Rueter wrote:
Hi all,
this is reported but was wondering if I'm the only one who finds
F_Regrain close to unusable in a render farm environment?
It's all dandy as long as you render locally, but as soon as you have
multiple machines render a script with F_Regrain in it, some of the
frame batches are all screwed up with completely wrong grain (way to big
and intense - confetti like).
It seems like F_Regrain samples it grain again when the batch starts or
something. I'm rendering on linux and osx, workstation is linux.
Does anybody know what I'm talking about? Maybe even a solution to
fixing it? I will generate a grain plate locally now and use that on the
render farm for now.
Cheers,
frank
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
