Frequently asked questions

Two common causes: the sample was recorded/exported quiet, or you're hearing it through a bus FX that drops level. Normalize the sample before import (or use the on-board normalize), check the pad's volume/velocity, and make sure you aren't routing through a gain-reducing effect on BUS 1/2. Gain-staging on the SP is the single most common "why is it quiet" issue.

More than people assume. The MkII works internally at 16‑bit / 48 kHz and auto-converts on import, accepting 16‑ or 24‑bit WAV at common rates (16k through 96k+), so you usually don't need to pre-convert. One nuance: format support is broader through the SP‑404MKII App than through direct SD‑card import — SD import is fussier, so if a file won't load straight from the card, try importing it through the app. When a sample "won't import," it's more often a corrupt/odd header, an unsupported container, naming, or length than the sample rate. A batch converter like SP404WavConvertor is a convenience for cleaning up odd files, not a requirement.

Two routes. The official SP‑404MKII App (over USB) is the easy way to import and manage samples/projects. You can also import from the SD card using the device's import function. The app is convenient, not mandatory — many people prefer SD import for bulk libraries.

Skip Back continuously buffers what just played so you can grab the last several seconds after the fact — press the Skip Back pad to capture a moment you didn't plan to record. Great for catching happy accidents from live jams or resampling a phrase you just performed.

Lean on the SP's lo‑fi character: resample through the Vinyl Sim / Cassette / SX bit-reduction effects, drop sample rate, and chain effects via the bus. The "Timbaland/ASR" vibe is mostly aggressive resampling + the right grit effect printed to the sample, then chopped.

Pads route to buses; effects sit on the bus or the main out. To print an effect, resample the bus output to a new pad. Confusion usually comes from expecting per-pad insert effects — instead, assign the FX to the bus the pads feed, then resample to commit.

Yes — the pattern sequencer records pad hits with quantize options and supports pattern chaining for longer arrangements. Set the BPM/length first; remember pattern length and sub-step resolution interact, so a "too short" loop usually means the bar length wasn't extended.

DJ mode turns the unit into a performance/looper setup with crossfading between sources; pad mutes let you drop parts in/out during a pattern. Many performers build a project of looped stems + one-shots and use mutes + bus FX live rather than the step sequencer.

The friction is real (format prep, bus routing, no per-pad inserts) but it's also why the workflow forces commitment and a recognizable sound. Most owners say the constraints are the point — once import + resampling click, it's fast. If you want a frictionless sampler, the SP isn't it.

Use separate projects per song/set and back up the whole SD card before firmware updates. Keep a clean import library on your computer (44.1/16 WAVs, named) and treat the device as the performance copy. Don't hand-edit the device's project folders on the SD card — let the app manage them to avoid corruption.

Trim the sample to exact bar boundaries and at zero-crossings so the end meets the start cleanly, set the pad to loop/gate mode, and make sure the sample's BPM/length matches the project tempo so the loop length is a whole number of bars. Clicks usually mean the loop points aren't on zero-crossings; a gap usually means the sample is slightly longer/shorter than the bar. Resampling the loop once at the project BPM locks it in.

The MkII sends and receives MIDI clock over USB and the MIDI jacks. In the MIDI/sync settings pick whether the SP is the clock master (it sends clock to your other gear) or slave (it follows incoming clock), match the project BPM, and set patterns to a whole number of bars so loops stay locked. If loops drift, something else is also sending clock, or the pattern length isn't an even bar count.

The effect algorithm is identical either way; the difference is destructive vs not. FX-only runs the audio through the bus effects live (non-destructive, but it uses the bus and you can't stack beyond the available FX). Resampling prints the effect into a new sample — it commits the sound (great for lo‑fi/bit-reduction character), frees the bus to add more processing, and lets you chop the processed result. Watch gain-staging when you resample so you don't clip or lose level.

Reorganize through the SP‑404MKII App / the device, not by hand-moving files in the SD card's folders. The SP references each pad's sample by its place in the project/import structure, so the app keeps those links intact when you move things around — but manually renaming or relocating files in the card's folders outside the app breaks the project→sample linkage and you'll get silent pads. Back up the card before any big reorganization.

Resample or import the break to a pad, then slice it: set the pad's start point (and the next pad's start a transient later) so consecutive pads play successive hits, or use the BPM/Mark so the loop plays in time and you re-trigger sections live. Many people resample the whole break at the project BPM first, then spread slices across a bank and re-sequence the hits. Roll/gate and the sub-pad tricks add the stutter feel.

Because the effect tail is tied to the pad's voice — re-triggering chokes it. Put the time-based FX on a bus (BUS 1/2) and let the pads feed that bus, so the tail rings out independently of the pad re-triggering; or print (resample) the tail into the sample. Per-pad/insert-style effects will keep cutting; bus FX is what sustains reverb/delay across hits.

The MkII is a class-compliant USB audio interface, so set it as an input/output device in your DAW and route a track to/from it (with an aggregate device on macOS if you also use another interface like a MOTU). For sending audio into the SP to resample, select the SP's USB input as the SP's recording source; to record the SP into the DAW, arm a track on the SP's USB output channels.

Decide who's the clock master. To make the SP follow external gear, set it to receive MIDI clock (SYSTEM ▸ MIDI ▸ Sync to an external/slave mode) and make sure the source is actually transmitting clock. To make the SP drive other gear, set it to send clock (master). Then check the physical link — USB-MIDI or the TRS MIDI adapter on the right TRS type (A vs B) — and that both ends agree on master/slave. Two masters, or none, is the usual reason the tempo won't lock.