If longer tracks are muted the loop is shortened conceptually/functionally, although visually, on screen, it’s still playing the entire (longest track) loop…
Which means I get unexpected behavior when my longest track(s) are muted - Stop at End of Loop, Rec next track, Change Parts, etc, now get queued and happen at the end of the longest playing (audible) loop.
This doesn’t really make sense to me, is it intended to work like this? what is the rationale?
Visually following looking at the looper it doesn’t make sense either - it plays the entire loop, which shows the muted longest track going by, but now if I hit Stop End of Loop (on SuperSwitch) it doesn’t play until all the red measure lines line up (the obvious, visual Start/End of the loop), as one would expect?
In my workflow - for example - sometimes I would like to mute the longest track - usually the guitar rhythm for example, and play that manually, for different chord voicings, or chord substitutes. And sometimes, in that case, I want to queue a part transition, record another long harmony track, like bass, or Stop at the end of the harmony phrase, but when I hit those functions the loop doesn’t play (visually) through my loop - i.e. until all the red measure lines line up (the start/end of the loop - the muted longest track(s)) - but to the longest track audibly playing, before executing the action I want, which can be much much sooner - worst case a single measure.
This isn’t a problem, of course, if I coincidentally have another unmuted track similarly as long as the muted one that I’m playing manually, and therefore I only discovered this issue, embarrassingly during a live performance recently.