<p>Hi Jeroen,</p>
<p>Ah yes, IMO group node is better for link/append.</p>
<p>Aditia A. Pratama - Kampoong Monster Studios<br>
<a href="http://www.kampoongmonster.com">www.kampoongmonster.com</a></p>
<div class="gmail_quote">On Jul 5, 2014 3:53 PM, &quot;Jeroen Bakker&quot; &lt;<a href="mailto:j.bakker@atmind.nl">j.bakker@atmind.nl</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    <div>Hi Aditia, <br>
      <br>
      Technical it can be implemented, but it will effect current
      developed scripts so it should be planned carefully. Linking does
      seems to be a step to far as the input nodes will be connected
      from the original file and rendering will not happen. Therefore
      group nodes seems to be a better solution.<br>
      <br>
      Jeroen<br>
      <br>
      On 07/03/2014 12:24 AM, Aditia A. Pratama wrote:<br>
    </div>
    <blockquote type="cite">
      <p>Hi Jeroen,</p>
      <p>Is it possible to have multiple compositing tree? but we have
        ability to choose which one to use for current scene. IMO The
        benefit of having &#39;slots&#39; nodetree as material/texture is the
        capabilities to transfer (linking/append) compositing nodetree
        to another blendfile, even we can do this with group node.</p>
      <p>And for enable/disable compositing in the pipeline, I think the
        one in render panel is enough, as sequencer does.</p>
      <p>Regards. </p>
      <p>Aditia A. Pratama - Kampoong Monster Studios<br>
        <a href="http://www.kampoongmonster.com" target="_blank">www.kampoongmonster.com</a></p>
      <div class="gmail_quote">On Jul 3, 2014 1:32 AM, &quot;Jeroen Bakker&quot;
        &lt;<a href="mailto:j.bakker@atmind.nl" target="_blank">j.bakker@atmind.nl</a>&gt;
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          Hi all,<br>
          <br>
          It is also a bit of legacy. First time clicking on use nodes
          will create<br>
          an initial composite node setup. It is because the other node
          tree types<br>
          (material/texture) can have multiple trees, but there is only
          one<br>
          composite tree per scene. The button is the same as the &#39;+&#39;
          button on<br>
          the other node trees types. The &quot;Compositing&quot; setting is
          introduced to<br>
          disable/enable the compositing step in the pipeline.<br>
          <br>
          Jeroen<br>
          <br>
          On 06/28/2014 12:10 AM, Diego Gangl wrote:<br>
          &gt; Besides what Pablo said, It&#39;s useful to stop Blender from
          compositing.<br>
          &gt; Sometimes, if you have a large network (or a huge
          resolution)<br>
          &gt; compositing can take a lot of time and resources, and the
          entire<br>
          &gt; network is recalculated every time you change a value.
          You can use the<br>
          &gt; button to &quot;pause&quot; it while you tweak some values/nodes,
          and then bring<br>
          &gt; it back.<br>
          &gt;<br>
          &gt; Cheers,<br>
          &gt;<br>
          &gt; 2014-06-27 18:57 GMT-03:00 Pablo Vazquez &lt;<a href="mailto:venomgfx@gmail.com" target="_blank">venomgfx@gmail.com</a>&gt;:<br>
          &gt;&gt; It is useful to render without compositing sometimes,
          but for that purpose<br>
          &gt;&gt; we also have the &quot;Compositing&quot; button in Post
          Processing under Render<br>
          &gt;&gt; properties.<br>
          &gt;&gt;<br>
          &gt;&gt; In fact, as far as I know they two do the same thing,
          if this is the case we<br>
          &gt;&gt; could get rid of the &quot;Use Nodes&quot; option and just use
          the &quot;Compositing&quot;<br>
          &gt;&gt; setting on Render properties. Assuming that when
          Compositing is enabled,<br>
          &gt;&gt; then Use Nodes will happen too. But perhaps a dev
          will be able to enlighten<br>
          &gt;&gt; us?<br>
          &gt;&gt;<br>
          &gt;&gt;<br>
          &gt;&gt; --<br>
          &gt;&gt; Pablo Vazquez<br>
          &gt;&gt; CG Artist - Blender Foundation Certified Trainer<br>
          &gt;&gt; Twitter: @PabloVazquez_<br>
          &gt;&gt; Blender Network: <a href="http://blendernetwork.org/pablovazquez" target="_blank">blendernetwork.org/pablovazquez</a><br>
          &gt;&gt; Email: <a href="mailto:contact@pablovazquez.org" target="_blank">contact@pablovazquez.org</a><br>
          &gt;&gt; Website: <a href="http://pablovazquez.org" target="_blank">pablovazquez.org</a><br>
          &gt;&gt;<br>
          &gt;&gt;<br>
          &gt;&gt; On Fri, Jun 27, 2014 at 11:51 PM, Sean Kennedy &lt;<a href="mailto:mack_dadd2@hotmail.com" target="_blank">mack_dadd2@hotmail.com</a>&gt;<br>
          &gt;&gt; wrote:<br>
          &gt;&gt;&gt; When we switch over to the compositor, we always
          have to click the &quot;Use<br>
          &gt;&gt;&gt; nodes&quot; button. Why is that there? What good is
          the compositing node graph<br>
          &gt;&gt;&gt; WITHOUT using nodes? Shouldn&#39;t that just happen
          by default?<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; Perhaps it has something to do with the
          interactions with the 3d and other<br>
          &gt;&gt;&gt; parts of blender.<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; Just asking. :)<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; Sean<br>
          &gt;&gt;&gt;<br>
          &gt;&gt;&gt; _______________________________________________<br>
          &gt;&gt;&gt; Bf-compositor mailing list<br>
          &gt;&gt;&gt; <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
          &gt;&gt;&gt; <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
          &gt;&gt;&gt;<br>
          &gt;&gt;<br>
          &gt;&gt; _______________________________________________<br>
          &gt;&gt; Bf-compositor mailing list<br>
          &gt;&gt; <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
          &gt;&gt; <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
          &gt;&gt;<br>
          &gt; _______________________________________________<br>
          &gt; Bf-compositor mailing list<br>
          &gt; <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
          &gt; <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
          &gt;<br>
          <br>
          _______________________________________________<br>
          Bf-compositor mailing list<br>
          <a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a><br>
          <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Bf-compositor mailing list
<a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a>
</pre>
    </blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
Bf-compositor mailing list<br>
<a href="mailto:Bf-compositor@blender.org">Bf-compositor@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
<br></blockquote></div>