simple to diagnose - launch Nuke with the performance metrics option enabled. ie nuke -P, it will show you which nodes are slowest.
On 6 March 2013 22:43, John RA Benson <[email protected]> wrote: > Hard to diagnose without a script! Other script slowdowns will also be > vectorblurs, optical flow, retimes/frameblends, uber-mega sized files in > the reads... If you find any part of the script that drags (walk down the > tree until it does), a precomp just after the slow node could help. A well > thought out script for efficiency could easily have many more nodes than a > brute force version and still be faster. > > good luck - > jrab > > On Mar 6, 2013, at 9:18 AM, Howard Jones <[email protected]> wrote: > > Check your bounding boxes that can slow things down > > Howard > > On 6 Mar 2013, at 02:12, Richard Bobo <[email protected]> wrote: > > If you have lots of RotoPaint nodes with many strokes and/or shapes in > them, that can really slow things down. Try to keep the number of strokes > in each RotoPaint node to a smaller number… > > Rich > > > > Rich Bobo > Senior VFX Compositor > Armstrong-White > http://armstrong-white.com/ > > Email: [email protected] > Mobile: (248) 840-2665 > Web: http://richbobo.com/ > > "The nobler sort of man emphasizes the good qualities in others, and > does not accentuate the bad. The inferior does." > - Confucius > > > > > > > > > > On Mar 5, 2013, at 7:44 PM, Randy Little <[email protected]> wrote: > > first thingk I always do if just comp and paste everything into a new > comp. It could also be things like the plates are a file that nuke > doesn't like. Say exr in a block compression. > > > Randy S. Little > http://www.rslittle.com <http://reel.rslittle.com/> > http://www.imdb.com/name/nm2325729/ > > > > > On Mon, Mar 4, 2013 at 1:33 PM, JoePockaj < > [email protected]> wrote: > >> ** >> So I am very new to Nuke and forums about Nuke but I have yet to find any >> solution to my problem. I am having some slowdown problems when working in >> Nuke with a certain project. The thing that confuses me is that it is >> really only the one script. It is a blood hit that has about 70 nodes in >> total. Thing is, I have another script ( wire removal) I was just working >> on and it was several times faster and it had almost 1000 nodes. This leads >> me to believe that the problem is something to do with the project >> specifically. >> If anyone has any hints on how to speed things up, they would be most >> welcome. >> >> Thank you >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 > > > > _______________________________________________ > 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
