prolost: Nuke

Showing posts with label Nuke. Show all posts

StarPro plugin from Maas Digital

StarPro plugin from Maas Digital

10:32 PM

the Slice Tool for Nuke

the Slice Tool for Nuke

11:51 AM

ProceduralNoise (ProcGeo) node test

ProceduralNoise (ProcGeo) node test

Sample file

10:05 AM

Frank Rueter's NukeMari Workflow Video

Frank Rueter's NukeMari Workflow Video

Frank Rueter's NukeMari Workflow Video from Hieronymus Foundry on Vimeo .

9:41 AM

Understanding Nuke's unique Layer and Channel system (including the Shuffle Nodes)

Understanding Nuke's unique Layer and Channel system (including the Shuffle Nodes)

First thanks SeaDog's great info! Understanding Nuke's unique Layer and Channel system (including the Shuffle Nodes)

9:35 AM

motion vector from Maya render pass

motion vector from Maya render pass

Motion Vectors - Example II from Sagroth on Vimeo . And the Sigillarium Blog Quick note: 1: Add a " Normalized 2d motion vector ...

12:35 AM

linear color workflow in Maya shader

<div>Here is something about linear color workflow in Maya shader <a href="http://whetstonevfx.com/blog/?p=91">http://whetstonevfx.com/blog/?p=91</a> <a href="http://www.gijsdezwart.nl/tutorials.php">http://www.gijsdezwart.nl/tutorials.php</a> <a href="http://mentalraytips.blogspot.com/">http://mentalraytips.blogspot.com/</a> <a href="http://mentalraytips.blogspot.com/2009/09/my-appearance-on-fxguide-linear.html#links">http://mentalraytips.blogspot.com/2009/09/my-appearance-on-fxguide-linear.html#links</a> <a href="http://linearworkflow.com/">http://linearworkflow.com/</a> <a href="http://3dlight.blogspot.com/">http://3dlight.blogspot.com/</a> <a href="http://vimeo.com/8119194">http://vimeo.com/8119194</a> please be careful the maya mentalray node call "mia_exposure_simple"</div><div><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCChU3tEfRF9ROqWqmFY5R_ZhXcG63RAghrPojacwaGAaYxlrt_NmnunqQPuTfOHU9iROJSmkF8hyphenhyphen5PFRc0Bv0PxfB0KELn57KtYfGjHmezn74qhhISNkuvciU7CLg0PuIJuKg7IPGPj5d/s1600/mia_exposure.jpg"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5559845122141859778" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhCChU3tEfRF9ROqWqmFY5R_ZhXcG63RAghrPojacwaGAaYxlrt_NmnunqQPuTfOHU9iROJSmkF8hyphenhyphen5PFRc0Bv0PxfB0KELn57KtYfGjHmezn74qhhISNkuvciU7CLg0PuIJuKg7IPGPj5d/s400/mia_exposure.jpg" style="width: 141px; height: 185px;" /></a> Base on eat3D training setting mia_exposure_simple <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhWzJXGNDkpOxqeIlZkkgZGOdZTa7Gs7nDmzRb1KyuJPKPuSVqdKZ60r1JKGqmBXL3KxJsDqX-KzKRohhA1wl6V1HB1s80vPBoksVSPyxnt5ctkWbQDSpF9lhgDAcW6EANH4OBu3PiYIP8m/s1600/mia_exposure.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5592503624010925202" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhWzJXGNDkpOxqeIlZkkgZGOdZTa7Gs7nDmzRb1KyuJPKPuSVqdKZ60r1JKGqmBXL3KxJsDqX-KzKRohhA1wl6V1HB1s80vPBoksVSPyxnt5ctkWbQDSpF9lhgDAcW6EANH4OBu3PiYIP8m/s400/mia_exposure.jpg" style="cursor: pointer; width: 400px; height: 308px;" /></a> set Knee: 1.0/ Compression: 0/ Gamma: 2.2 it works exactly like nuke's LUT function, good for render out some color pass such (beauty/ diff/ spec/ refl/ refr/ sss/ oc...etc), if you output format is gamma 2.2(sRGB)'s Tiff/ TGA..etc, you will need to leave "mia_exposure_simple" on and set gamma 2.2 to render. But if output format is EXR in linear color space, you might set "mia_exposure_simple" gamma to 1.0 </div><div>Well! personal feel you will need to break mia_exposure_simple from maya camera, since this node does some strange result on RGB color matte (darker color)/ Point in space render (points become all flat, no depth) what I discover recently..... and the Final, Great thanks Stu / Zap and Kuan Lin..... who inspire me all the linear workflow </div>

