I guess, that makes sense since the write node will still be enabled on those frames. What if you do the same thing but on the write nodes's disable? The expression would be"Read1.error". It should disable the write if the read node has an error.
-ak On Tue, Jun 28, 2011 at 11:07 AM, Olivier Jezequel < [email protected]> wrote: > It was a very good tip, but unfortunately doesn't work on my case :( > i tried to put the expression on my write node but when rendering it is > still stopping the render at the error frames (When a keyframe work) maybe > because it is a gui thing ??? > i can't use that on the read bcs it will render me a black fame, which is > definitely a no go. > > thanks for the try > > would it work to add an expression in the tab Python in before each frame ? > i am not quiet sure what put there ... > > Anthony Kramer wrote: > >> Add an expression to the disable knob of the read node and simply put >> "error" in the expression field. This is will disable the node if there's an >> error (missing a frame, etc). >> >> -ak >> >> On Tue, Jun 28, 2011 at 10:08 AM, Olivier Jezequel < >> [email protected] >> <mailto:olivier-je@moving-**picture.com<[email protected]>>> >> wrote: >> >> Hiya, >> It is quiet specific so in advance, no i don't want black frames >> by setting the read node to it ;) >> >> I need to render in a specific pipeline that will load as >> sequences in nuke but are just still frames. >> There will be missing frames because we don't need them (naming >> conventions) >> and we want to render the same frames (not the missing ones in black) >> >> per default, nuke6.2 will stop at the first missing frame (while i >> know nuke 6.3 will carry on gently) >> so i want to write a script that check the error fames of my read >> and disable the write node at those frames >> (because a disabled node will skip the frame where it is disabled) >> >> i don't know how to query an action for each frame, and not sure >> where to put the script too in fact. >> >> it would be something like this in my mind : >> >> for each frame : >> if error : >> write.knob('disable').**setValue(1) >> >> cheers >> Olivier >> ______________________________**_________________ >> Nuke-python mailing list >> >> Nuke-python@support.**thefoundry.co.uk<[email protected]> >> >> <mailto:Nuke-python@support.**thefoundry.co.uk<[email protected]> >> >, >> >> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> >> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/** >> nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python> >> >> >> ------------------------------**------------------------------** >> ------------ >> >> >> ______________________________**_________________ >> Nuke-python mailing list >> Nuke-python@support.**thefoundry.co.uk<[email protected]>, >> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> >> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python> >> >> > > ______________________________**_________________ > Nuke-python mailing list > Nuke-python@support.**thefoundry.co.uk<[email protected]>, > http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/> > http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-python<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python> >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
