Massive X 1.6.1 update (September 2025)!

[DJ Warmonger]

Lots of people like to use midi controllers... many people use Ableton Push and you can set it up to globally edit most every plugin without needing to use the mouse and screen. This is not possible with Massive X because you cannot edit parameters directly.

You don't get it. You need to assign whatever parameters to the very top row of 16 macro knobs (preferably only and then control these with any MIDI controller of your choice, especially Ableton Push. This is standardized way to control such a complex synth with knobs.

[el-bo (formerly ebow)]

Lots of people like to use midi controllers... many people use Ableton Push and you can set it up to globally edit most every plugin without needing to use the mouse and screen. This is not possible with Massive X because you cannot edit parameters directly.

You don't get it. You need to assign whatever parameters to the very top row of 16 macro knobs (preferably only and then control these with any MIDI controller of your choice, especially Ableton Push. This is standardized way to control such a complex synth with knobs.

Huh?

I have a controller with 24 knobs, 9 sliders and about 20 buttons, all of which could potentially be assigned to separate functions of a synth. Being locked into only a handful of combined assignable options is a severe, arbitrary and unnecessary limitation, especially for a synth that’s supposed to be at the top of the heap. Give us macros...sure, but not at the expense of such basic, expected functionality

[DJ Warmonger]

Different people have different controllers, often simpler than yours.

Plus, standardized macros make it possible to create presets that have controls already mapped. You don't need to do anything.

[el-bo (formerly ebow)]

Different people have different controllers, often simpler than yours.

Plus, standardized macros make it possible to create presets that have controls already mapped. You don't need to do anything.

Not sure where you got the idea that either pdxindy or I don’t understand the benefits of macros. It’s great when synths go the extra mile to include them, along with other performance features. What isn’t great is when they are given as the only option, eschewing normal, expected MIDI-assignable behaviours.

[middle_color]

I am bad in music theory: how to setup dotted delay in Massive X? I see there is no such option, but it should be possible with choosing different dividers of time?

[chk071]

Yes. E.g., 3/16 is a dotted 1/8.

[Arcvidean]

Double post.

[Arcvidean]

