Recording and loop problems
Recording will not start
Check:- you are in the
Createtab - the loops row is focused
- the correct slot is selected
- your input or playback setup is not in a broken state
The first loop feels wrong
Remember that the first meaningful loop establishes session timing. If that first loop is sloppy or unintended, later loops will inherit the wrong foundation. Best fix:- clear the bad first loop
- record the timing source again cleanly
- use First Loop Setup in Fixed mode when you want
90.00 BPM, QuantizeOFF, a4 BEATScount-in, aREC + PLAYclick, and a loop that keeps the selected Length even if you press[ENTER]before the automatic stop; early commits queue asOVR+until the fixed interval arrives - if the first beat is blank after a count-in, remember that the final count-in beat advances hits to
0:00, including slightly early hits near that beat; play there or after REC starts when you want a top-of-loop event - switch First Loop Setup to
Mode: AUTO TEMPOonly when you want the completed take to define the tempo by its ending; Auto keeps Length flexible while still applying the dialog’s Quantize, Count-in, and Click choices, then continues directly into overdub
Overdub made the loop worse
Use the smallest rollback possible:- undo the last loop edit
- clear the affected track if available
- re-record the overdub only
Loop length feels wrong
Check whether the issue is:- bad take timing
- wrong loop close point
- quantization mismatch
- a loop that should have been extended or duplicated instead
Quantize made it feel stiff
Use less correction, or leave more of the original timing intact. Quantization should improve the groove, not erase it.The project is playing too fast or too slow
OpenSettings → Tempo, then set the BPM you actually want. This retimes loop playback and synced material while keeping pitch unchanged.
If first-loop detection keeps choosing the double-time or half-time BPM, set Range before recording the first loop. The default 65-135 range turns a detected 171.45 BPM first loop into 85.73 BPM; None disables this automatic correction.
Tempo is unavailable in Settings
The project tempo editor requires at least one recorded loop to establish a timing source. Record a loop first, then openSettings → Tempo.