Frank, ...In your Transform node’s translate x expression, you may want to also add a tweak for the pixel aspect:
translateRel*( width*pixel_aspect) I’ve been working on a resolution-independent Slate tool lately and found I needed to take that into consideration for any anamorphic standards, such as Cinemascope, PAL and NTSC, just to name a few… Rich On Dec 19, 2013, at 3:20 PM, Frank Rueter <[email protected]> wrote: > something like this (rough and dirty): > > CheckerBoard2 { > inputs 0 > name CheckerBoard1 > selected true > xpos -478 > ypos -263 > } > set N619fac0 [stack 0] > push $N619fac0 > Reformat { > type scale > scale 0.5 > name Reformat1 > label proxy > selected true > xpos -376 > ypos -179 > } > Switch { > inputs 2 > name Switch1 > selected true > xpos -478 > ypos -114 > } > Transform { > translate {{"translateRel * width"} {"translateRel * height"}} > rotate 48 > scale 0.8 > skewX -0.98 > center {{"centerRel * width"} {"centerRel * height"}} > name Transform1 > label "relative transform" > selected true > xpos -478 > ypos -69 > addUserKnob {20 User} > addUserKnob {12 translateRel} > translateRel {-0.2 1} > addUserKnob {12 centerRel} > centerRel {1.567 0.33} > } > > > On 20/12/13 03:31, HSK wrote: >> Hi Frank, >> >> this sounds interesting... >> >> would you be able to send me a small setup? I dont think I'm quite g etting >> it...but it definitely sounds like its on the right track for what I need. >> >> >> Cheers, >> >> Steve >> >> >> On Thu, Dec 19, 2013 at 1:17 AM, Frank Rueter <[email protected]> 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 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
