MSuperLooper same-beat reaction?

[Burillo]

It seems that if i place a loop change trigger at the start of the loop, even if it's at the very loop, MSuperLooper will still wait until next loop to trigger the change. That means if i jump the transport to a place where i'm expected loop 1 to be playing, it will only actually start playing once it's gone around the loop one more time. It would have been better if, when loop change triggered at the start of the loop, MSuperLooper would change to it immediately.

[Dirk Diggler]

Sounds like there must be a default behavior, personally I like it to act this way.
It's like a bar quantize.
Check through your preferences, I bet it's there somewhere.

Sorry I've never had the need to change it, I'm sure someone else here will have the correct answer.
Good luck,
Dirk

[Burillo]

I did, i don't see any settings regarding this. Just to be clear: i still need the quantize, that's not the problem. What i also need is that if the transport jumps and lands on a loop switch, that switch should be triggered, not waited on.

[MeldaProduction]

My guess is that the DAW sends it a part sample too late. I'm not sure what you are trying to do really. This is designed for live looping, not arranging.

[Burillo]

My guess is that the DAW sends it a part sample too late. I'm not sure what you are trying to do really.

no other plugin (including, say, Enso, a fellow looper) has problems with this. it would be nice if you could investigate and possibly fix what causes it.

This is designed for live looping, not arranging.

it doesn't have to be one or the other - you can have a hybrid setup based on some kind of arrangement, but with live looping involved. please don't dictate how others should use your software.

[MeldaProduction]

Could you make a small project, which does that and send it to me via info@meldaproduction.com?