Massive X 1.6.1 update (September 2025)!

[swilow11]

Massive X is marketed as a flagship wavetable synth, yet it’s closed off to external content. That fundamentally contradicts the modular and exploratory spirit of wavetable synthesis. Every serious wavetable synth today, even free ones offer WT import. So Teksonik is absolutely right here.

Yes, you get 170+ tables with shaping modifiers, but they're finite. Creative workflows are stifled when you can’t experiment with your own audio sources. The metadata excuse is weak. NI could still allow user import with limited compatibility.

It's not an excuse, it's actually the reality. And it's not closed off to external inputs, you can use whatever noise samples you want. I know that's not what you mean but still, that's the reality. It probably could import wavetables given the fact it can use imported samples but the fact it can't suggests the metadata issue is actually the real reason NI didn't allow it.

Saying that it's not "serious" because "finite" is just weird. You could probably make (arbitrary number incoming) 464,567 different sounds with it. It's finite nature is so broad as to probably never really impact you. If there is a particular wavetable that you absolutely must use, the best way to deal with that is to figure out how to get there another way. This is agreat boost for creativity and I've learned a heap about sound design with Mx as a result. I appreciate limitations because they represent a very effective way to enhance creativity. Maybe you don't and that's totally fine.

Teksonic isn't actually "right" because he was responding to my opinion. His perspective on what I feel is as irrelrvantt as what shoes you've got on while I'm writing this. He can disagree but then it's like me arguing against his aversion to spaghetti. Im not saying that it absolutely shouldnt allow wavetable import. I'm just saying that for me, it's no longer a big deal. If it is for you, simply don't use the synth.

[zerocrossing]

Massive X is marketed as a flagship wavetable synth, yet it’s closed off to external content. That fundamentally contradicts the modular and exploratory spirit of wavetable synthesis. Every serious wavetable synth today, even free ones offer WT import. So Teksonik is absolutely right here.

Yes, you get 170+ tables with shaping modifiers, but they're finite. Creative workflows are stifled when you can’t experiment with your own audio sources. The metadata excuse is weak. NI could still allow user import with limited compatibility.

It's not an excuse, it's actually the reality. And it's not closed off to external inputs, you can use whatever noise samples you want. I know that's not what you mean but still, that's the reality. It probably could import wavetables given the fact it can use imported samples but the fact it can't suggests the metadata issue is actually the real reason NI didn't allow it.

Saying that it's not "serious" because "finite" is just weird. You could probably make (arbitrary number incoming) 464,567 different sounds with it. It's finite nature is so broad as to probably never really impact you. If there is a particular wavetable that you absolutely must use, the best way to deal with that is to figure out how to get there another way. This is agreat boost for creativity and I've learned a heap about sound design with Mx as a result. I appreciate limitations because they represent a very effective way to enhance creativity. Maybe you don't and that's totally fine.

Teksonic isn't actually "right" because he was responding to my opinion. His perspective on what I feel is as irrelrvantt as what shoes you've got on while I'm writing this. He can disagree but then it's like me arguing against his aversion to spaghetti. Im not saying that it absolutely shouldnt allow wavetable import. I'm just saying that for me, it's no longer a big deal. If it is for you, simply don't use the synth.

It's software, so obviously there's the possibility of a solution for wavetable import, if they wanted to provide it. Are they adding the metadata manually? If not, could their import process add it?

Regardless, you're right, it's doubtful they'll add it, and development seems dead. There are plenty of other plugins that do import/editing. One thing that's weird, is that they probably could have done expansion packs with added factory waveforms. Imagine a "Reimagined presets of the original PPG," that had presets inspired by the original ones that came from the PPG Wave, and all the wavetables. I'd pay for something like that. "Waves of the VS" "DWG Mania," "Viral Infection," etc. Money sitting there to be taken. I think if they'd continued development of Massive X, and fixed all the issues with the user interface, added stuff in a V2, it would be one of the most talked about wavetable synths on this site. Now it's not mentioned that often, and when it is, it's usually some complaint.

[EvilDragon]

The development is not dead, just FYI.

[Bartone]

The development is not dead, just FYI.

That is great news!

I would love to see easier/faster preset browser.
I am (at least now) using mostly ready to made presets so that would be good.

The workflow is somehow not intuitive for me but that is maybe just me (but then again it seems I’m not the only one feeling this).

But the sound is very good and there are very good presets inspiring and giving new life for my music

[swilow11]

The development is not dead, just FYI.

Good news... do you know what sort of development this could be?

[EvilDragon]

I do, but sadly I cannot share anything about it. ^_^;

[Penguin Classics]

I think it looks great and is pretty easy to use already - the only area I find it slow is the wavetable warp modes, just feels like a fair bit of clicking about for some reason and I don't find it that enjoyable.. I'm not bothered at all about user wavetables personally..
It is fantastic it is still being worked on - the sound is majestic.

