Overview
Massive X is Native Instruments’ follow-up to the original Massive, sold on its own and as part of Komplete. It runs as a plugin in your DAW. The sound starts with two wavetable oscillators, and NI adds two phase-modulation oscillators that can push extra movement into the main pair, plus two noise modules whose sources range from synthesized noise to recordings like rain, choirs, and machines.
Each wavetable oscillator can read its table in one of 10 oscillator modes, and each mode has its own submodes and extra controls. NI lists the aggressive Gorilla family (King, Kang, and Kong), a wavetable-bending mode, Hardsync, and Formant among them. Because the mode changes how the table is read, the same factory table can sound very different from one mode to the next, which is where much of Massive X’s range comes from.
NI says the instrument ships with over 170 wavetables. The routing system also lets insert slots act as extra sound sources, with up to three additional sine, saw, or pulse oscillators.
Wavetables on the Massive X
Massive X doesn’t import user wavetables. Native Instruments’ own Massive X FAQ answers the question directly: loading custom wavetables “is not possible currently.” The oscillators only read the factory set, and there’s no folder you can drop WAV files into and no import menu in the plugin.
That means a table built or exported in WaveStack can’t be loaded into Massive X, whatever its frame size or format. Converting the file won’t help, since the limit is in the instrument rather than the file, and renaming a WAV or placing it next to the factory content doesn’t make Massive X see it. WaveStack has no Massive X target for that reason. If NI adds import in a future update, this page will change.
If you want your own tables in a plugin, several synths read them and WaveStack exports to each one directly: Serum, Vital, Surge XT, Phase Plant, Pigments, Hive 2, and Ableton Wavetable if you work in Live. You can keep Massive X in the same project for its modes and modulation and run your own tables in one of those alongside it.
Those plugins don’t all want the same file. Serum and Vital read 2048-sample frames, Ableton Wavetable works in 1024-sample frames, and Phase Plant only loads a WAV that is exactly 256 frames of 2048 samples. WaveStack builds the table once and writes each version to the rules of the synth you pick, so moving a sound between them doesn’t mean redoing the work. For background on frames, scanning, and why frame size matters when a table moves between synths, see how wavetables work.
Specifications
| Oscillators | 2 wavetable, plus 2 phase-modulation |
|---|---|
| Oscillator modes | 10, each with submodes |
| Factory wavetables | Over 170 |
| User wavetable import | None |
Frequently asked questions
Does Massive X support user wavetables?
No. Native Instruments’ Massive X FAQ says importing custom wavetables is not possible currently. The two wavetable oscillators read only the factory set of over 170 tables. There’s no import menu and no user wavetable folder, so WAV files from WaveStack, Serum, or any other editor can’t be loaded. If you need your own tables, use a plugin that reads them, such as Serum, Vital, Surge XT, or Pigments.
Can I load Serum wavetables into Massive X?
No. Serum wavetables are WAV files, and Massive X has no way to read user WAV files as wavetables. Native Instruments’ FAQ confirms custom wavetable import isn’t possible. Serum tables load in Vital, Surge XT, Bitwig Polymer, and several other synths, and WaveStack can convert a table to the exact frame size each of those expects. Massive X is limited to its own factory tables.
How many wavetables does Massive X come with?
Native Instruments says Massive X includes over 170 wavetables. Each one can be read in any of 10 oscillator modes, including the Gorilla family, a bending mode, Hardsync, and Formant, and each mode has its own submodes and controls. That’s why the factory set covers more ground than the number alone suggests: one table sounds quite different from one mode to another.
Why doesn’t WaveStack have a Massive X export?
Because Massive X has nothing to export to. An export target only makes sense when the instrument can load a user file, and Native Instruments’ FAQ says custom wavetable import isn’t possible in Massive X. WaveStack exports to the synths that do read user tables, including Serum, Vital, Surge XT, Phase Plant, Pigments, Hive 2, and Ableton Wavetable. If Massive X gains import later, a target can follow.
What plugin should I use instead if I want my own wavetables?
Any of the plugins WaveStack exports to will load your tables: Serum, Vital, Surge XT, Phase Plant, Pigments, Hive 2, Ableton Wavetable in Live, and Polymer or Grid in Bitwig. Vital and Surge XT are free downloads. Each reads WAV wavetables with slightly different rules for frame size and frame count, and WaveStack handles those per target, so you pick the synth and it writes the file that synth expects.