Section A - 160 steps 10 bars
Section B - 128 8 bars
Section C - 128 8 bars
The pattern lengths are the same as seen at the start of the video too.
I hit play and Section A is fine then moved into Section B but it looks like it starts at 5/16 which I think is step 5 of 16? Then in Section C is ok and starts at 1/16 but ends at 4/16.
i have encountered this behavior in Song mode as well, long before 2.10, and never could figure out an acceptable solution other than setting all Patterns to “restart” so that they all have a hard reset with each section change. but then if you did want some or all of the Patterns to run “free” across any of the Sections (in my experience) the time jump comes back into play when the Section change occurs
This behavior is expected, this is the purpose of the TRIG = FREE option :
TR2 PATTERN 6 is 160 Steps
TR2 PATTERN 7 is 128 Steps
They are both FREE running, so they are drifting apart from each other at each loop, until they are back to sync after 10x8 bars (Yes it will take a while!)
Here is what is happening in your case :
When PTRN 6 is reaching step 128/160, PTRN 7 restarts because it is 128 steps long (it is looping back to its beginning)
PTRN 6 continues to play, and it eventually reaches step 160. At this point, as PTRN 7 is FREE running, it is playing step 32 already.
At this moment, the PTRN switch happens, and PTRN 7 is played from step 32, which is expected.
If you want PTRN 7 to start at step 0, you simply have to set it to TRIG = RE-START.
@Gonzo told me that this solved it for him, @chrisroland do you have a scenario in which this is not the solution?
i just moved on to Deluge for the linear arranger a while ago so i haven’t really tried to sort it out in Hapax. but my recollection is that wasn’t my precise problem. it was when i had several other much shorter Patterns (4-bar, 8-bar, maybe 16-bar at most) looping repeatedly in, say a 128-step Section. the lone onger, free-running pattern (say 132 steps) that I needed to not reset across two different Sections was the one that kept jumping to the middle when a Section change occurred. if that’s also expected behavior i’ll take your word for it . . .
Well, pretty hard to say without the project, but a lot of issues have been solved in the last OS, so it might have been a soft issue, or a wrong setting.
Anyway, if you circle back on this, feel free to drop a line!
Cheers,
Tom