linear color workflow in Maya shader

Here is something about linear color workflow in Maya shader http://whetstonevfx.com/blog/?p=91 http://www.gijsdezwart.nl/tutorials.php http...

7:48 AM

what is ChromAberration?????

what is ChromAberration?????

ChromAberration training from http://maltaannon.com

12:11 AM

RenderMan and Nuke.....XD

RenderMan and Nuke.....XD

RenderMan - Nuke Pipeline Plug-in [DEMO] from Peter Barnes on Vimeo .

2:35 AM

shake's IBlur in Nuke

shake's IBlur in Nuke

set cut_paste_input [stack 0] version 5.2100 push $cut_paste_input Radial { area {131.5 92 627 477} softness 0.855 name Radial1 selected tru...

1:21 PM

The waiting in finished.... finally....finally....finally-Trapcode Particular for Nuke

看到這個CG news, 眼淚差點就要流出來了.... 感謝 Red Giant Software的努力......特此發文慶祝 <a href="http://www.redgiantsoftware.com/products/all/trapcode-particular-nuke/"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5538488533455034594" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiWHDE-IX-ZeUkb5J_PTYphZ8WR846Sfl8162kEfpe8MQFU73-Gn8-AM3Kkaa8Xr4M5bXURVKsFE8auGGGZzC002n7887ZxwNOHQ84inTUTO1nHMi463IGmQG1DR7osfxrAErI9xUWWPVxB/s400/image_product_large_86.jpg" style="WIDTH: 400px; HEIGHT: 224px; CURSOR: hand" /></a> <a href="http://www.thefoundry.co.uk/products/particular/">The NEWS from Foundry</a>.... and <a href="http://www.redgiantsoftware.com/videos/tutorials/#trapcode-particular-nuke">30mins traning video </a>from Red Giant software..... <iframe src="http://player.vimeo.com/video/16424513" width="400" height="265" frameborder="0"></iframe><a href="http://vimeo.com/16424513">Trapcode Particular for Nuke Tutorial v1 by Steve Wright</a> from <a href="http://vimeo.com/thefoundry">Hieronymus Foundry</a> on <a href="http://vimeo.com">Vimeo</a>.

The waiting in finished.... finally....finally....finally-Trapcode Particular for Nuke

看到這個CG news, 眼淚差點就要流出來了.... 感謝 Red Giant Software的努力......特此發文慶祝 The NEWS from Foundry .... and 30mins traning video from Red Giant software...

6:42 PM

Point Position and Object Normal in Maya mental ray

Point Position (Point World): <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDUA9m8yLNxQdnUrha1E_Rz2WlmJPJQJDrMfUedTpM7tsIf0xEJRYTOeErxXIUi5IpPV7jMaZSbFaTtOCxOCEDsq58_hkqFq2nxdrjQACMNP0DvJBi6Ow6T1l7fxYd5-cmGVC9QUMauW0I/s1600/pointSpace.jpg"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5534610673794147938" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiDUA9m8yLNxQdnUrha1E_Rz2WlmJPJQJDrMfUedTpM7tsIf0xEJRYTOeErxXIUi5IpPV7jMaZSbFaTtOCxOCEDsq58_hkqFq2nxdrjQACMNP0DvJBi6Ow6T1l7fxYd5-cmGVC9QUMauW0I/s400/pointSpace.jpg" style="width: 400px; height: 273px;" /></a> create 3d point clouds from Maya and view it in Nuke 3d space! Create a render layer ex: pointSpaceR base on what kind of point space you need: pointCamera / pointObj or pointWorld (mostly this one)> Surface Shader's outColor <div>one thing about use linear workflow in maya mental ray, camera's mia_exposure_simple node must be remove/ break connection.</div><div></div><div>This point position render can be apply in Nuke's PositionToPoints node, xyz input for this point space render/ col input for normal color render. Base on D.T. training said, point space render suggest openEXR format and no anti-Alias render feature turn on! <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6a2jMp4G-33cQH5BVTeXw4MKcesma559uZE7wFugC0m-hLSTNjAKF42O_wz6lTW5FmpR6Uux5EJ_pvPe-3mO5dNY-o8vFw9sYfTNGTXgw2H_N957tjr-F5Fvwi29N9ebvC_6TSjSbZvG8/s1600/renderPointSpace.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5559857294228669170" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6a2jMp4G-33cQH5BVTeXw4MKcesma559uZE7wFugC0m-hLSTNjAKF42O_wz6lTW5FmpR6Uux5EJ_pvPe-3mO5dNY-o8vFw9sYfTNGTXgw2H_N957tjr-F5Fvwi29N9ebvC_6TSjSbZvG8/s400/renderPointSpace.jpg" style="cursor: pointer; width: 400px; height: 295px;" /></a> first: in the pointSpaceR render layer in render setting> Passes> Create a new "Beauty" passes from maya render passes library> Add to associated passes second: double click the beauty and dis-check "Filtering" and set Frame Buffer Type "32-bit Float", of course you also need to enable "RGBA (Float) 4x32 Bit" under Quality/ Framebuffer in render setting. object Normal: object normal pass can be render with point space pass together, simple add a default pass call "Object Normal (World space)" from library. this also suggest turn off anti-alias on render. This just the object normal only, no texture normal. If you need texture normal as well, just use colorR render layer that already has well texture bump and displace map setup to add the same "Object Normal (World space)", will get the object normal and texture normal together. </div>

Point Position and Object Normal in Maya mental ray

Point Position (Point World): create 3d point clouds from Maya and view it in Nuke 3d space! Create a render layer ex: pointSpaceR base on w...

8:55 AM

Install gizmo in Nuke and create icon on menu

1: after you create your part of nuke script into a group (Edit>Node>Group>Collapse To Group (Ctrl+G) 2: Right Click on your Group node's properites> Manage User Knobs... to setup your own gizmo interface what ever you need 3: and click group node's Export as gizmo to your nuke's plugins folder ex: X:/Program Files/Nuke6.0v2/plugins/ 4: click X and pick TCL to type the gizmo name you just save, to test saved gizmo working or not? 5: Create a text file call menu.py toolbar = nuke.toolbar("Nodes") # The "3DTools" menu m = toolbar.addMenu("3DTools", "ReConverge.png") m.addCommand("DepthGrade", "nuke.createNode(\"DepthGrade\")") and save menu.py into your system folder below: •Linux: /users/login name/.nuke /usr/local/Nuke6.0v2/plugins •Mac OS X: /Users/login name/.nuke /Applications/Nuke6.0v2/Nuke6.0v2.app/Contents/MacOS/plugins •Windows: In the .nuke directory, which can be found under the directory pointed to by the HOME environment variable. If this variable is not set (which is common), the .nuke directory will be under the folder specified by the USERPROFILE environment variable - which is generally of the form drive letter:\Documents and Settings\login name\ (Windows XP) or drive letter:\Users\login name\ (Windows Vista). ex: X:\Documents and Settings\username\.nuke <a href="http://www.dvjimmy.com/nuke_source/depthGrade_gizmo_sample.rar">depthGrade_example...</a><a href="http://www.dvjimmy.com/nuke_source/nuk203-class03.rar">.</a> Show gixmo internal structure after export as gizmo Gizmos are designed to be hard coded once you export them. To get around this and get back into the structure you will have to locate the .gizmo file in your plugin folder or wherever its stored. Now open this file in a text editor, and change the name "gizmo" on the third line from the top to "group" Now you can copy and paste the acsii text back into Nuke. Now you will have the gizmo back as a group node that you can Show contents and edit. update: in nuke6 has "copy to group" on gizmo to quick reveal in qroup. cool!

Install gizmo in Nuke and create icon on menu

1: after you create your part of nuke script into a group (Edit>Node>Group>Collapse To Group (Ctrl+G) 2: Right Click on your Group ...

8:54 AM

Nuke customer build viewer LUT update!

以前的文章關於<a href="http://vfxjimmy.blogspot.com/2009/01/nuke-tips-customer-build-nuke-lut.html">Nuke customer build viewer LUT</a>, 在Nuke 5.2之後有不同的作法. 請參閱Nuke官方 <a href="http://www.thefoundry.co.uk/dl_file.aspx?ui=D3B80FB5-D28B-4105-94B0-F49A7F6F09B7">Basic Worlflows colour management part3</a> There are two type of process: Viewer Process and Iuput Process 1: Input Process: >add a ColorLookup node and adjust the color curve look result you want! >disconnect the ColorLookup node from comp tree, just rename the ColorLookup node to "VIEWER_INPUT", now IP fountion turn on and all viewer result will apply the color curve. >or don't change the name of Colorlookup, disconnect the ColorLookup node from comp tree, select the ColorLookup node and go menu Edit>Node>Use as Input Process. Now IP fountion on again. (But the down side of this way, that is hard to know which node is your Input Process!) 2:Viewer Process (create custom build viwer lookup): >Turn off your sRGB viwerProcess to none, so Nuke viewer display the raw linear image. >Add Colorspace node and change out to sRGB (default is Linear), or other color space you want to output, personally like gamma2.2 >If you need to change more lookup color curve, just add another ColorLookup node for example. >If you need other image process ex:soft, just add Blur node for example. >select Colorspace+ColorLookup+Blur nodes that you want to add the customer build viwer. >Ctrl/Command+G to group the nodes >To export as gizmo, click "Home" on the export window, type/.nuke/name of gizmo. (first letter of gizmo must be capital) >register customer build viwer lookup gizmo with Python >edit init.py with simple text editor nuke.ViewerProcess.register("Name of display", nuke.Node, ("Name of gizmo", "")) >restart nuke to active init.py >now you can pick the custom viewer lookup from the list.

Nuke customer build viewer LUT update!

以前的文章關於 Nuke customer build viewer LUT , 在Nuke 5.2之後有不同的作法. 請參閱Nuke官方 Basic Worlflows colour management part3 There are two type of process:...

6:00 AM

Nuke 6/NukeX 6 Released

Nuke 6/NukeX 6 Released

Dam!... Foundry released new Nuke 6/NukeX 6.... Some impressive new feature (something I tested) 1: new Paint and Roto tool: much better tha...

8:12 PM

Color Curves Quick Reference Guide

Thanks John Dickinson's Color Curves Quick Reference Guide.... <a href="http://www.motionworks.com.au/tips/curves_guide.gif" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5411762183549246946" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgPdYVdvISXgdgOn-zy4ws8ayjOfFXRWILZf8GinfQC8B21ywAkCGnC9f_Hb7wD3wbTru3EX4IM5TEGP05UWBDnDSH8LqMxyIydiaveRi1T6KItC2_SzDEGLLzVzQwg5GaeRubjgPKGvU65/s400/curves_guide_thumb.jpg" style="cursor: pointer; width: 80px; height: 80px;" /></a> One thing you need to keep in mind...color combine RGB... Red(1,0,0) <> Cyan(0,1,1) Green(0,1,0) <> Magenta(1,0,1) Blue(0,0,1) <> Yellow(1,1,0) So when your eyes tell you the image looks so yellow, or Magenta... you will know how to fix them base on RGB channel...

Color Curves Quick Reference Guide

Thanks John Dickinson's Color Curves Quick Reference Guide.... One thing you need to keep in mind...color combine RGB... Red(1,0,0) Cy...

6:39 AM

add nuke gizmo tool into Nuke tool bat!

add nuke gizmo tool into Nuke tool bat!

edit menu.py file under C:\Documents and Settings\Username\.nuke (for example!), and add a gizmo call "DepthGrade" toolbar = nuke....

7:39 PM

The Foundry Un-Rolls Your Shutter for Nuke / AE

The Foundry Un-Rolls Your Shutter for Nuke / AE

Great info from Stu's blog It also has a very interesting video clip look of something that you can't always Un-Rolls Your Shutter o...

7:08 AM

Katana from SPI for Nuke

Thanks Kuan's info about Katana from SPI for Nuke <a href="http://www.fxguide.com/article570.html" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5408485832194601074" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiI_cZpsO3x3raKW49MNe6vkblEoUQ6YoDFVNDHZvBKIp1pDWlt11OYhmyH3qP46toPs-2iZXl0KiwX6POxfwiOUFhwi5LSAhaJTxZ4v5l58aGdD25X4QGr3JQs6VV5-s7iXQJmPQ9Dj854/s400/katana_3.jpg" style="cursor: pointer; width: 400px; height: 313px;" /></a> check out this: On the lighting side the package, while not writing shaders, does allow nodal based manipulation of the shaders and speaks to third party renderers such as Pixar's Renderman and Arnold. It started life as a 3D lighting package some five to six years ago, it takes assets (geometry) "assigns materials, textures, - gets the lighting rigs set up - it is the primary 3D lighting interface that all of our lighting people use" Bredow explains. The system is node based, like Nuke but covering lighting in addition to compositing. On the compositing side it has all the main compositing tools, color correction, roto, paint, keying, camera mapping and stereo compositing & manipulation etc. "Our previous compositor was Bonsai, and that was developed over a number of years, it had very sophisticated keying, roto tools, etc.. Katana took all those tools in as a starting point and then we built on top of it, so Katana has pretty sophisticated fully featured tools in there". adds Bredow. wow...

Katana from SPI for Nuke

Thanks Kuan's info about Katana from SPI for Nuke check out this: On the lighting side the package, while not writing shaders, does allo...

10:46 AM

EXR layer naming conventions

<pre>http://www.mail-archive.com/openexr-user@nongnu.org/msg00178.html R G B A Z Raw Colour: Raw.R .G .B Reflection Colour: Refl.R .G .B Diffuse Colour: Diff.R .G .B Specular Colour: Spec.R .G .B Backdrop Colour: Backdrop.R .G .B PreEffect Colour: PreEffect.R .G .B Single channels: Special, Luminosity, Diffuse, Specularity, Reflectivity, Transparency, Shading, Shadow, Geometry, DiffShade, SpecShade Motion.X .Y <tt>the channel names should all be single-letters, </tt><tt>Are there cases where you reed to put more letters? That </tt><tt>would make it easier for people to make layers like "guy.head.spec.R" </tt><tt>and you know that everything before is part of the layer name and the </tt><tt>"R" is the channel. </tt><tt>And also, I think that is you have multiple channels that are tied </tt><tt>together, they should always use the layer format, like Motion.X and </tt><tt>Motion.Y. I see some files that just say "X" or "Y" or "VX" or </tt><tt>"velX" and there's no good algorithmic way to know they're tied </tt><tt>together. ----------------------------------------------------------------------------- </tt>Channel Names An OpenEXR image can have any number of channels with arbitrary names. The specialized RGBA image interface assumes that channels with the names "R", "G", "B" and "A" mean red, green, blue and alpha. No predefined meaning has been assigned to any other channels. However, for a few channel names we recommend the interpretations given in the table below. We expect this table to grow over time as users employ OpenEXR for data such as shadow maps, motion-vector fields or images with more than three color channels. name interpretation ---- -------------- Y luminance, used either alone, for gray-scale images, or in combination with RY and BY for color images. RY, BY chroma for luminance/chroma images, see above. AR, AG, AB red, green and blue alpha/opacity, for colored mattes (required to composite images of objects like colored glass correctly). ------------- A few thoughts on extending this: - I think "Z" for camera depth should be added to the recommendation list. This is a de facto standard in many (if not most?) apps already. - I agree with the other comments that "<layer>.<channel>" is the best way to go for all other channels, so that associated channels can be easily matched by layer. - Layer names should be mostly unrestricted, but there should probably be a recommendation for nesting within layer names, for example using dots or underscores (e.g. layer.sublayer.channel). This could support things like stereo images each with multiple layers. (For what it's worth, Nuke uses "<layer>.<channel>" for all channel names, but it doesn't allow dots in the "<layer>" part.) - For consistency, "<channel>" should, if possible, be chosen from the list of main channels: R/G/B/A/Z/Y/RY/BY. This works for layers that represent colors. Writers should be strict about using the recommended channel suffixes, but readers should recognize other reasonable versions, like r/g/b/a, red/green/blue/alpha, etc.. - What about scalar (single value) layers or layers that represent 3D data like points/normals/vectors? Some apps currently use x/y/z as channel suffixes, e.g. N.x, N.y, and N.z for normals. At least one uses nx, ny, and nz with no suffix. For scalars, most apps I've looked at just output the layer name without a channel suffix, e.g. "myscalar". It would be nice to have a unified, deterministic rule to handle all of these cases without requiring complex logic or lists of legal suffixes. What about using simple numerical indices for all data (non-color) channels? The layer name should be enough for apps to interpret the individual channels. Scalars could be the same, but with just a single index. For example: N.0, N.1, N.2, myscalar.0. This idea could also handle layers holding a 4-point vector or 16-element matrix at each pixel. Thoughts? There might be a better approach than numerical indices for data channels, but I can't think of anything else simple and flexible, at least not without having a system to declare file-specific channel suffixes in a "channel suffix declarations" attribute, or something like that. That would be an interesting idea to explore, but I think we need to be practical. Anything more than a simple naming convention is unlikely to be incorporated by application developers any time soon. <tt> </tt></channel></layer></channel></layer></channel></layer></pre>

EXR layer naming conventions

http://www.mail-archive.com/openexr-user@nongnu.org/msg00178.html R G B A Z Raw Colour: Raw.R .G .B Reflection Colour: Refl.R .G .B Diffuse ...

6:45 AM

prolost