[Nuke-users] RotoPaint knobDefault's for toolbar settings

2012-04-09 Thread Alexander Berson

hello,

Is there a straight forward way of setting the tool bar knobDefaults on 
create for the RotoPaint node?


ie

nuke.knobDefault('RotoPaint.toolbar_opacity', '0.05')
nuke.knobDefault('RotoPaint.toolbar_lifetime_type', 'all')

obviously don't work or I'm missing something.. also not sure what the 
expression would be if I wanted it to apply these settings only under 
certain paint tools inside of the roto paint node.


ie
clone and the eraser tool gets set to : opacity = .05
lifetime = all
other tools get left at their default state of single frame and 1 opacity.


thanks,


___
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


Re: [Nuke-users] RotoPaint knobDefault's for toolbar settings

2012-04-09 Thread pixelcowbo...@gmail.com
Hi Alex, you have to do it like this (for lifetime, for example). They
should really change the way this works, I have a bug id for it: bug
#10544


nuke.knobDefault(RotoPaint.toolbox, '''clone {
{ brush ltt 0}
{ clone ltt 0}
{ blur ltt 0}
{ sharpen ltt 0}
{ smear ltt 0}
{ eraser ltt 0}
{ reveal ltt 0}
{ dodge ltt 0}
{ burn ltt 0}
}''')

On Mon, Apr 9, 2012 at 3:45 PM, Alexander Berson aber...@wetafx.co.nz wrote:
 hello,

 Is there a straight forward way of setting the tool bar knobDefaults on
 create for the RotoPaint node?

 ie

 nuke.knobDefault('RotoPaint.toolbar_opacity', '0.05')
 nuke.knobDefault('RotoPaint.toolbar_lifetime_type', 'all')

 obviously don't work or I'm missing something.. also not sure what the
 expression would be if I wanted it to apply these settings only under
 certain paint tools inside of the roto paint node.

 ie
 clone and the eraser tool gets set to : opacity = .05
                                                            lifetime = all
 other tools get left at their default state of single frame and 1 opacity.


 thanks,


 ___
 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



-- 
Jose Fernandez de Castro
___
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


Re: [Nuke-users] RotoPaint knobDefault's for toolbar settings

2012-04-09 Thread Magno Borgo

type help('_curvelib') on script editor and run to find out the attributes.

ltt = lifetime
opc = opacity
and so on.



Hi Alex, you have to do it like this (for lifetime, for example). They
should really change the way this works, I have a bug id for it: bug
#10544


nuke.knobDefault(RotoPaint.toolbox, '''clone {
{ brush ltt 0}
{ clone ltt 0}
{ blur ltt 0}
{ sharpen ltt 0}
{ smear ltt 0}
{ eraser ltt 0}
{ reveal ltt 0}
{ dodge ltt 0}
{ burn ltt 0}
}''')

On Mon, Apr 9, 2012 at 3:45 PM, Alexander Berson aber...@wetafx.co.nz  
wrote:

hello,

Is there a straight forward way of setting the tool bar knobDefaults on
create for the RotoPaint node?

ie

nuke.knobDefault('RotoPaint.toolbar_opacity', '0.05')
nuke.knobDefault('RotoPaint.toolbar_lifetime_type', 'all')

obviously don't work or I'm missing something.. also not sure what the
expression would be if I wanted it to apply these settings only under
certain paint tools inside of the roto paint node.

ie
clone and the eraser tool gets set to : opacity = .05
   lifetime =  
all
other tools get left at their default state of single frame and 1  
opacity.



thanks,


___
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







--
**
Magno Borgo

www.borgo.tv
www.boundaryvfx.com
___
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] Creating infinate zoom and image nesting

2012-04-09 Thread mesropa
I have been trying for the last few days in creating an Earth Zoom also known 
as a Cosmic Zoom or as I like to think of it simply as image nesting. I found 
a tutorial for it in AE and it seams straight forward. It can also be done in 
Flame with the same logical steps, however I have been unable to do the same 
thing using Nuke. The problem is that once a node passes through a merge the 
pixels are baked down. You can have transform nodes one after the other doing 
inverse things and because of CONCATENATING they will cancel each other out 
without effect. but if you scale something down using a transform and merge it 
with another plate the output can not be inversely scaled back up with out 
degradation. Short of creating giant 30K and larger images (using a reformat to 
nest them ) I can't make something work as efficiently as possible. Below is 
the tutorial of the After Effects  setup. If any one can give some pointers 
that would be an amazing help

http://www.videocopilot.net/tutorial/earth_zoom/

Thanks



___
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

Re: [Nuke-users] Creating infinate zoom and image nesting

2012-04-09 Thread Ivan Busquets
Hi,

In Nuke, I think there's 2 ways you could go about this:

