Frequently asked questions

Ask for a video powering on, every pad triggering (pressure-sensitive, no dead/weak pads), the encoders/screen working, and that it boots to the current OS without errors. Confirm the storage (internal SSD/SD) is healthy and there are no account-locked expansions. Pad sensitivity wear and screen/encoder issues are the main used-unit problems.

Standalone runs the MPC OS on the hardware with no computer. Controller mode connects to the MPC software on a computer for more CPU, plugins, and audio tracks. Many features (third-party plugins, and higher, host-dependent audio-track/plugin capacity) only exist in software/controller mode, while standalone has fixed per-model limits — a huge share of "why can't I do X" is "X is software-only."

USB host limitations apply — the MPC's USB ports are particular about class-compliant devices and you generally can't freely chain an interface + iPad + everything. Check the model's supported-class-compliant-device behavior; a powered USB hub helps for some combos, but expect constraints vs a computer.

Expansions install via the MPC software (or the standalone's expansion install from storage). Free third-party "expansions" are often just sample/program folders — drop them in your project/sample storage and browse to them, vs official .xpn installers. Account-locked official expansions need to be authorized in your inMusic account first.

Autosampler plays a connected synth (or plugin) chromatically and captures each note into a keygroup program automatically, turning hardware/plugins into sampled instruments. Set the MIDI out to the synth, define the note range/velocity layers, and let it render — great for getting an external synth "into the box."

Standalone MPCs only run MPC‑internal plugins, not VST/AU. Third-party plugins work only in the MPC software (controller mode), and even there they must be a supported format/architecture and rescanned. "Plugin not working on standalone" almost always means it's a desktop VST the standalone can't run.

The Key 37 adds a 37-key keybed + onboard synth engines; the One+ is the compact pad-centric box with Wi‑Fi/Bluetooth. Note neither has built-in speakers — the MPC Live II is the standalone with battery + speakers. So choose the Key 37 if you want keys and onboard synths, or the One+ for the compact pad workflow; both share the standalone MPC OS. If you play keys and want built-in synths, Key 37; if you want the classic compact pad workflow and portability, One+. Both share the standalone MPC OS.

Audio track count and behavior vary by model/OS — standalone supports audio tracks but with limits vs the software. Arm an audio track, set input, and record; use the grid/main view to arrange. If audio tracks seem missing/limited, you may be on an older OS or hitting the model's track cap.

Keep projects self-contained (collect samples into the project) and back up to an SD/SSD regularly; don't move sample files a project references or links break. Internal storage fills fast with expansions — keep your library on removable storage and only load what a project needs.

Yes — MPCs sequence external gear over MIDI and mix audio inputs, so they work well as the center of a dawless rig. Watch for MIDI routing/port assignment (the #1 hybrid headache) and clock settings. The Force and MPC X have more I/O for bigger hybrid setups.

That's automation recording. Set the Automation state to Read (or Off) instead of Write — on standalone it's the global automation toggle (and per-track automation). When it's on Write, every parameter tweak is captured as automation; switch it to Read to play back existing automation without overwriting, or Off to ignore it entirely.

On standalone you can export a track/sequence as a MIDI file to your storage (and import MIDI files onto a track); in the MPC software you can also drag MIDI in/out. For round-tripping with a DAW, export the sequence as MIDI, edit in the DAW, and re-import. Keep an eye on tempo and which track/channel the MIDI lands on.

Warp time-stretches a sample to a target tempo without changing pitch. In the sample/program editor, set the sample's original BPM/bars, enable Warp, and the MPC stretches it to the sequence tempo; pick a warp algorithm that suits the material (drums vs melodic). If a loop sounds slow/fast or "off," its source BPM/bars are set wrong, so Warp is stretching by the wrong ratio.

The Tascam Model mixers add analog summing, per-channel EQ/compression and — crucially — multitrack USB recording, so an MPC (plus other gear) can be mixed hands-on and captured as separate stems into a DAW in one pass. It suits the dawless-but-record-stems workflow a lot of MPC YouTubers use. Any class-compliant multitrack USB mixer does the job; the Tascam is just the popular, affordable one.

Close in spirit, not a clone. The ASR‑10's character is its 12‑bit-ish converters + resampling grit. On an MPC1000 (especially with JJOS) lean on lower bit/sample-rate resampling, the filters, and committing the sound by resampling; run it through the SP‑404 MkII's vinyl/cassette/SX effects for the dusty top end. It won't be identical, but aggressive resampling + the SP's lo‑fi FX gets you into the same sonic territory.

Standalone MPCs (One, Live, X, Key, Sample) run the MPC OS on the hardware itself — no computer needed. They can also connect to a computer in controller mode, where the MPC 2 desktop software does the processing and the hardware is the control surface. Controller-only units (and older models) require the software. MPC Beats is the free, cut-down version of that desktop software. So a standalone unit is fully self-contained but can double as a controller — pick standalone if you want to make music without a computer.