2009年1月19日 星期一
2009年1月17日 星期六
2009年1月16日 星期五
2009年1月13日 星期二
Nuke Tips: Customer build Nuke LUT profile for viwer
First of all, big thanks Matt from Foundry to this>>
Nuke's default LUT for monitor and viewer is sRGB, if you want to set LUT to gamma 2.2 like Shake linear comp workflow.
1: Go to Nuke Root setting, pick LUT and create a new LUT profile and you might name it ex: "gamma 2.2" .
2: right click on the new curve> Edit> Edit Expression>
3: type pow (x, 2.2)
4: then set viewer/ monitor to new LUT profile to gamma 2.2
Nuke's default LUT for monitor and viewer is sRGB, if you want to set LUT to gamma 2.2 like Shake linear comp workflow.
1: Go to Nuke Root setting, pick LUT and create a new LUT profile and you might name it ex: "gamma 2.2" .
2: right click on the new curve> Edit> Edit Expression>
3: type pow (x, 2.2)
4: then set viewer/ monitor to new LUT profile to gamma 2.2
2009年1月12日 星期一
2009年1月9日 星期五
2009年1月5日 星期一
Node Graph Shortcut in Nuke
swap the A and B inputs of a merge node by pressing Shift+X
Merge node's mix control affect the A input channel
Merge node's mix control affect the A input channel
2009年1月4日 星期日
Viewer in Nuke
You can also press the ; (semicolon) and ‘ (forward single quote) keys to move between different
views in the Viewer.
views in the Viewer.
Read Node and Colorspace in Nuke
Nuke reads images from their native format, but the Read node outputs the result using a linear colour space. If necessary, you can change the Colourspace option in the Read node’s properties panel, or insert a Color > Colorspace node to select the colour scheme you want to output or calculate.
QuickTime .mov files may appear different in Nuke relative to Apple’s Final Cut Pro, because Final Cut Pro introduces a gamma compensation based on assumptions about the content of the files and the viewing environment.
If you are using 64-bit Windows, you cannot read QuickTime files into Nuke. This is because Apple has not released QuickTime for 64-bit Windows.
The file names of image sequences generally end in a number before the extension, for example image0001.rgb, image0002.rgb, image0003.rgb, and so on. When browsing for files like this, you may notice that the sequence appears as image%04d.rgb. Here, %04d is Nuke’s way of indicating that the number is in a 4-digit incremental format. For a 3-digit format, such as image001.rgb, the frame number variable would be %03d. Nuke’s File Browser also understands unpadded file names, such as image1.rgb, image2.rgb, image3.rgb, and so on. They appear as image%d.rgb.
You can also use #### instead of %04d, ### instead of %03d, ## instead of %02d, and so on.
QuickTime .mov files may appear different in Nuke relative to Apple’s Final Cut Pro, because Final Cut Pro introduces a gamma compensation based on assumptions about the content of the files and the viewing environment.
If you are using 64-bit Windows, you cannot read QuickTime files into Nuke. This is because Apple has not released QuickTime for 64-bit Windows.
The file names of image sequences generally end in a number before the extension, for example image0001.rgb, image0002.rgb, image0003.rgb, and so on. When browsing for files like this, you may notice that the sequence appears as image%04d.rgb. Here, %04d is Nuke’s way of indicating that the number is in a 4-digit incremental format. For a 3-digit format, such as image001.rgb, the frame number variable would be %03d. Nuke’s File Browser also understands unpadded file names, such as image1.rgb, image2.rgb, image3.rgb, and so on. They appear as image%d.rgb.
You can also use #### instead of %04d, ### instead of %03d, ## instead of %02d, and so on.
訂閱：
文章 (Atom)