1 - Keep all your transforms together for each image, before merging them
together. That means you'll probably want to have one master transform that
drives the camera move, and have it cloned (or expression linked) as the
last transform of each one of your images. Then, above that transform, just
position, scale each image to line them up. And if you need to do any
masking to blend them together, make sure you do that before the transforms.

2 - The workflow you describe from AE  Flame can be achieved by moving to
a 3D setup instead. One of the really cool things about Nuke that doesn't
get enough rep is the fact that geometry honors concatenation when looking
up its textures. So, say you have an image, scale it way down, and put it
on a card. If you render that through a camera that gets very close to the
card (and therefore scales it up again), you'll see that it's still
concatenating with the transformations before the card. And, most
importantly, this stays true even when you use MergeMaterial nodes.
So, for the case of the Earth Zoom, you could use a setup like this  (and
if you're going to be adding cloud layers, etc, they might need to have
some parallax, so I would definitely recommend the 3D setup in this case):

set cut_paste_input [stack 0]
version 6.3 v4
StickyNote {
 inputs 0
 name StickyNote1
 label because of the way geometry textures itself honoring\nconcatenation
of transforms, you can get close to your scaled\ndown images without
loosing detail down here
 selected true
 xpos -1564
 ypos 342
}
push $cut_paste_input
Camera2 {
 translate {{curve x1 0} {curve x1 0} {curve x1 -0.528 x20 1.528}}
 name Camera1
 selected true
 xpos -1586
 ypos 250
}
CheckerBoard2 {
 inputs 0
 name CheckerBoard1
 selected true
 xpos -1221
 ypos -27
}
Transform {
 scale 0.1
 center {1024 778}
 name Transform8
 label sacled way down
 selected true
 xpos -1228
 ypos 61
}
CheckerBoard2 {
 inputs 0
 name CheckerBoard7
 selected true
 xpos -1318
 ypos -144
}
Transform {
 scale 0.3
 center {1024 778}
 name Transform9
 label sacled way down
 selected true
 xpos -1318
 ypos -55
}
ColorWheel {
 inputs 0
 gamma 0.45
 name ColorWheel1
 label BG = widest image
 selected true
 xpos -1428
 ypos -230
}
MergeMat {
 inputs 2
 name MergeMat2
 selected true
 xpos -1428
 ypos -49
}
MergeMat {
 inputs 2
 name MergeMat1
 selected true
 xpos -1428
 ypos 67
}
Card2 {
 translate {0 0 -0.713866}
 control_points {3 3 3 6

1 {-0.5 -0.5 0} 0 {0.166865 0 0} 0 {0 0 0} 0 {0 0.166865 0} 0 {0 0
0} 0 {0 0 0}
1 {0 -0.5 0} 0 {0.166716 0 0} 0 {-0.166716 0 0} 0 {0 0.166865
0} 0 {0 0 0} 0 {0.5 0 0}
1 {0.5 -0.5 0} 0 {0 0 0} 0 {-0.166865 0 0} 0 {0 0.166865 0} 0 {0 0
0} 0 {1 0 0}
1 {-0.5 0 0} 0 {0.166865 0 0} 0 {0 0 0} 0 {0 0.166716 0} 0 {0
-0.166716 0} 0 {0 0.5 0}
1 {0 0 0} 0 {0.166716 0 0} 0 {-0.166716 0 0} 0 {0 0.166716 0} 0
{0 -0.166716 0} 0 {0.5 0.5 0}
1 {0.5 0 0} 0 {0 0 0} 0 {-0.166865 0 0} 0 {0 0.166716 0} 0 {0
-0.166716 0} 0 {1 0.5 0}
1 {-0.5 0.5 0} 0 {0.166865 0 0} 0 {0 0 0} 0 {0 0 0} 0 {0 -0.166865
0} 0 {0 1 0}
1 {0 0.5 0} 0 {0.166716 0 0} 0 {-0.166716 0 0} 0 {0 0 0} 0 {0
-0.166865 0} 0 {0.5 1 0}
1 {0.5 0.5 0} 0 {0 0 0} 0 {-0.166865 0 0} 0 {0 0 0} 0 {0 -0.166865
0} 0 {1 1 0} }
 name Card1
 selected true
 xpos -1428
 ypos 158
}
push 0
ScanlineRender {
 inputs 3
 output_motion_vectors_type accurate
 name ScanlineRender1
 selected true
 xpos -1428
 ypos 270
}


Hope that helps.

Cheers,
Ivan



