I got a response back from support and it looks like this was an existing bug: > > Bug 37146 - Motionblur samples for RotoPaint and Roto nodes do not > increase when large numbers are used as input in the timeline. >
On Sun, May 4, 2014 at 7:24 AM, Mario Maruska <majomaru...@gmail.com> wrote: > It's odd that the motionblur sampling would break at high frame numbers in > the first place. > Ended up using vector generator and vectorblur (..deadline is in 8 hours, > no time to fix things properly) > > Cheers for sending the bug report Jed. > > Thanks for the help guys ! > > > On Sat, May 3, 2014 at 1:24 PM, Randy Little <randyslit...@gmail.com>wrote: > >> Im guessing its to late to use the read node to start the plate at 1 and >> then write with original frame numbers? Then use offset in roto node to >> set it to frame one as needed? >> On May 3, 2014 3:08 AM, "Jed Smith" <jedy...@gmail.com> wrote: >> >>> You could use a python script something like >>> this<https://gist.github.com/jedypod/c8e52de11e0b4af890ba>to offset the >>> lifetime start and end of all roto shapes in all roto or >>> rotopaint nodes. >>> >>> However it sounds like you might need to offset the animation of the >>> curves in time, so that the motionblur sampling will function correctly. >>> Adjusting the lifetime start and end will not change the timing of the roto >>> shapes, it will only turn them on or off at different frames. >>> >>> I have verified the bug with motionblur sampling at high frame numbers >>> and sent a bug report to the foundry. It looks like time-offseting the >>> shapes backward in time does not fix the sampling issue. >>> >>> You might try selecting all keys of all shapes in each roto node and >>> offsetting them backwards by a sufficient number of frames. You could >>> probably do this with python also, but I'm sleepy. >>> >>> Hope that helps! >>> >>> On Friday, 2014-05-02 at 4:26a, Mario Maruska wrote: >>> >>> Hi all, >>> >>> I've got some scenes with frame ranges starting at over 1 000 000 (non >>> normalised conform...) >>> and the roto & rotopaint nodes don't do motion blur sampling properly at >>> such high frame numbers. >>> >>> Is there a way to globally offset the curves' lifetime start/end ? >>> Those parameters don't seem to show up in curve editor / dope sheet. >>> >>> I'd do it by hand but it's hundreds of roto shapes. >>> >>> Cheers, >>> Mario >>> _______________________________________________ >>> Nuke-users mailing list >>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> >>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>> >> >> _______________________________________________ >> Nuke-users mailing list >> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> > > > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
