Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
natron [2015/07/06 14:44]
slackermedia 		natron [2021/06/03 19:48] (current)
Line 1: Line 1:
-[[{arrowp.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​left:​0;​}muse|]] 
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}obs|]] 
  
 ====== Natron ====== ====== Natron ======
Line 63: Line 61:
 The install can happen in two different ways: The install can happen in two different ways:
  
-  * Run the installer as a normal user and install to a location in your home directory (for instance, ''​~/​bin/​natron''​) +  * Run the installer as a normal user and install to a location in your home directory (somewhere in ''​~/​bin''​ is customary; ​for instance, ''​~/​bin/​natron''​) 
-  * Run the installer from a terminal using the ''​kdesu''​ command and install to a systemwide location, (such as ''/​opt''​)+  * Run the installer from a terminal using the ''​kdesu''​ command and install to a systemwide location, (''/​opt'' ​is customary)
  
  
Line 163: Line 161:
 Slightly more advanced is the ubiquitous green screen effect. For this, you need sample footage. Sample footage abounds online, but much of what you find online is heavily compressed, which by definition discards information. For a clean green screen, the //less// compressed your footage, the better. Slightly more advanced is the ubiquitous green screen effect. For this, you need sample footage. Sample footage abounds online, but much of what you find online is heavily compressed, which by definition discards information. For a clean green screen, the //less// compressed your footage, the better.
  