[Danilo Villanova]

The development is not dead, just FYI.

The OTT update after a year of nothing was a slap in the face. Very little confidence they will not drop the ball (doing so is their nature and identity at this point). I'm happy to be proven wrong but we all know that the browser will get updated to make it bare minimim functional, but nothing else get be sorted.

[SamDi]

The development is not dead, just FYI.

It might be not dead in terms of, that they keep it running for latest MacOS updates, but I doubt, that they are going to improove much mure. Hell this synth is really good sounding, but using it with the dated GUI is so much PITA, compared to Serum, Pigments or Phase Plant, that I avoid it for making presets myself. They should have taken the chance in the first version to update it to modern GUI standards and mod matrix, add proper MESGs and making effect settings and performance modulators save- and loadable.

[EvilDragon]

They are working on things other than OS compatibility updates.


"Dated" GUI? This ain't Synth1, yo. THAT is a dated GUI. MX is not. Lack of mod matrix is not making it "dated", it is an explicit design decision (OG Massive also didn't have it, and it was perfectly fine - a synth doesn't NEED to have a mod matrix, there's more than one way to skin a cat).

[Teksonik]

Why? If you love the sound of MX why not support it having a wider range of sounds provided by a wider range of waveforms and wavetables to choose from?

All factory wavetables have additional metadata which is required for some of the shaper modes. None of the 3rd party wavetables out there would work properly in those modes then.

Are you saying that the N.I. coders couldn't figure out a way to add user wavetable import for tables that bypass those shaper modes? Or that they couldn't figure out how to create a waveform/wavetable creation tool inside MX?

Ok fair enough. I've got enough other plugins that do allow for not only user waveform/wavetable import but the creation of same as well.

[EvilDragon]

Sure, there would have to be some sort of analysis tool - but this is gone with Mike Daliot as he holds the rights to that AFAIK (not NI). And he's not getting involved with this project ever again, for reasons.

In any case, there is absolutely enough ways to contort the factory wavetables beyond anything any other WT synth does, so those things should be explored first, as that's what the intention behind the whole thing was. Now you may disagree with that design decision, and that's fine, but that's also missing the point.

[aMUSEd]

They are working on things other than OS compatibility updates.


"Dated" GUI? This ain't Synth1, yo. THAT is a dated GUI. MX is not. Lack of mod matrix is not making it "dated", it is an explicit design decision (OG Massive also didn't have it, and it was perfectly fine - a synth doesn't NEED to have a mod matrix, there's more than one way to skin a cat).

Mod matrix would be a step backwards - it was Massive that helped set the current trend of drag and drop modulation - modulation in Massive X continues to use that so in that sense it is inline with current interfaces. It also has a semi modular aspect I hope does not get dumbed down.

I don't really care about wavetable import or editors - not that fussed about having more macros - 16 imho is enough for most sound designers - in fact most don't use more than 8.

All I want is full user bank authoring, less clunky user tagging and browser, some more LFO types, polyphonic performers with sub presets, micro tuning support and polyphonic aftertouch. 3 OSCS might be nice - maybe more synthesis types but I also want NI to make other synths rather than try and cram everything into Massive X. MPE would be the icing on the cake.

[SLiC]

S MK3 owner here - polyphonic aftertouch on ALL NI instruments is an absolute must, amazed it hasn't been done already (but then I still can't play drum kits on Maschine so....)

[Teksonik]

With MX you get over 170 Wavetables

That's cute. Here's a link for 2,500 wavetables and included waveforms:

https://charlesdickens.neocities.org/

And 1,000 more:

https://oceanswift.net/product/dune-3-wavetable-pack/

Beyond the raw oscillators you then have a deep and complex synth

It's not deep and complex when you compare it to synths like Avenger or Rapid. It's modulation may be complex but its architecture is not when compared to more powerful synths.

if they offered Wavetable import then what? The rest of the synth engine wouldn't work with them without the meta data

As mentioned by ED "some of the shaper modes". Imported wavetables would still have a useful function even if they couldn't take advantage of those modes. Not everything needs to be modulated to death just to get a useful and pleasant sound.

So you would be reduced to using them in the traditional Wavetable way, and why would you want to do that?

"Reduced to using them in the "traditional Wavetable way" would still provide function beyond the limited number of wavetables included so that's why I would want them.

But it's quite apparent that user waveform/wavetable import or creation is not going to happen in Massive X and in a way that's a good thing because it will keep people who get triggered by new features from having to waste their time pushing back against them on an internet forum.

In the end I got Massive X for free and its certainly worth every penny of that price. It's not ever going to be one my most used synths but it will probably see some use despite its many limitations. So for that I am grateful to NI for their generosity.

At any rate I won't discuss it any further. I made a feature request that's obviously not going to happen so time to move on......