X:X Conditional Trigs: A Pattern Cueing Saga

Sorry in advance, this is a longer one, and it may have been asked somewhere before, but it’s fairly convoluted so I’ve been unable to find anything…

I’m working on a project that requires various combinations of Track Length and Track Scale, with numerous Conditional Locks (Pattern CH.LEN is set to 16. M.LEN to INF).

There is a “Master” Track (drums) of 64/64 steps at 1x scale.

Now, this works finely and dandily if I let the whole pattern run to the end, and then cue the next pattern right at the end of the current pattern.

However, I’d like to be able to cue different patterns whenever I like. As I mentioned, the CH.LEN is set to 16 so the behaviour should be 100% predictable based on the 64/64, 1x Scale drum track.

Blurb aside, the issue is this:
Various melodies rely on conditional trigs (1:2, 2:2). When I cue another pattern before it gets right to the end, any 2:2 trigs present in the next pattern play the FIRST time.

In this video, there are two different starting notes for the melody 1:2 or 2:2 conditional locks (beginning of the bar = trig 1 / trig 2 with micro-timing).
The 2:2 note is intentionally loud and dissonant for the sake of this demonstration.

The patterns I’m switching between are identical, and their full lengths are much longer. They are being cued and changing following the 16 steps set in CH.LEN and the 64/64, 1x Scale drum track.

You can see here, as I mentioned, running one pattern then cueing another causes the 2:2 trig to play the first time the next pattern runs.
From this point it’s impossible to get back to the 1:2 trig without letting the whole Pattern/Track run to its conclusion. But obviously because of this behaviour, all of the various Tracks with their various Conditional locks are all over the place.

I’m finding it very difficult to comprehend the logic of this behaviour; surely when you change to a new pattern, everything should start from 0 and the 1:x trigs should play.

Any help before I cry would be much appreciated.

Cheers.

Yes, of course. If it doesn’t then it’s clearly a bug. Are you running the latest firmware version?

2 Likes

Thank you. New firmware fixed it.

Feel a bit silly now.

Cheers.

1 Like