Massive X 1.6.1 update (September 2025)!

[digitalboytn]

I bet Mikael would still be interested. Right?

I would be if there was enough requests for a MX soundset by Leap Into The Void.
What do you (everyone) think?

In the meanwhile if there are Massive enthusiasts here that would be interested there's a Leap Into The Void complete Massive bundle with a super price available right now.

Absolutely - take my money now

Wusik

[_leras]

You actually could tag your sounds in Komplete Kontrol and it would show under user banks. For example:

Maybe I missed a previous post, but it is pretty simple to select just your own user saved patches.

Everything else in the browser is a bit painful unless looking at NI preset packs...

[_leras]

i was never able to gel with MX. it sits gathering dust.

Did you read the manual?

[ChanceB]

i was never able to gel with MX. it sits gathering dust.

Did you read the manual?

Definitely worth reading. This synth has specific components,wavetables,warp modes,routings etc that are designed to work together.It’s pretty great really,I should probably try to use it more often.

[swilow11]

Before I demo it... can I adjust the parameters with the scroll wheel in Massive X?

No

Thanks... and bye bye Massive X

People are just insanely picky. Massive X Is easily the best sounding soft synth out there.

That's why sound designers rolled out thousands of amazing preset packs for Massive X

Point taken but is that how you honestly evaluate a synth? MX has plenty of drawbacks but the sound quality is simply not one of them.

When it comes to 3rd party sound packs, I think the inability to import ones own wavetables works against it. I actually really like this aspect- the included tables are great and limitations spur one to actually rely on and deepen their synthesis ability. But for sound designers trying to make a living of this, that sort of limitation may just make MX less appealing than the great but generic Serum for eg.

[EvilDragon]

There's 700+ factory wavetables, couple that with a shedload of wavetable mangling modes (a lot of them not available in any other wavetable synth!), you still end up with a fuckton of sounds.

[digitalboytn]

There's 700+ factory wavetables, couple that with a shedload of wavetable mangling modes (a lot of them not available in any other wavetable synth!), you still end up with a fuckton of sounds.

Some creatively descriptive language

[EvilDragon]

Pretty much! But really I mean...

https://native-instruments.com/ni-tech- ... able-modes

This is extremely comprehensive.

[RobGee]

For me all it needs is an upgrade to the browser, lfos and some midi and automation enhancements. Such a shame NI are run by bean counters now! It definitely holds its own sound wise compared to my Summit and PolyBrute.

[Vortifex]

Biggest issue for me is the lag. It takes a while for the interface to open, and while that's happening it freezes my DAW. Having to double click presets is a pain in the arse too. Definitely the best sounding synth I have though.

[MidnightRunner]

i was never able to gel with MX. it sits gathering dust.

Did you read the manual?

i tired to read some of it. the entire GUI seems counterintuitive compared to other competing products (which I won't bother to name.). Synth VI's are a personal taste. With some you get along. With some you don't.

[swilow11]

There's 700+ factory wavetables, couple that with a shedload of wavetable mangling modes (a lot of them not available in any other wavetable synth!), you still end up with a fuckton of sounds.

Yeah I don't disagree- the wavetables, wavetable modes, and simply enormous PM options make it almost unlimited. But I do think the lack of import has decreased the number of sound designers building packs for MX mainly because it's way easier to just import a predictable table into whatever synth than it is to have to synthesise the sounds using a fixed set of options/tools.

[EvilDragon]

The problem is that MX wavetables require some additional metadata in order to make certain WT mangling modes work. This would not work with external wavetables.

[swilow11]

The problem is that MX wavetables require some additional metadata in order to make certain WT mangling modes work. This would not work with external wavetables.

I did not know that, interesting.

[Dencheg]

It is a shame the browser isn't a bit better, and that seems to have paused updates. A 1.5 or even 2.0 update would be very welcome.

Lots of low hanging fruit for NI when they get the time.
Browser improvements
LFO improvements
Midi control mapping (beyond the macros)
etc

At least we've got oscialltors. And they are the best.