Thanks Ben, I think I tried this solution at one point...
where I set everything up using my High resolution read's then in order to get the same transforms, I reformatted my low res stuff to the high resolution...cloned the transforms over ....and back again. This didn't go over well for interactivity, and it elimintated the purpose of having the low resolution images. There was a diffference in speed switching from high to low...but not interactive. Once I set up a scene with only the low res reads, the interactivity when adjusting the transform sliders looked like we were trying to make a real time Terry Gilliam short :) (meaning, it was quick) On Thu, Dec 19, 2013 at 2:01 AM, Ben Dickson <[email protected]> wrote: > If you do need to do the Transforms on each different resolution > (instead of reformatting at the end), you could potentially sandwich the > Transform node between two Reformats - one to reformat into a consistent > format, then apply your transform, then a second Reformat back to the > original size > > Like this, which should work regardless of the input size (and would be > easily gizmoable): > > set cut_paste_input [stack 0] > version 8.0 v1 > CheckerBoard2 { > inputs 0 > format "1024 1024 0 0 1024 1024 1 square_1K" > name CheckerBoard1 > selected true > xpos 501 > ypos -126 > } > Reformat { > format "2048 2048 0 0 2048 2048 1 square_2K" > name Reformat1 > label "To \"high\" res" > selected true > xpos 501 > ypos -12 > } > Transform { > translate {-25 40} > rotate 5.039086546 > scale 1.316 > center {1250 1175} > name Transform1 > label "Regular transform node" > selected true > xpos 501 > ypos 38 > } > Reformat { > type "to box" > box_width {{Reformat1.input.width}} > box_height {{Reformat1.input.height}} > box_fixed true > name Reformat2 > label "Back to original format" > selected true > xpos 501 > ypos 76 > } > > > On 19/12/13 16:47, 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 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 > > > > -- > ben dickson > 2D TD | [email protected] > rising sun pictures | www.rsp.com.au > _______________________________________________ > 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
