width = 1998
Strange - something funny with our fbx conversions then? Or maybe the win_translate isn't the filmback offset? I would have thought the values for offset and calculated offset would be the same, and the actual win_translate.u and the calculated u would be the same. the actual offset for the first shot is -24 pixels and the win_translate.u = 0.18, yet the calculated u is 0.024. The 2 cameras with offsets of -24 both had a u of 0.018, but by using these calculations it should be 0.024. I'm not sure what's correct... jrab Deke Kincaid wrote: u would be: -1 * (2/width * offset)v would be: ((root.format.h/root.format.w)*2)/root.format.h * offset -deke On Thu, Apr 28, 2011 at 14:26, John RA Benson <john.benson.macg...@gmail.com> wrote:While we're on the subject of cameras and a little matrix math - does anyone have the math for converting pixel values of the offset of a filmback into the window u value for the camera? Say I want to offset the image by 15 pixels, I'd need to adjust the window u by ... ? thanks! JRAB_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python |
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
