[Sidefx-houdini-list] Bypass a Composite COP - what's intuitive?

Rangi Sutton rangi.sutton at gmail.com
Sun Aug 27 21:50:05 EDT 2006

Hoknamahn wrote:
> Both inputs of the Composite COP just a chains of operators. But which 
> chain is "main"? Especially if we remember that Composite COP have 
> different modes.
> Or maybe behaviour of the Composite COP should be dependent on mode? 
> Is it good idea? Maybe yes maybe no :)
> The things so simple now. No need to think what will be in the case if 
> I bypass the Composite COP. But maybe you right and we need to have 
> cool smart bypass :)
Nuke passes through the "B" input. So where an over is A over B and you 
bypass it you get B. B will usually be the main trunk of the comp, and A 
is the additional component. Works well for me. Halo I find myself doing 
temporary re-wires instead of by-passing...


> Peter Bowmar wrote:
>> Hmmm, interesting... To my mind, if you bypass a Composite you want to
>> remove the element the Composite brings in, which is the "top" one,
>> leaving the bottom. But that's just me :) No big deal, especially
>> after I learned about the "r" hotkey from Craig Zerouni's awesome
>> book!!
>> Cheers
>> ,
>> Peter B
>> On 27/08/06, Hoknamahn <hoknamahn at cgtalk.ru> wrote:
>>> Over or Layer in Shake have the same behaviour as the Composite COP.
>>> Peter Bowmar wrote:
>>> > Is it just me, or when a Composite node is bypassed, shouldn't it 
>>> pass
>>> > through the background not the foreground? What do other packages do?
>>> >
>>> > Cheers,
>>> >
>>> > Peter B 

More information about the Sidefx-houdini-list mailing list