Hi. I have a very strange problem with my AR. I have a sequence of patterns where some tracks play at double speed, to allow me to do more precise p-locking. Then in some patterns I use the “not 1st” trig condition, so that when the pattern starts playing, it doesn’t play some triggers right away. Now this works pretty great when I just hit play - certain steps are triggered only after the first loop. When I play patterns that have 1x track speed, continuously, one after the other - also, works as expected. If however, in the first pattern I have a track that plays at 2x speed, after changing the pattern, the “not 1st” trig condition doesn’t work on that track in the next patter. Does anyone know, what might be the issue here? Are you aware of any possible workarounds?
Sadly, no. I bring only empathy.
I found a similar issue today (and found this thread whilst searching for similar issues). I have a pattern with a “1st” condition set, that’s being ignored. The trig plays every cycle of the pattern, rather than just on the first. I’ve deleted the trig and re-made it; I’ve changed the condition, and then set it back to “1st”. Neither solved the issue.
I probably have different track lengths, but I’m not using the scale multiplier.
Small update!
The track with the 1st condition trig that played more often than it should was set to have 32 steps. The Master Length was set to 16 (and also Chng set to 16). In this state, the condition wasn’t being honored. Tried both of these:
- setting the track’s length to 16, to match the Master Length
- setting Master Length and Chng to 32
Both of these fixed the issue: the trig only played the first time through the pattern.
It seems that having the track length longer than than the Master length, and having the master length at 16 triggers the bug.
This reminds me of the issues many people have with changing patterns when syncing Elektrons to one another. There’s bug around setting Master Length to 16 (or below, AIUI). Setting it longer (or in this case, also setting the track length to match 16) fixes it.
master length
Master length is only useful when you need to reset all the tracks own patterns at the same time.
But otherwise, I usually set it to INF and only set the pattern change (which sets the number of beats the sequence will keep playing to complete a number of bars once you’re interrupting it with a pattern change).
To me, change length should be the default over master length ![]()
Conceptually, I agree, and changing patterns manually works like this.
But neither changing patterns by programme change, or by chains work this way. Instead the Master Length is used to determine when the pattern will change. I think this is wrong. For some time the manuals for Four, Rytm, and possibly Octatrack, claimed that sync worked the same way as manual pattern change. The manuals may have been updated now, I’ve not checked. The manuals still wrongly imply Change Length is the value used in automated pattern change.
(Maybe Tonverk behaves differently? I don’t have that one.)