On Mon, Apr 9, 2012 at 6:09 PM, mesropa
nuke-users-re...@thefoundry.co.ukwrote:

 **
 I have been trying for the last few days in creating an Earth Zoom also
 known as a Cosmic Zoom or as I like to think of it simply as image
 nesting. I found a tutorial for it in AE and it seams straight forward. It
 can also be done in Flame with the same logical steps, however I have been
 unable to do the same thing using Nuke. The problem is that once a node
 passes through a merge the pixels are baked down. You can have transform
 nodes one after the other doing inverse things and because of CONCATENATING
 they will cancel each other out without effect. but if you scale something
 down using a transform and merge it with another plate the output can not
 be inversely scaled back up with out degradation. Short of creating giant
 30K and larger images (using a reformat to nest them ) I can't make
 something work as efficiently as possible. Below is the tutorial of the
 After Effects setup. If any one can give some pointers that would be an
 amazing help

 http://www.videocopilot.net/tutorial/earth_zoom/

 Thanks

 ___
 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

Re: [Nuke-users] Creating infinate zoom and image nesting

2012-04-09 Thread chris
there are probably other solutions to this, but my first go 
would be to use a master transform node for the zoom and create 
expression linked (or cloned) instances in every branch of each 
tile before the merge, then a separate transform to adjust scale 
and then merge them..


something like:


set cut_paste_input [stack 0]
CheckerBoard2 {
 inputs 0
 boxsize 300
 color0 0
 color1 1
 color2 0
 color3 1
 centerlinewidth 0
 name CheckerBoard2
 selected true
 xpos -135
 ypos -468
}
Grade {
 blackpoint -0.075
 whitepoint {2.45 1 1 2.45}
 name Grade1
 selected true
 xpos -135
 ypos -396
}
Remove {
 channels alpha
 name Remove1
 selected true
 xpos -135
 ypos -364
}
Transform {
 translate {{Transform1.translate} {Transform1.translate}}
 rotate {{Transform1.rotate}}
 scale {{Transform1.scale}}
 skew {{Transform1.skew}}
 center {{Transform1.center} {Transform1.center}}
 invert_matrix {{Transform1.invert_matrix}}
 filter Keys
 clamp {{Transform1.clamp}}
 black_outside {{Transform1.black_outside}}
 motionblur {{Transform1.motionblur}}
 shutter {{Transform1.shutter}}
 shutteroffset {{Transform1.shutteroffset}}
 shuttercustomoffset {{Transform1.shuttercustomoffset}}
 name Transform1_clone1
 selected true
 xpos -135
 ypos -258
 icon \[value Transform1.icon]
}
CheckerBoard2 {
 inputs 0
 boxsize 60
 color0 0
 color1 1
 color2 0
 color3 1
 centerlinewidth 0
 name CheckerBoard1
 selected true
 xpos 59
 ypos -469
}
Grade {
 blackpoint -0.075
 whitepoint {1 2 1 2.45}
 name Grade2
 selected true
 xpos 59
 ypos -397
}
Remove {
 channels alpha
 name Remove2
 selected true
 xpos 59
 ypos -373
}
Transform {
 translate {{Transform1.translate} {Transform1.translate}}
 rotate {{Transform1.rotate}}
 scale {{Transform1.scale}}
 skew {{Transform1.skew}}
 center {{Transform1.center} {Transform1.center}}
 invert_matrix {{Transform1.invert_matrix}}
 filter Keys
 clamp {{Transform1.clamp}}
 black_outside {{Transform1.black_outside}}
 motionblur {{Transform1.motionblur}}
 shutter {{Transform1.shutter}}
 shutteroffset {{Transform1.shutteroffset}}
 shuttercustomoffset {{Transform1.shuttercustomoffset}}
 name Transform1_clone2
 selected true
 xpos 59
 ypos -265
 icon \[value Transform1.icon]
}
Transform {
 scale 5
 center {960 540}
 filter Keys
 name Transform2
 selected true
 xpos 59
 ypos -197
}
Merge2 {
 inputs 2
 name Merge1
 selected true
 xpos 59
 ypos -112
}
push $cut_paste_input
Transform {
 scale {{curve i x1 1 x100 0.1}}
 center {960 540}
 filter Keys
 name Transform1
 label MASTER ZOOM
 selected true
 xpos -304
 ypos -260
}



On 4/10/12 at 3:09 AM, nuke-users-re...@thefoundry.co.uk 
(mesropa) wrote:



I have been trying for the last few days in creating an
Earth Zoom also known as a Cosmic Zoom or as I like to
think of it simply as image nesting. I found a tutorial
for it in AE and it seams straight forward. It can also be
done in Flame with the same logical steps, however I have
been unable to do the same thing using Nuke. The problem
is that once a node passes through a merge the pixels are
baked down. You can have transform nodes one after the
other doing inverse things and because of CONCATENATING
they will cancel each other out without effect. but if you
scale something down using a transform and merge it with
another plate the output can not be inversely scaled back
up with out degradation. Short of creating giant 30K and
larger images (using a reformat to nest them ) I can't
make something work as efficiently as possible. Below is
the tutorial of the After Effects  setup. If any one can
give some pointers that would be an amazing help

http://www.videocopilot.net/tutorial/earth_zoom/

Thanks




___
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