Stems Are Changing DJing: What Lexicon Users Need to Know

From novelty to standard: stems are everywhere now

A few years ago, pulling a clean acapella out of a track live on the deck felt like a magic trick. Now it is a checkbox feature. VirtualDJ introduced real-time stem separation back in 2020 and kicked off the whole movement, splitting a song into vocals, melody, bass and drums during the mix. Since then, Serato added real-time Stems to Serato DJ Pro and Serato DJ Lite, isolating vocals, bass, melody and drums at the click of a button, and rekordbox shipped its own Track Separation / STEMS engine that splits a track into Vocal, Drums, Bass and Instrumental parts on the fly, with a choice between a three-part and a four-part mode.

The short version: if you use Serato DJ Pro, rekordbox or VirtualDJ, you already have stems, and the DJs around you are starting to build sets around them. That shift matters for anyone running a serious library, so it is worth being clear about what actually changes and what does not.

The big misconception: stems are a performance feature, not library files

Here is the thing that trips people up. Real-time stem separation happens live, on the deck, during playback. The software uses AI to split the audio as it plays. It does not quietly dump four new WAVs into your collection every time you load a track.

That distinction matters for library management:

• Your library size does not balloon. Isolating vocals or muting the drums in Serato, rekordbox or VirtualDJ does not create acapella or instrumental files that live in your folders. The separation is generated in the moment and thrown away when you unload the track.
• Your folder structure and file paths stay the same. There are no extra stem assets to organise, relocate or back up. One track in equals one track in your library.
• Your Lexicon database is unaffected. Because there are no per-stem files, there is nothing extra for a library manager to catalogue, dedupe or move.

If you deliberately bounce an acapella out to its own file, that is a separate manual step and that file is yours to manage like any other track. But the everyday, in-the-mix stems workflow adds nothing to your library. So the fear that "stems will bloat my collection" is mostly unfounded. What stems really change is how you prepare and cue the tracks you already have.

Where Lexicon actually fits: your cues have to survive the app hopping

The real library-side consequence of stems is subtler. Because each app has its own separation engine and its own sound, a lot of DJs are app hopping, testing Serato against rekordbox against VirtualDJ to find the stem quality and controls they like best. And stems change how people cue: instead of only marking the intro and the drop, you start dropping cues at the vocal-in, the a-cappella break and the exact bar where you want to swap a stem out.

All of which means your cue points now carry more of your creative work than ever, and they have to travel cleanly when you move a library between apps. That is exactly the job Lexicon is built for. It converts and keeps your cue points when you move a library between Rekordbox, Serato DJ and VirtualDJ.

The one wrinkle is Rekordbox, which is the only app with a separate memory-cue bank alongside its hot cues. Lexicon gives you explicit control over how that split is handled:

• When importing from Rekordbox, you choose which cues to pull in with Only hot cues, Only memory cues or Both.
• When syncing back out to Rekordbox, the Cue Destination setting decides where they land: Default, All to hot cue, All to memory cue, or All to hot and memory cue.

With the Memory Cue feature enabled in Lexicon, you mark any cue as memory cue for Rekordbox. When you have the Cue Destination setting on Default, it will only create memory cues from those special cues with the little M on them. This is great for stems. Keep your real hot cues intact and only set your vocal cues on the memory bank.

Serato DJ and VirtualDJ do not have a separate memory-cue concept, just hot cues, so Lexicon simply converts and keeps your cues when moving between those apps. The full behaviour is documented in the Rekordbox sync guide. If you are chasing the best stem engine by switching platforms, getting these settings right is what keeps your carefully placed stem cues intact.

What Lexicon does and does not do with stems

Lexicon is a library manager, not a performance app, so it is worth being precise about the boundary:

• Lexicon does not separate stems for you. The AI separation lives inside Serato, rekordbox and VirtualDJ. Lexicon organises the tracks that those engines then split live.
• There are no stem-specific fields to sync. Since the split is real-time and file-free, there is no stem metadata for Lexicon to carry between apps. Your cues, tags, beatgrids and track data are what move.

In other words, Lexicon's job in a stems world is to keep the underlying library clean and portable so that whichever app you fire up can do its separation on a solid, well-organised source.

Prepping your library for a stems workflow

A few practical habits pay off once stems become part of how you play:

• Start from clean, high-quality source files. Stem separation is only ever as good as what you feed it. A muddy, low-bitrate or badly transcoded file gives the AI less to work with, and the isolated vocal or instrumental will show it. Keeping one good copy of each track, rather than a pile of duplicates at different qualities, is the single biggest favour you can do your stems.
• Tidy up before you convert, not after. Fix tags, remove dead duplicates and settle your cue strategy in Lexicon first, then push the clean version out to your performance app. It is far easier to organise once in a library manager than to repair the same mess separately in Serato, rekordbox and VirtualDJ.
• Decide your cue convention and stick to it. If you are placing cues specifically for stem swaps, be consistent about where they go so they read the same way in every app after conversion. Consistency is what makes the cross-app cue handling above actually useful.

Stems are not a passing gimmick, they are becoming a standard part of the DJ toolkit. The good news for anyone already running a tidy library is that the shift asks very little of your file management and a lot of your preparation. Keep your source files clean, keep your cues deliberate, and let Lexicon make sure both survive the trip between apps.