Add Stems to a DDJ-1000 or DDJ-800 through Pad Editor.

A widespread idea is false: that using Stems requires a new controller. For the DDJ-1000 and DDJ-800, that is directly incorrect, and rekordbox’s own official documentation disproves it.

Both appear on the Pad Editor compatibility list, and Pad Editor includes a STEMS pad mode with dedicated functions for each stem. In other words: official Stems control, without mods, alternative firmware or buying anything.

You only need to know that this option lives in Pad Editor, rather than the MIDI Learn window.

The news first: yes, they are supported

The official Pad Editor compatibility list is short: DDJ-FLX10, DJM-S7, DJM-S11, DDJ-XP2, DDJ-800, DDJ-1000 and DDJ-XP1.

Both models in this guide are included. That is the fact changing everything: if your equipment appears on the list, you have the official route and need none of the alternatives.

Requirements before starting

Nothing unusual, but check everything first to avoid searching for a screen that will not appear:

1. Equipment powered on and connected by USB cable. Pad Editor requires a wired connection; it is not designed to work without connected equipment.
2. PERFORMANCE mode active. Select it at the top of the screen.
3. The equipment must support Pad Editor. If it is not on the list, this guide does not apply.

One reassuring detail: there is nothing to install or modify here. No firmware, mods or third-party tools. It is configuration inside rekordbox.

Step by step: enable STEMS mode on the pads

With those conditions met, the procedure is straightforward:

1. Open Pad Editor. When compatible equipment is connected, the [PAD] button appears at the top right. Press it to open the Pad Editor screen.
2. Choose the ASSIGN block. Each ASSIGN supports 8 pad modes, giving you two blocks of eight to allocate.
3. Select a customisable pad mode. For customisation, choose one of USER 1 to USER 8 rather than a fixed mode.
4. Choose the STEMS template. Templates provide a starting point: they assign a function to every pad at once rather than individually. The STEMS template assigns Active Stem and Active Stem FX functions.
5. Adjust individual pads if needed. You can change each pad’s function and its details. For example, add Active Stem Mute/Solo to a pad the template did not cover.
6. Test on the deck before relying on it. Check each pad with a real track. The configuration is not “exported” afterwards, so it is worth getting it right initially.

For templates, check one useful shortcut before building everything manually: alongside themed templates, recommended combinations assign a mixture of functions. Sometimes one already provides a reasonable starting point for how you play.

What each STEMS-mode pad function does

STEMS mode divides the track into VOCAL, INST, BASS and DRUMS and plays the audio accordingly. Its documented pad functions are in the table.

The STEMS template covers Active Stem and Active Stem FX. Mute/Solo is usually omitted and most missed, so it is worth adding manually.

Designing a usable layout

With nine possible functions and limited pads, decisions are necessary. An approach that works in the booth:

• Put the four Active Stem functions on pads you can press without looking. These are the ones you will actually use on time.
• Keep Mute/Solo beside them, because it rescues a misjudged entry.
• Group Active Stem FX in their own space. They are accents rather than the foundation, so they can occupy a less immediate area.
• Leave some space unused. A free pad you can reassign when your style changes is worth more than a full row of effects you never touch.

And the advice familiar from the Pad Editor guide: if the same knob or pad changes function, you need soft takeover to avoid a live parameter jump. Stems are the number one use case for this feature, because sharing knobs between EQ and stem volume is common.

The detail that breaks expectations

Read one note in the official documentation before designing anything: Pad Editor applies to all decks.

You cannot configure pads one way on deck 1 and differently on deck 2. It is a global configuration.

If you planned to use only three stems on one deck and allocate the other differently, that cannot be implemented here. Since this applies to Pad Editor generally, no other tool inside rekordbox permits it. Knowing beforehand avoids a design you cannot execute.

Ergonomic trade-offs

Without dedicated controls, every pad assigned to Stems is taken from another function. Three typical conflicts:

• Pad FX: assigning pads to Stems removes direct effects access. Choose or divide the space.
• Hot Cues: taking pads from cues is costly, because cues are part of playing forward.
• EQ: mapping stems to EQ controls offers fine mixing, but you lose that band’s EQ while the mode is active.

There is no single correct answer. Avoid building everything the day before a gig: a pad layout needs hours of use to become automatic, and live, hesitation means you will not use it.

Common mistakes

• Looking for Stems in MIDI Learn rather than Pad Editor. They are different tools, and this feature lives in Pad Editor.
• Opening Pad Editor without USB-connected equipment. The screen does not appear.
• Not using PERFORMANCE mode. Pad Editor is unavailable outside it.
• Assuming different pads per deck are possible. It applies to all decks.
• Designing the layout without soft takeover when controls are shared with EQ.
• Expecting to export pad configuration like a MIDI mapping. Pad Editor does not generate that file; MIDI Learn is the route for mapping backups.

Next step

You now have Stems working on pads through an official feature. But as soon as one control serves two functions—and with Stems that is almost inevitable—you will need the next concept, already mentioned three times in this section: soft takeover. It is short, precisely defined in the documentation, and prevents the parameter jump everyone has experienced without knowing its name. It is the next guide.