gistfile1.txt

Port publishing:
 
 There are 2 situations where this is useful:
 1. Publish to parent (from in a macro)
 2. Publish to root from deep in a nest of macros. This 
 gets painful fast if you have to publish from each layer.
 
 Time:
 
 QC has a really useful timebase system for any time-based 
 nodes (e.g. LFOs, timelines etc.):
 
 - All nodes get the global time by default, but you can 
 change it on time-based nodes
 - You can switch to "local" time. This works by having a 
 seperate timebase for a macro. The time becomes an input 
 on the macro.
 - You can also have per-node time, again time becomes an 
 input.
 
 Seperating out time is useful because:
 
 - You can easily loop animations, just feed the time input 
 through mod(time, duration)
 - Slow down/speed up/go backwards for specific objects
 - Basically time becomes another variable you can do what 
 you want with, but only where you need it as a variable
 - Time * BPM = instant easy sync, 1 second = 1 beat
 
 -- edit --
 
Forgot about this. There was a QC plugin, I forget the name,
'ghost patch' or something. It had 2 nodes, 1 with an input 
only, the other with an output only. You connect an input to 
the first one, then wherever you need that value you put the 
output node. It just connects the two, but without noodles. 

With multiple inputs, naming (named pipes?), and 1 input 
multiple outputs, this gets useful fast, and cuts down on 
the spaghetti pile you inevitably end up with.