@Antoine - sounds great, glad you like it!
Have you tried to change the autoloop length fitting method configurable on the CONFIG screen?
Quote from the handbook:
Configure the desired autoloop length fitting method from the CONFIG screen. For
example, an available length fitting method is “loop blocks”, which creates clip lengths
based on a geometric progression of two beats (4, 8, 16, 32 sixteenth notes in 4/4 time
scale). The default setting is simply “any number of integer measures”, which works well
for most recordings.
If that does not help, i suggest to try out the following two alternatives to full autoloop recording with the sequencer engine stopped:
a) pre-set the clip to the length you want to record (i.e. 2 bars), start the sequencer, just ARM LoopA with the ARM button and record the clip to its length. You can potentially use a footswitch to jump the recording cursor just ahead of the clip start (“JumpToPrecount”). You can use the secondary footswitch to “punch in” notes on secondary recording loops, if there were some (e.g. timing) issues with a previous loop. Like this you should be easily able to record in the exact length required.
b) use autoloop recording, but start it when the sequencer is already running. Like this you’ll get tempo-matching to your existing session and get a precise count-out (possible stop in X steps) to match the recorded clip lengths to measures - like this it should also be easy to record a clip of a predetermined length.
Autoloop mode with the sequencer engine stopped will just try its best to match what it thinks you wanted to do - but there can be a difference between what the user wants and what the machine thinks the user wants 🙂. For me it works nicely when recording one-bar and two-bar clips, but your mileage may vary. For me, the best method for predictable recordings is to pre-set the clip length and record with the original ARM mode (not autoloop) - see option a) above.
Best regards, Peter
