Massive X 1.6.1 update (September 2025)!

[chk071]

I could be wrong, but, I think what sQueetz meant was mapping the controls to macros inside your DAW.

Which is something I personally don't do (I rather use the plugin's GUI), but, we're all different.

[sQeetz]

Let's assume you want to automate filter cutoff. Just assign Filter Cutoff to one of the 16 macros and automate that.

[pdxindy]

It's not about the number and it's not just about automation.

In Bitwig, if I want to create a Remote Page with 8 Amp Env parameters so that I can edit them without opening the plugin GUI and/or using my midi controller for it, not possible* in MX.

How often do you really need/want to do that? Seriously

I have Remote Pages set up for all my synths and FX. It's fast and easy to do and once done, works for every instance automatically from then on.

It's especially nice for simple plugins like Valhalla Plate where I can map the common parameters to a single Remote Page and then I can tweak the plugin without opening the GUI. Quite handy!

Also, I can set up the default state for devices (Bitwig and Plugins)... so I can add a number of modulators with assigned targets (but depth at 0) and they are automatically there with each new instance.

Cannot do any of that in MX.

[sQeetz]

I can do that in Logic and add the 16 assignable parameters and having them ready by just hitting 'B' on the keyboard

[aMUSEd]

Well you can but just not with anything other than the macros - I can see why that is a problem for you but I quite like the fact that my 16 macro Bitwig device panel for MX basically auto maps for every preset (although frustratingly most sound designers for MX presets only tend to use 8 of them) - I suppose the ideal would be to have synth macros and mappable params, doesn’t have to be an either/or thing. Or maybe what Omnisphere does where there are no fixed params, the user decides which ones to make available to the host (basically because there are so many it wouldn’t be practical to have them all fixed in advance)

[sQeetz]

Well you can but just not with anything other than the macros -

I don't get how this is a problem

[aMUSEd]

Well you can but just not with anything other than the macros -

I don't get how this is a problem

Was responding to previous post

[zzz00m]

Let's assume you want to automate filter cutoff. Just assign Filter Cutoff to one of the 16 macros and automate that.

Wouldn't you need to edit/update every preset that you wished to have a specific parameter assigned to a macro?

Or am I misunderstanding how the macros act on a per-preset basis?

For example, when I look at a number of factory presets, I can see that many of them already have Cutoff mapped to macro #3, but not all do. Some presets have macro #3 mapped to a different parameter.

And if I try to link parameters from the host, the only ones that I can see are what a specific Massive X preset exposes to the host, i.e., the current macro assignments.

[sQeetz]

Was responding to previous post

Nice. Hug?

[chk071]

Let's assume you want to automate filter cutoff. Just assign Filter Cutoff to one of the 16 macros and automate that.

Wouldn't you need to edit/update every preset that you wished to have a specific parameter assigned to a macro?

Or am I misunderstanding how the macros act on a per-preset basis?

No, that's how it works.

[sQeetz]

And if I try to link parameters from the host, the only ones that I can see are what a specific Massive X preset exposes to the host, i.e., the current macro assignments.

How much different would it be from a plugin you would have to hunt down the parameter you want to automate?

[pdxindy]

I can do that in Logic and add the 16 assignable parameters and having them ready by just hitting 'B' on the keyboard

You can only do that with the Macros. And every preset will have different parameters controlled by the Macros. It only works per preset. If you want Macro 4 to always control Cutoff, you would have to edit every single f**king preset one by one.

In contrast, I can take a synth like Bazille, add a Remote Page (make that Page default) and have the ADSR of the Amp Env for the first 4 knobs and Filter Drive, Cutoff, Env Amount and Resonance with the next 4. Once done, every time I add an instance of Bazille, it just works and across all presets. The 8 knobs on my midi controller always by default control the same parameters. No need to even look at the screen.

MX is like the freakin dark ages!

[zzz00m]

And if I try to link parameters from the host, the only ones that I can see are what a specific Massive X preset exposes to the host, i.e., the current macro assignments.

How much different would it be from a plugin you would have to hunt down the parameter you want to automate?

I'm not really looking at it from an automation perspective.

Rather for live playing from a MIDI controller. For example if I want my knobs to control the same parameter for ANY Massive X preset that I call up, such as ADSR, cutoff, resonance, etc. I don't understand why NI chose to make that so difficult.

[sQeetz]

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

[chk071]

And if I try to link parameters from the host, the only ones that I can see are what a specific Massive X preset exposes to the host, i.e., the current macro assignments.

How much different would it be from a plugin you would have to hunt down the parameter you want to automate?

I'm not really looking at it from an automation perspective.

Rather for live playing from a MIDI controller. For example if I want my knobs to control the same parameter for ANY Massive X preset that I call up, such as ADSR, cutoff, resonance, etc. I don't understand why NI chose to make that so difficult.

I was guessing a while ago that they wanted to tailor it to Komplete Kontrol, which would explain why they only have 16 macros, instead of having pages and pages of parameters in Komplete Kontrol, and the absence of a preset browser.

Of course, it could also be that it's simply another functionality which wasn't properly implemented.

You know, Massive X is a gem, but, it's a bit rough on the edges. Kind of like Spire.