Step trigger

[m5tevens]

Either I'm doing something wrong, or this isn't working correctly. I have a GateSeq sending its trigger out to an IntervalSeq ... the IntervalSeq is set to cvSTP. I would assume the IntervalSeq would advance one step for every non-zero step of the GateSeq, however, the IntervalSeq is advancing with every step of the GateSeq, including the steps set to zero.


http://www.solipsist.org/modules.gif

http://www.solipsist.org/routing.gif

[jim]

Connect the "Gate Out" to the "Trigger In" of the CV Seq. The "Trigger Out" port generates a trigger for every gate step, thus causing the behavior you were seeing. I plan to rename it, but haven't decided what yet.

Best,
Jim

[PaulSC]

The "Trigger Out" port generates a trigger for every gate step, thus causing the behavior you were seeing. I plan to rename it, but haven't decided what yet.

"Stepping Out"?

j/k

[m5tevens]

Yup, that was it, thanks. Is the functionality of the trigger output to allow for chaining multiple modules and driving them all from one divide-down? I ask as I'm wondering if it also addresses order-of-execution stuff I'm going to run across when working with more complicated stacks than I am now ...

[jim]

On Mar 27, 2009, at 9:18 PM, m5tevens wrote:


> Yup, that was it, thanks. Is the functionality of the trigger output
> to allow for chaining multiple modules and driving them all from one
> divide-down? I ask as I'm wondering if it also addresses order-of-
> execution stuff I'm going to run across when working with more
> complicated stacks than I am now ...


Can you be more specific about "order-of-execution" ?

But yes, the idea is that the trigger allows other seqs or module
(envelope) to be 'syncd' to the gate seq.

Thanks,
Jim