Track 1 seq reset affects other tracks?

I don’t know if this is a bug or my own error. I have a situation where changing seq reset on Track 1 apparently affects the seq reset on Track 2 and Track 3. Perhaps I’m confused and have lost track of something, so I’d like @ward to take a look. I’ve made a video here:

[DELETED]

In case the video isn’t clear enough, I’ll also describe what I do in the video:

I’ve got synths on Track 1 and Track 2 and quad engine on Track 3, so the three different timbres are easy to distinguish when the seq reset value changes. In the video, I first give you a look at each track, then I go back to Track 1 and wiggle the seq reset knob. You can clearly hear the drums on Track 3 speed up, and you can hear the synth on Track 2 speed up if you listen closely. Then I switch the screen to Track 2 and Track 3 to show that their seq reset values haven’t changed, but you can clearly see each track’s higher density of pulses.

Why do Track 2 and Track 3 pulses become denser when I change Track 1’s seq reset? Meanwhile, if I change Track 2’s or Track 3’s seq reset, they operate entirely independently of the other tracks. Can you explain what’s going on?

I think this can be explained by the recently implemented reset by (in [edit]+[track]) function. It has been in track settings for quite some time now but only really worked since last update.

With the reset by setting you can have a tracks sequencer reset when another tracks sequencer resets. By default they should all be set to none so seq resets do not affect other tracks. Can you check if the issue persists when all reset by parameters are set to none?

1 Like

Yes, this was the cause.

I also see you’ve also implemented the shift++# option–thanks.

1 Like