Massive X 1.6.1 update (September 2025)!

[EvilDragon]

It's not hard, but then you have to do it for each and every patch that doesn't have those assignments. That's the objection here. Usually with other plugins which do have MIDI learn implemented, it is global and applies for all patches.

This is potentially trickier for MX since it's semi-modular and different module types can have different number of parameters.

[sQeetz]

oooh poor you... having to adjust a plugin to your liking....

[chk071]

Sorry, I know that some objections are justified, but...

[pdxindy]

You assign cutoff, Res to Macros 1 & 2
I don't understand how this is so hard?

You assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
assign Cutoff and Res to Macro 1 and 2... now switch presets and you again have to
Etc., Etc., Etc.

With every other synth I own, I can do it once and it works for all presets.

[sQeetz]

Do you?

[aMUSEd]

It's not hard, but then you have to do it for each and every patch that doesn't have those assignments. That's the objection here. Usually with other plugins which do have MIDI learn implemented, it is global and applies for all patches.

This is potentially trickier for MX since it's semi-modular and different module types can have different number of parameters.

Which is why I think the Omnishere type approach probably makes the most sense.

[EnGee]

Macros add an additional unnecessary layer. For me they are secondary in importance when programming/automating parameters. Take the original Massive. Most of the macros are the "lazy" knobs for someone doesn't want to involve in sound design or editing. So, in that, yes, I agree with a previous post that said NI might have wanted MX to be mainly a player for libraries they sell. Another Nexus maybe?!

[EvilDragon]

Do you?

He does otherwise there'd be no objection.

[digitalboytn]

What amazes me here is that NI got the original Massive so right...

WTF has happened with Massive X ?

[pdxindy]

Macros add an additional unnecessary layer. For me they are secondary in importance when programming/automating parameters. Take the original Massive. Most of the macros are the "lazy" knobs for someone doesn't want to involve in sound design or editing. So, in that, yes, I agree with a previous post that said NI might have wanted MX to be mainly a player for libraries they sell. Another Nexus maybe?!

That would explain the non-existent browser for user presets too. Or maybe that they want to promote their controllers.

[aMUSEd]

Macros add an additional unnecessary layer. For me they are secondary in importance when programming/automating parameters. Take the original Massive. Most of the macros are the "lazy" knobs for someone doesn't want to involve in sound design or editing. So, in that, yes, I agree with a previous post that said NI might have wanted MX to be mainly a player for libraries they sell. Another Nexus maybe?!

I love the way the macros work in Massive - a good sound designer, thinking particularly here of Leap into the void - uses the macros intelligently to expand the sonic range of each preset by creating additional sonic possibilities to explore.

[zzz00m]

You assign cutoff, Res to Macros 1 & 2
I don't understand how this is so hard?

I understand, but that would fail as soon as you selected a new preset...

[EnGee]

Macros add an additional unnecessary layer. For me they are secondary in importance when programming/automating parameters. Take the original Massive. Most of the macros are the "lazy" knobs for someone doesn't want to involve in sound design or editing. So, in that, yes, I agree with a previous post that said NI might have wanted MX to be mainly a player for libraries they sell. Another Nexus maybe?!

I love the way the macros work in Massive - a good sound designer, thinking particularly here of Leap into the void - uses the macros intelligently to expand the sonic range of each preset by creating additional sonic possibilities to explore.

But just compare sound design in Massive 1 and Massive X! Which one you want to spend your time with?
Oh man! We just wanted Massive 2, i.e. Massive 1 with updated audio/synthesis engine, some additional features and filters and bigger GUI!

[fisherKing]

But just compare sound design in Massive 1 and Massive X! Which one you want to spend your time with?
Oh man! We just wanted Massive 2, i.e. Massive 1 with updated audio/synthesis engine, some additional features and filters and bigger GUI!

is the correct answer massive X? i used massive for years, don't miss it, and am thrilled with X, and it's better sound, and it's capabilities...

[EnGee]

But just compare sound design in Massive 1 and Massive X! Which one you want to spend your time with?
Oh man! We just wanted Massive 2, i.e. Massive 1 with updated audio/synthesis engine, some additional features and filters and bigger GUI!

is the correct answer massive X? i used massive for years, don't miss it, and am thrilled with X, and it's better sound, and it's capabilities...

No!!
Ok, maybe NI did the right thing then! I might be in the minority, but I like the original Massive much more (design and workflow), but of course Massive X wins in the sound quality.