Accumulate, Metropolix style?

[mgd]

- the initial setting of the tables is executed twice, i.e. it seems the first SPFX 011 initializes all position pointer (or however you call them) to 0 and thus results in table position 0 being executed twice.

As with clocking in general, a step is executed when a tick/clock is happening. With the table you use, there is no clock in the first place but the first clock comes on step 14 which is then also the first execute. They are also fine here.

Hmm.

I did the following tests:
I moved the SPFX 011 in the pattern from 0E to 0B (while 02 is still active).
Now playing gives me the untransposed line twice before transposition starts.

I then changed the tables 01 and 02 as of my project such that line 00 (no transpose) was removed and played it.
It now plays the first transposition line twice and then moves on.

That seems at least unwanted. When initially the effective table position is 0 then applying SPFX 011 should move this on forward instead of initializing it to 0 (that's what it seems to me right now).

As an afterthought:
What triggers the execution of a HP?
Let's say there is a HP 00 on step 03 of the table. Is it executed upon executing/playing step 03 or is it executed when that table is active and plays step 02 and then a SPFX 011 happens?
Or phrased differently:
Is HP executed when the position pointer of the active table is moved and the new step of that table contains a HP?

What happens when there are RND HP on each step?
Is at most one HP performed per tick/clock or could I create an infinite loop?

Kind regards,
Michael

PS: I'm not trying to be PITA. I'm honestly interested in understanding how these things work