Actually that's something I always found surprising about nuke; for a comp package that at its core is happily resolution independent, why does it store translation in pixels? Surely it'd be better to run them as a fraction of screen width/height, or go full fancy pants and run them as NDC. Or an option to display in pixels, but store internally as NDC.
Or am I missing something? On Thursday, December 19, 2013, Frank Rueter wrote: > use user knobs that drive the position (and centre position) in > normalised values, i.e 1 = right side of image, 0 is left side etc. > use expressions in the respective knobs that take those user knob values > and multiply them by the incoming width or height > > scale and rotate are resolution independent anyway. > > Cheers, > frank > > On 19/12/13 17:14, HSK wrote: > > Hi there, > > This may seem like...well..an odd question. > > Ive been asked to setup a multi resolution comp/group/gizmo. > > Where the user would have the choice of switching between Low / Hi > Resolution source files. > > I know there is the "Proxy" system built into Nuke, but I think that > works on a global level. They want the artists to be able to view the rest > of the comp at an independent resolution.....does this make sense? > > > So back to my question.... > > When setting up the multi resolutions...how can I automate any > transformations to match? > > since they're at different resolutions, the transform nodes have > different centers. > > > Any help or clarity would be greatly appreciated > > Steve > > > _______________________________________________ > Nuke-users mailing [email protected] <javascript:_e({}, > 'cvml', '[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
