Re: [Nuke-users] RotoPaint vs Roto

2015-04-17 Thread Diogo Girondi
This was requested (by myself and others) during a beta when moving from the old Bezier node to the "new" RotoPaint, it was purely a request for workflow/customization and readability reasons. Using a RotoPaint for masks implies on more clicking around, prevents you from having a default that work

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Diogo Girondi
The Reformat node in Nuke misses a option to reformat by a full box with x,y,r,t where the inputs bbox is preserved. But since it doesn't, what you can do is do your LensDistortion then add a Crop where x,y,r and t are derived from the inputs bbox via expression. Then do your jazz and merge the ou

Re: [Nuke-users] Dimensions of Grid in 3D Viewport

2015-04-17 Thread Diogo Girondi
For what I know Nuke follows the SI convention and is metric in nature, so think in terms of km, m, cm and mm. And even though there is no fixed number established for what 1 3D unit translates to I usually work by the assumption that 1 unit is equivalent to 10 cm. On Fri, Apr 17, 2015 at 5:28 PM,

Re: [Nuke-users] Dynamic black bar behind text?

2015-04-17 Thread Sam Cole
read the text node bbox, like 'nodename.bbox.x' etc On Fri, Apr 17, 2015 at 10:11 PM, Jon Wesström wrote: > Does anyone know of a clever way to have a dynamic background behind text? > > As of now, I do it manually with a rectangle tool, but that is rather > annoying. > > I know you could link

Re: [Nuke-users] Dimensions of Grid in 3D Viewport

2015-04-17 Thread Randy Little
It seems to work best if you think of it in CM. Randy S. Little http://www.rslittle.com/ http://www.imdb.com/name/nm2325729/ On Fri, Apr 17, 2015 at 3:29 PM, Daniel Hartlehnert wrote: > Hi, > > i think it has no units. But i could be wrong. > > > Am 17.04.2015 um 21:17 schrieb Igor Majdandzic

Re: [Nuke-users] Dimensions of Grid in 3D Viewport

2015-04-17 Thread Daniel Hartlehnert
Hi, i think it has no units. But i could be wrong. Am 17.04.2015 um 21:17 schrieb Igor Majdandzic: > Hello, > could somebody please shed some light what the units are in Nuke's 3D > Viewport. Or point me to linke or something. > I thought I read about it, but search did not come up with anythi

[Nuke-users] Dimensions of Grid in 3D Viewport

2015-04-17 Thread Igor Majdandzic
Hello, could somebody please shed some light what the units are in Nuke's 3D Viewport. Or point me to linke or something. I thought I read about it, but search did not come up with anything. Thanks, Igor ___ Nuke-users mailing list Nuke-users@supp

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Rich Bobo
*** OK, so here’s what I’ve got… LensDistort: [x] Undistort filter [Cubic] Distortion Scaling [Scale to Input Format] Reformat: type [scale] scale [1.041] resize type [none][x] center filter [Cubic] [x] preserve bounding box Crop:

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Igor Majdandzic
Thinking about it, just put the crop after the reformat and check intersect. that should do the trick with the least amount of work. Just make sure the crop is connected directly so it picks up the images size and not that of the root settings. Am 17.04.2015 um 19:13 schrieb Igor Majdandzic: Y

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Igor Majdandzic
Yeah, for some reason it puts black based on the image before reformatting. When you compare the two the visible information is the same. But in case you really need black, you could always put a crop after the reformat with box set to the bounding box of the image, with black outside and inter

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Pat Wong
Rich you;ll need to inverse the reformat node to get back to the original dimensions..again set the resize type to none. and preserve bounding box ticked. 1 / 1.1 (or the amount you scaled the undistorted image upstream) Kind Regards Patrick Wong 077961 35224 www.wahwahdigital.com On

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Rich Bobo
Igor, Thanks! I had tried that before, but this time I turned off “black outside”. That was cropping to some arbitrary size - i.e., not my root format and not anything else that makes any sense. The pixels that are outside my LensDistort-expanded bounding box are stretched, which is kinda ugly,

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Igor Majdandzic
Just put a reformat after the LD node and set type to 'scale', the scale itself whatever suits you (usually 1.1 should suffice) and resize type to 'none'. That should do the trick. Igor Am 17.04.2015 um 18:16 schrieb Rich Bobo: Hi, I need some help with figuring out how to reveal the extra,

Re: [Nuke-users] LensDistortion overscan help

2015-04-17 Thread Charles Bedwell
If you reformat to a larger size, say 4/5k, resize type: none and black outside turned off does that not display all the pixels? Charlie On 17 Apr 2015, at 5:41 pm, Rich Bobo mailto:richb...@mac.com>> wrote: Hi, I need some help with figuring out how to reveal the extra, hidden pixels gene

[Nuke-users] LensDistortion overscan help

2015-04-17 Thread Rich Bobo
Hi, I need some help with figuring out how to reveal the extra, hidden pixels generated by the LensDistortion node… How do I show the pixels that get scaled out of the format size after an undistort? I see the larger bounding box, but there doesn’t seem to be any option in the LensDistort node

[Nuke-users] Dynamic black bar behind text?

2015-04-17 Thread Jon Wesström
Does anyone know of a clever way to have a dynamic background behind text? As of now, I do it manually with a rectangle tool, but that is rather annoying. I know you could link the rectangle with the bounding box, or do some kind of erode, thingy, but that stops working when you have two or more