The Save button has stated blanking out on Massive X 1.3 (didn't used to when I first updated) I've found it's only usable when I move the tiny little triangle that serves as the slider for the main volume control. When I change a program it blanks out again and I have to do the same thing. Really wierd.

Arcvidean.

[gondii]

Lots of people like to use midi controllers... many people use Ableton Push and you can set it up to globally edit most every plugin without needing to use the mouse and screen. This is not possible with Massive X because you cannot edit parameters directly.

You don't get it. You need to assign whatever parameters to the very top row of 16 macro knobs (preferably only and then control these with any MIDI controller of your choice, especially Ableton Push. This is standardized way to control such a complex synth with knobs.

Huh?

I have a controller with 24 knobs, 9 sliders and about 20 buttons, all of which could potentially be assigned to separate functions of a synth. Being locked into only a handful of combined assignable options is a severe, arbitrary and unnecessary limitation, especially for a synth that’s supposed to be at the top of the heap. Give us macros...sure, but not at the expense of such basic, expected functionality

Yeah I am also using a 24 knob, 8 slider controller and I can have several pages with different mappings. That way I like to map my entire synth to the controller - for example: page 1 oscillators and macros, page 2 filters and envelopes, page 3 modulation, page 4 effects depending on the synth. Works quite well and is a lot of fun. So it's unfortunate that it's not possible with MX.

[chk071]

The Save button has stated blanking out on Massive X 1.3 (didn't used to when I first updated) I've found it's only usable when I move the tiny little triangle that serves as the slider for the main volume control. When I change a program it blanks out again and I have to do the same thing. Really wierd.

Arcvidean.

Not sure if I get you right, but, isn't that exactly how it's supposed to behave? I mean, if you switch the preset, and did no change to the preset, then it's pointless to save the preset, thus the save button should be greyed out, and not operable.

[pdxindy]

Lots of people like to use midi controllers... many people use Ableton Push and you can set it up to globally edit most every plugin without needing to use the mouse and screen. This is not possible with Massive X because you cannot edit parameters directly.

I get what you mean, and I definitely appreciate the ability to control every (or almost every) parameter on most synths with my Komplete Kontrol S49 (the ones that support NKS, anyway). However, I'd argue that it's not practical in this case, because Massive X is so flexible that it's impossible to simply create a map all of its parameters. Practically every section has a dropdown menu at the top that lets you swap it out with a different module, and each module has different parameters, with different numbers and types of controls. Many of them even have a subtype or other menus that also reveal different controls. There are also graphical performance sequencers and tracking maps, and a graphical routing page.

I didn't say I want to map everything... but just cause I don't want to map everything, doesn't mean I don't want to be able to map anything.

And Massive X doesn't have more parameters than say Zebra... yet I can map/automate/midi learn pretty much anything in Zebra. That is how it should be. Zebra has macros too. 4 X/Y pads. And I can create as many macros as I want in Bitwig using Bitwig modulation. Except Massive X cannot work with Bitwig's modulation system. Massive X is crippled.

There is no reason whatsoever for it to be an either or.

[pdxindy]

Lots of people like to use midi controllers... many people use Ableton Push and you can set it up to globally edit most every plugin without needing to use the mouse and screen. This is not possible with Massive X because you cannot edit parameters directly.

You don't get it. You need to assign whatever parameters to the very top row of 16 macro knobs (preferably only and then control these with any MIDI controller of your choice, especially Ableton Push. This is standardized way to control such a complex synth with knobs.

I know what the macros do. They only work per preset. If I want the first 8 macros to be the Amp Envelope, I have to set that up and overwrite every single preset one by one. Every other synth I have I can set that up once and it works for all instances/presets.

Lots of complex synths have midi learn and parameter automation. That would include Zebra, Dune, Icarus, etc. All synths with many hundreds of parameters and all/most of them can be automated and/or midi learned as needed. There is no reason MX cannot do the same.

Though I can set up the same sort of macros for any synth in Bitwig, it's handy to have the macros as an option in Massive X for hosts that don't have Bitwig's capability... but not having midi learn and parameter automation is a severe limitation in Massive X. I find the sound quality of Massive X to be right up there with the best synths available today. The infrastructure around it however is outdated to non-existent. It's shockingly bad. Something is wrong at NI.

[Arcvidean]

The Save button has stated blanking out on Massive X 1.3 (didn't used to when I first updated) I've found it's only usable when I move the tiny little triangle that serves as the slider for the main volume control. When I change a program it blanks out again and I have to do the same thing. Really wierd.

Arcvidean.

Not sure if I get you right, but, isn't that exactly how it's supposed to behave? I mean, if you switch the preset, and did no change to the preset, then it's pointless to save the preset, thus the save button should be greyed out, and not operable.

I'm pretty sure it's after changing the preset but I'll check that this evening. I haven't come across SAVE functions blanked out before, can anyone else advise me?

Arcvidean.

[Arcvidean]

The Save button has stated blanking out on Massive X 1.3 (didn't used to when I first updated) I've found it's only usable when I move the tiny little triangle that serves as the slider for the main volume control. When I change a program it blanks out again and I have to do the same thing. Really wierd.

Arcvidean.

Not sure if I get you right, but, isn't that exactly how it's supposed to behave? I mean, if you switch the preset, and did no change to the preset, then it's pointless to save the preset, thus the save button should be greyed out, and not operable.

Yes you're quite right thank you , I must have perhaps just been renaming the program. I suppose that has to be done in the User contents folder and rescanning the browser instead of using the SAVE function. It does seem a bit more cumbersome but then I'm sure someone will tell me to stop whining if I mention it, so I won't.

Arcvidean..

[markyboard]

New to massive x, but It has no MIDI learn or automation? The only thing you can do apparently is automate some macros via daw? Thats kinda ridiculous!

Kinda. It makes sense in some way though. We could update how our sound is responding to the automation by making tweaks to the parameters but because the Macro is automated we wouldn’t have to adjust several lanes of automation data. It’s actually quite a smart way to do it. Lion can only be automated by its macros too. I’m sure there are others.

No, it is not a smart way to do it. Being able to automate macros is cool, but when that is all you can do, that is not smart at all... way too limited and clumsy

If it saves you time re-automating because of the parameters you wish to change. It is quite smart. Anything that makes life easier for you and saves time is smarter way to work with. Because it limits it to just the macros which are very, very easy to set up it saves you from also potentially wading through the endless lists of automatable parameters in the DAW, especially if your automating several on the timeline, that’s quick, it’s precise, it’s the opposite of clumsy.

I can understand you have a preferred way of working, but you can’t really say it’s not smart or that it’s clumsy.

Hi -
With all due respect from an old guy...

You need to be listening to and acknowledging your customer's comments. While your replies are somewhat informative regarding automation they don't address the concerns and specific points of needing midi learn by more than a few. Suggesting options is fine. But attempting to softly insult people into working differently is to your benefit, not the customers

If you can't implement midi learn for some reason (cost, technical limits etc) so be it (and maybe tell us). But your replies quickly sound argumentative and dismissive. We're paying customers. Please treat us as such.

Thanks.