There seem to be a problem where the live looper doesn’t get updated with the numbers of bars for the currently playing pattern if you switch between patterns that have a different amount of bars.
If I’m recording a loop over a 4 bar pattern, then switch to another pattern which is 6 bars, the next time I’m recording now monitoring sound drops out after 4 bars leaving the last 2 silent. In both in the actual recording and input monitor while playing it in.
It seems to me that looper tracks are not looping “by themselves” but are rather re-triggered all at once at the beginning of a pattern. Maybe they are actually looped when the Division setting is in play but it doesn’t help really.
Anyway, this current implementation results in a half-hearted looper functionality.
There should simply be a way to define loop lengths independently and let the loops loop no matter how long a pattern is! Although it is definitely a challenge for the programmer, it’s also a very logical thing from the user’s perspective. Nothing fancy for the 2023 standards.
Please @bradholland give us another looper update!
looks like live looper is simply not a prio and we are out of luck. It also seems like there’s only a dozen of us who use it extensively
These are the cruelest words I’ve ever heard.
The looper has definately gotten a lot of love these last updates, but independent loop lengths etc would be great.
But for now just getting these looper bugs fixed that make it really scary to actually use the machine in a live situation would be good enough right now. Noise bursts and loosing timing when committing loops is the most important to me. It has improved a lot lately but losing timing can’t be happening even once when you play with a band in front of a crowd. The noise bursts can be brutal through a PA to…
Maybe it’s connected to the same problem they seem to have getting modwheel, pitchbend and CC working. Maybe it’s hard to have the looper work any other way when the whole machine is pattern and tick based but what do I know….
It’s that and the fact that 60-70% of live loops get buffer glitches for me which results in it being unusable. Last time I made something with my S2400 was probably June/July. I come back every now and then to see if reported bugs are present and they still are.
Brad mentioned yesterday that it will be a while before S2400 receives another update since the unit is stable now. Okay.
You get it that often still?
I’ve been reheasing for maybe 10 hours the last two days and had the commit glitches only a couple of times after the last update.
Hopefully they can at least fix the important things to make it usable in a loud PA without risking these noises before moving on to other development.