A friend pointed me to this tutorial:  https://vimeo.com/63503007 
<https://vimeo.com/63503007>
It helped quite a bit with the workflow ideas, including the BlackOutside node 
which I was unaware of. That solved the stretchy pixels problem.

Thanks for all of the help and suggestions! As I usually do, I will be saving 
an example script as a sort of Nuke Notebook, so the next time I need to do 
something similar, I’ll be able to look it up…  ;^)

Rich 



> On Apr 17, 2015, at 10:53 PM, Diogo Girondi <diogogiro...@gmail.com> wrote:
> 
> 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 output of that jazz to your original input or 
> something that has the same format of your image before the crop. On the 
> output of that jazz before the merge add a position node and type in the x 
> and y values from the crop, this should yield your original image with your 
> jazz minus the losses associated with the LensDistortion.
> 
> cheers,
> diogo
> 
> On Fri, Apr 17, 2015 at 3:09 PM, Rich Bobo <richb...@mac.com 
> <mailto:richb...@mac.com>> wrote:
> *** 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:
>       preset [format]
>       box       (...selected "Set to default" from anim. menu to populate x, 
> y, r, and t values...)
>       [x] intersect  [x] black outside
> 
> 
> — The Reformat is used to expand the format size to encompass the undistorted 
> plate size… which gives stretched pixels.
> — The Crop with intersect and black outside squashes the stretched pixels.
> 
> 
> *** Whew! Seems like the LensDistort node ought to have an option to create 
> this without all the extra nodes, right...?!?
> 
> 
> 
> *** And, to bring things back to square one…
> 
> (Copy of original) LensDistort:
>       [  ] Undistort     (…unchecked...)
>       filter [Cubic]
>       Distortion Scaling [Scale to Input Format]
> 
> Reformat:
>       type [scale]
>       scale [0.9606147]     (...value derived from 1/1.041 — one, divided by 
> original scaling amount...)
>       resize type [none]    [x] center
>       filter [Cubic]   [  ] preserve bounding box    (…unchecked...)
> 
> 
> *** So, thank you to everyone for your help!
> 
> 
> Rich
> 
> 
>> On Apr 17, 2015, at 1:29 PM, Igor Majdandzic <subscripti...@badgerfx.com 
>> <mailto:subscripti...@badgerfx.com>> wrote:
>> 
>> 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:
>>> 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 intersect 
>>> checked. That way you get the image with a black outline instead of the 
>>> stretched pixels.
>>> 
>>> Thats what we are here for :)
>>> Igor
>>> 
>>> Am 17.04.2015 um 18:58 schrieb 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, but I can live with that. I had hoped that the pixels would be 
>>>> mapped to black. It seems like that’s what the black outside button should 
>>>> be doing, but it’s obeying some other unknown format size…
>>>> 
>>>> Thanks!
>>>> Rich
>>>> 
>>>> 
>>>>> On Apr 17, 2015, at 12:47 PM, Igor Majdandzic <subscripti...@badgerfx.com 
>>>>> <mailto:subscripti...@badgerfx.com>> wrote:
>>>>> 
>>>>> 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, 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 to expand the plate/format size to encompass the 
>>>>>> undistorted size. I.e., to have the size expand without clipping pixels. 
>>>>>> It’s the equivalent of increasing Photoshop’s Canvas Size. If I do an 
>>>>>> Undistort in PFTrack, for example, the image size is automatically 
>>>>>> expanded.
>>>>>> 
>>>>>> I don’t know why I can’t figure this out, but any combination of 
>>>>>> Reformat or Merge-ing over a larger image size will not reveal the 
>>>>>> hidden pixels! I know I must be missing something really simple, 
>>>>>> right..?  (8^\
>>>>>> 
>>>>>> Thanks for any help,
>>>>>> Rich
>>>>>> 
>>>>>> 
>>>>>> Rich Bobo
>>>>>> Senior VFX Compositor
>>>>>> Armstrong White
>>>>>> Email:  rich.b...@armstrong-white.com 
>>>>>> <mailto:rich.b...@armstrong-white.com>
>>>>>> http://armstrong-white.com/ <http://armstrong-white.com/>
>>>>>> 
>>>>>> Email:  richb...@mac.com <mailto:richb...@mac.com>
>>>>>> Mobile:  (248) 840-2665
>>>>>> Web:  http://richbobo.com/ <http://richbobo.com/>
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Nuke-users mailing list
>>>>>> Nuke-users@support.thefoundry.co.uk 
>>>>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>>>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>>>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>>>>> _______________________________________________
>>>>> Nuke-users mailing list
>>>>> Nuke-users@support.thefoundry.co.uk 
>>>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Nuke-users mailing list
>>>> Nuke-users@support.thefoundry.co.uk 
>>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>>> 
>>> 
>>> _______________________________________________
>>> Nuke-users mailing list
>>> Nuke-users@support.thefoundry.co.uk 
>>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
>> _______________________________________________
>> Nuke-users mailing list
>> Nuke-users@support.thefoundry.co.uk 
>> <mailto:Nuke-users@support.thefoundry.co.uk>, 
>> http://forums.thefoundry.co.uk/ <http://forums.thefoundry.co.uk/>
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
>> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
> 
> 
> _______________________________________________
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk 
> <mailto:Nuke-users@support.thefoundry.co.uk>, http://forums.thefoundry.co.uk/ 
> <http://forums.thefoundry.co.uk/>
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users 
> <http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users>
> 
> _______________________________________________
> Nuke-users mailing list
> Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to