Skip to main content

​
Recording and loop problems

​
Recording will not start

Check:
  • you are in the Create tab
  • the loops row is focused
  • the correct slot is selected
  • your input or playback setup is not in a broken state
  • if an existing loop is playing and the selected slot is empty, press [R] to put that blank slot in OVR+ and schedule it for the next loop iteration
OVR+ is a wait for the next project-loop downbeat, not a new four-beat count-in. The toast starts counting on the next existing beat and displays only the beats left in this iteration. Pad, chop, and MIDI hits during the wait remain audible but do not enter the take. Keep at least one loop playing; stopping playback, cancelling with [R] or [ESC], or starting another overdub cancels the wait rather than starting an unaligned recording.

​
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, Quantize OFF, a 4 BEATS count-in, a REC + PLAY click, and a loop that keeps the selected Length even if you press [ENTER] before the automatic stop; early commits queue as OVR+ 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 TEMPO only 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

Open Settings → 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 open Settings → Tempo.

​
Input capture overflowed or failed

Input capture overflowed; recording discarded means incoming audio exceeded the bounded capture transfer. The incomplete take returns to Idle and cannot be kept. Re-arm for a fresh take after resolving the load or input problem. Input stream failed requires selecting the input device again. A capture stop timeout also discards the incomplete take. If saving from Review fails, the valid samples remain in Review so you can retry after fixing storage.

​
MPC Sample SHIFT controls do not select a pad

SHIFT+pad invokes the printed function outside Chop. Use [DATA] for silent selection. EDIT opens trim bounds or Sync Stretch without claiming committed cropping or stock WARP. Native Time Correct stages until [B3] applies; [B1] cancels. REC QUANTIZE changes new recorded hits only and cannot recover the raw off-grid performance.

​
Bounce reports overflow or a flush timeout

The capture was incomplete and is not exported. Existing project assets remain intact. Start a new bounce after resolving the load or audio-device problem. Channel-file write failures can leave successfully written tracks; failed partial files are removed and the bounce is not announced as complete. See bounce failure and retry.

​
Resample did not assign a pad

Select an empty destination pad, play the selected source sequence or scene, and retry [CTRL+SHIFT+R] or native [SHIFT+PAD 11]. Finish or cancel armed takes first. Resample requires a live output and matching transport/output sample rates. A missed scheduled boundary, queue overflow, incomplete span, timeout, write or decode error discards the capture. Keep the output running, reduce system load, and retry. Cancellation and project/target changes discard even a late completed result. Wait for the cancellation screen to close before starting another capture. The original pads and files remain intact; no truncated WAV is assigned.

​
Song will not flatten

Select an empty destination sequence before opening SONG. Every referenced scene must contain recorded sequences. Remove empty references or reduce repeats/order if duration or the one-million-event limit is exceeded. Songs terminate explicitly; legacy scene next/stop links do not create recursive song chains. If whole-sample canonical timing cannot represent a retimed offset exactly, restore the original project tempo and retry. No destination content changes on rejection.