Table sequencer question...

I've noticed that when I reset the clock, most event sequencers move to the first step, insteat of before it, so when the sequence is started again, the first step is missed. Am I doing something wrong, or is this a problem others have had? Any fixes?

jpb

 

try this algorithm

for start: set to 0 and transmit,
for step > loop length-- set to -1,
and the next pulse that goes to the "up" of counter moves it
to 0:

trigger(midiplay,gate,button,etc)>input of macro:

in_of_macro> val1.in
val1.val=0
val1.out>counter.set
counter.out>separator.in
separator.thresh = loop_length
separator.lo>order.in
separator.hi>val2.in
val2.val=0
val2.out>counter.up
order.1>output_of_macro
order.2>val3.in
val3.val=1
val3.out>counter.set

this way the start and loop start always set to 0, and there's
no double triggering (because of separator)

also, you may want midi play(i.e. start) to open a router
hooked up to a sync, instead of triggering the counter itself,
since a clock will be what should be hooked up to the in of the above
macro (receiving clock pulses--each one ++'s the counter)--so it's
1 trigger for start (instead of start, and then pulse "0")-- you just
want the pulses (i think)


good luck

hmmm, i wonder if the above is a sufficient enough language to describe a structure. if it is, then it wouldn't be hard to make
a structure script, that you could apply text editing tools to (like
perl) so you could execute repetitive tasks very fast--
imagine that, editing a reaktor ensemble in emacs on a linux box
while you're at work--and then you come home with a phat ensemble...
but that's neither here nor there