-Download ​sample footage from [[http://blah|an online mirror]]+The Internet has quite a lot of sample greenscreen footage. If you cannot find any that suits, download ​sample footage from [[https://drive.google.com/​open?​id=0B_nYaI3DodmMdmZWSE9sbTRQbGs|this online mirror]].
  
   - Add a greenscreen shot with a **Read** node (''​r''​ on your keyboard, or a right-click anywhere in the **Node Graph** window).   - Add a greenscreen shot with a **Read** node (''​r''​ on your keyboard, or a right-click anywhere in the **Node Graph** window).
Line 178: Line 176:
 Once you have a good chroma key, you'll see it in your viewer. Once you have a good chroma key, you'll see it in your viewer.
  
-[[{ natron_chroma.jpg | A basic chroma key. }}]+[{{ natron_chroma.jpg | A basic chroma key. }}]
  
 To get a feel for how flexible Natron is, and how a little extra effort in compositing can render improved results, add a little style to the setup: To get a feel for how flexible Natron is, and how a little extra effort in compositing can render improved results, add a little style to the setup:
  
-Add a **Merge** node to the **Node Graph** window. +  - Add a **Merge** node to the **Node Graph** window. 
-Connect the output of the **ChromaKeyer** to the ''​A''​ side of the **Merge** node. +  ​- ​Connect the output of the **ChromaKeyer** to the ''​A''​ side of the **Merge** node. 
-Add an **Filters** → **BlurCImg1** node after your background image, and disconnect the background (or the blur) from the ChromaKeyer. By freeing the background from the chroma key process, you add flexibility to how you can process the output of the keyer. +  ​- ​Add an **Filters** → **BlurCImg1** node after your background image, and disconnect the background (or the blur) from the ChromaKeyer. By freeing the background from the chroma key process, you add flexibility to how you can process the output of the keyer. 
-Connect the blur node to the **B** side of the **Merge** node. +  ​- ​Connect the blur node to the **B** side of the **Merge** node. 
-Connect the **Merge** node to the **Viewer**. +  ​- ​Connect the **Merge** node to the **Viewer**. 
-In the **BlurCImg1** property panel, increase the blur amount until the background gets a "soft focus" look.+  ​- ​In the **BlurCImg1** property panel, increase the blur amount until the background gets a "soft focus" look.
  
 Now you have a scene with the suggestion of depth-of-field at best, or a de-emphasis on any clutter at worst. Now you have a scene with the suggestion of depth-of-field at best, or a de-emphasis on any clutter at worst.
  
-[[{ natron_blur.jpg?​666 | A basic chroma key with separate pipes for foreground and background. }}]+[{{ natron_blur.jpg?​666 | A basic chroma key with separate pipes for foreground and background. }}]
  
 In this example, the ballerina in the shot is still a little rough around the edges. There are several ways to deal with that issue, but in this case an artificial glow to suggest stage lighting is what the client is looking for. This is a good example of how output can be doubled up on itself to produce a unique effect. In this example, the ballerina in the shot is still a little rough around the edges. There are several ways to deal with that issue, but in this case an artificial glow to suggest stage lighting is what the client is looking for. This is a good example of how output can be doubled up on itself to produce a unique effect.
  
-Without removing any nodes or connections,​ click and drag to select **Read** and **Chromakeyer** nodes. Right-click on your selection and choose **Edit** → **Duplicate Nodes**. +  - Without removing any nodes or connections,​ click and drag to select **Read** and **Chromakeyer** nodes. Right-click on your selection and choose **Edit** → **Duplicate Nodes**. 
-Move the duplicated nodes to the side so you can work with them. +  ​- ​Move the duplicated nodes to the side so you can work with them. 
-Add a **Merge** → **Dissolve** node. +  ​- ​Add a **Merge** → **Dissolve** node. 
-Connect the new **Chromakeyer** output to the **Dissolve** node. +  ​- ​Connect the new **Chromakeyer** output to the **Dissolve** node. 
-Add a **Filter** → **Tuttle Blur** node and connect it to the **Dissolve** node. +  ​- ​Add a **Filter** → **Tuttle Blur** node and connect it to the **Dissolve** node. 
-Now disconnect the original **Chromakeyer** from the **Merge** node and re-connect it into your new **Dissolve** node. +  ​- ​Now disconnect the original **Chromakeyer** from the **Merge** node and re-connect it into your new **Dissolve** node. 
-Connect the **Dissolve** node to the **Merge** node. +  ​- ​Connect the **Dissolve** node to the **Merge** node. 
-In the **TuttleBlur** properties panel, increase the blur amount just enough so that an outer glow appears around the subject.+  ​- ​In the **TuttleBlur** properties panel, increase the blur amount just enough so that an outer glow appears around the subject.
  
-[[{ natron_green.jpg?​666 | Composites can get complex, and when they aren't frustrating,​ they'​re a lot of fun. }}]+[{{ natron_green.jpg?​666 | Composites can get complex, and when they aren't frustrating,​ they'​re a lot of fun. }}] 
 + 
 +Were this an actual deliverable shot, you would apply colour correction and probably an additional transform to position the subject, and so on. There are plenty of effects and nodes available to help a composite reach its best possible quality, and the best way to learn them is to experiment.
  
 The important lesson here is the segmentation technique; rather than hooking all nodes into a central **Merge** node, the script keeps individual effects in their own subroutines,​ which are then finally connected to a **Merge** just above the final viewer. That's not always how a composite will go, but it's important to keep in mind that few scripts are just three or four nodes, and fewer still are linear. The important lesson here is the segmentation technique; rather than hooking all nodes into a central **Merge** node, the script keeps individual effects in their own subroutines,​ which are then finally connected to a **Merge** just above the final viewer. That's not always how a composite will go, but it's important to keep in mind that few scripts are just three or four nodes, and fewer still are linear.
Line 217: Line 217:
 <WRAP tip> <WRAP tip>
 **See Also** \\ **See Also** \\
-Blender \\ +[[blender|Blender]] \\ 
-Synfig+[[synfig|Synfig]] 
 +</​WRAP>​ 
 + 
 +<WRAP centeralign>​ 
 +<wrap fa>​[[mypaint|R]]</​wrap>​ <wrap fa>​[[start|S]]</​wrap>​ <wrap fa>​[[non|Q]]</​wrap>​
 </​WRAP>​ </​WRAP>​
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}obs|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}muse|]]