Overview
What a stem is, how the four layers and the mixdown relate, and which route puts stems on a track.
A stem is one instrumental or vocal part of a track, separated from the rest so you can control it on its own. Instead of one stereo mix, you work with the song’s building blocks.
The four layers
Mixar uses the same four parts as Native Instruments Stem files:
| Layer | Typical content |
|---|---|
| Drums | Kick, snare, hats, percussion |
| Bass | Bassline and low-end instruments |
| Other | Synths, pads, guitars, and everything that is not drums, bass, or vocals |
| Vocals | Lead and backing vocals |
Mixdown
The mixdown is the full stereo track, all parts combined the way you normally hear the song. In a Stem file it sits beside the four layers. When stems are available, Mixar plays that mixdown as the main audio and attaches the four layers so you can mute or isolate them. Until you change a layer, what you hear is the complete mix.
A normal MP3 or FLAC is only a mixdown. Generating stems keeps a mixdown in the cache file and adds the four separated layers next to it.
Why stems are useful
Stems let you change the mix while the track plays:
- Drop the vocals for an instrumental breakdown, or solo vocals over another track’s beat.
- Mute drums when you want a soft intro, or solo drums to keep the groove while you bring in the next track.
- Carve space in a mix, for example silence “other” so a vocal from deck B sits cleaner.
- Rehearse and perform the same ideas without exporting alternate edits of every song.
On the deck, the Stems pad mode is how you mute and isolate those layers while the track plays.
Two routes to stems
The route depends on the file you have:
| Aspect | Native NI Stem file | Generated by Mixar |
|---|---|---|
| Source | A .stem.mp4 that already contains the four layers |
Any normal library track (MP3, FLAC, WAV, and so on) |
| Preparation | None | Separation in the background, from the track menu or the collection Analyze dialog |
| Separation model | Not used | HTDemucs or SCNet int8, downloaded once |
| Result on disk | The file stays where you put it | One .stem.mp4 per track under Mixar’s app data |
| Ready when | The track loads | The job finishes; later loads reuse the cache |
Use the native file when you already have one. For any other track, generate a cache once and the pads are ready on later loads.
Loading a deck never starts an offline separation by itself. Until stems exist for the loaded track, the Stems pads stay disabled and the track plays as a normal stereo file.
With Settings → Mixer → Realtime Stems enabled, a deck whose track has neither a cache nor native Stem layers can separate live instead. That fallback writes nothing to disk and has lower quality. See Generate stems for when to rely on it.
What stems cost
- Time: separation can take a while, often on the order of the track’s length and sometimes longer on slower machines. A GPU is recommended, and Mixar uses one automatically; without a GPU the job runs on the CPU, more slowly.
- Disk: one
.stem.mp4per separated track, plus the shared separation model. Native Stem files are not copied, and live separation writes nothing. - During a set: jobs run in the background and do not stop playback, but they still compete for CPU, GPU, and disk. Generate stems before you perform.
Generated files and the separation model live under Mixar’s app data: see Storage for locations, format, clear, and sync.
In this section
| Topic | Page |
|---|---|
Open .stem.mp4 files as-is |
Native NI Stem files |
| Separate any library track | Generate stems |
| Cache location, format, clear, and sync | Storage |
| Mute and isolate on the deck | Stems pad mode |
Internals for contributors: Stems (developers).