This should be fixed for 6.3v6.
Thanks,
Wouter
-- Sent from my HP Pre3
On 14 Nov 2011 18:12, Christoffer =?UTF-8?Q?Hulusj=C3=B6?= <[email protected]> wrote:
Hi,
We are having problems with the ScannedGrain node in 6.3v5 under Linux.
When rendering, what seems to be happening is that if you have a batch/chunk size set to 1 it will only use one frame for the grain sample and render static grain over the sequence, if you have a larger chunk size like 5 it seems to be using 5 samples and might be unnoticeable but it’s still not using the full 50 frames of the original grain clip.
I ran my render tests locally through the terminal, rendering a sequence at 1, 5 and 10 frames at a time. I tried the exact same nuke script with Nuke 6.3v1 and 6.2v2 and in both those versions it worked fine, so it must be something introduced recently.
Cheers
Christoffer
We are having problems with the ScannedGrain node in 6.3v5 under Linux.
When rendering, what seems to be happening is that if you have a batch/chunk size set to 1 it will only use one frame for the grain sample and render static grain over the sequence, if you have a larger chunk size like 5 it seems to be using 5 samples and might be unnoticeable but it’s still not using the full 50 frames of the original grain clip.
I ran my render tests locally through the terminal, rendering a sequence at 1, 5 and 10 frames at a time. I tried the exact same nuke script with Nuke 6.3v1 and 6.2v2 and in both those versions it worked fine, so it must be something introduced recently.
Cheers
Christoffer
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
