KVR Audio

zzz00m · Post by **zzz00m** » Sun Jul 31, 2022 2:08 am

_leras wrote: Sat Jul 30, 2022 11:37 pm
zerocrossing wrote: Fri Jul 29, 2022 4:39 pm
DJ Warmonger wrote: Wed Jul 27, 2022 4:35 pm New Massive X expansions dropped today:
https://www.native-instruments.com/en/s ... c3f9ffcbbe

Kino and Fade are finally something that's not just a bunch of cheesy EDM presets for latest club hits.
I’ll buy a Massive X expansion when they decide to support the basic MIDI spec.
Ha ha good one.

You mean eight controls isn't enough for you?

I'm halfway house on this. Would be great to have the expected control over every parameter. But just having the eight macros is usually enough for most things.

True, but MIDI learn is always nice to have as well.

sQeetz · Post by **sQeetz** » Sun Jul 31, 2022 3:07 am

I'm also on the "you put what you want to control on the macros, which you can program to do whatever you want" camp... You have 16 of them. How much more do you want to automate?

zerocrossing · Post by **zerocrossing** » Sun Jul 31, 2022 3:42 am

_leras wrote: Sat Jul 30, 2022 11:37 pm
zerocrossing wrote: Fri Jul 29, 2022 4:39 pm
DJ Warmonger wrote: Wed Jul 27, 2022 4:35 pm New Massive X expansions dropped today:
https://www.native-instruments.com/en/s ... c3f9ffcbbe

Kino and Fade are finally something that's not just a bunch of cheesy EDM presets for latest club hits.
I’ll buy a Massive X expansion when they decide to support the basic MIDI spec.
Ha ha good one.

You mean eight controls isn't enough for you?

I'm halfway house on this. Would be great to have the expected control over every parameter. But just having the eight macros is usually enough for most things.

I’m mostly just hoping they support basic polyphonic aftertouch, but MPE would really be a treat.

sQeetz · Post by **sQeetz** » Sun Jul 31, 2022 3:48 am

zerocrossing wrote: Sun Jul 31, 2022 3:42 am I’m mostly just hoping they support basic polyphonic aftertouch, but MPE would really be a treat.

That would indeed be nice

_leras · Post by **_leras** » Sun Jul 31, 2022 5:50 am

zerocrossing wrote: Sun Jul 31, 2022 3:42 am I’m mostly just hoping they support basic polyphonic aftertouch, but MPE would really be a treat.

Yes, really it should have that and allow automation of parameters without needing a macro.

I said I was halfway house, but really... It's more accurate to say I can work with what is there, but would like it to work like most other synths.

Definitely a synth of ups and downs.

EvilDragon · Post by **EvilDragon** » Sun Jul 31, 2022 9:37 am

Most hosts will allow you to channel MIDI CCs through to host automatable parameters, tho...

pdxindy · Post by **pdxindy** » Sun Jul 31, 2022 2:18 pm

sQeetz wrote: Sun Jul 31, 2022 3:07 am I'm also on the "you put what you want to control on the macros, which you can program to do whatever you want" camp... You have 16 of them. How much more do you want to automate?

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.

I can only create a Remote Page that points to 8 macros, but the macros control different parameters when you change presets.

Every other plugin I have I can create Remote Pages that work consistently across all presets. I create a number of Remote Pages that cover the most common parameters and they are always available for every instance of the plugin. I may or may not use them for a given case and may just edit or automate, but they are always there, always the same which is fast as one develops muscle memory.

In a practical sense, MX doesn't work with midi controllers. MX is the ultimate in tedious.

sQeetz · Post by **sQeetz** » Sun Jul 31, 2022 3:10 pm

pdxindy wrote: Sun Jul 31, 2022 2:18 pm 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

pierb · Post by **pierb** » Sun Jul 31, 2022 6:58 pm

pdxindy wrote: Sun Jul 31, 2022 2:18 pm In a practical sense, MX doesn't work with midi controllers. MX is the ultimate in tedious.

I agree and it's probably because NI wants to steer users towards Komplete Kontrol and NKS.

Honestly it seems the only interest of NI is in making MX a player for official libraries.

pierb · Post by **pierb** » Sun Jul 31, 2022 7:00 pm

sQeetz wrote: Sun Jul 31, 2022 3:10 pm
pdxindy wrote: Sun Jul 31, 2022 2:18 pm 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

Huh?

Very often. Not only in Bitwig but any DAW that has macros like Live, Cubase, or Studio One.

sQeetz · Post by **sQeetz** » Sun Jul 31, 2022 7:04 pm

pierb wrote: Sun Jul 31, 2022 7:00 pmHuh?

Very often. Not only in Bitwig but any DAW that has macros like Live, Cubase, or Studio One.

So you program/map the stuff you want to have controlled via the 16 macros. I don't understand what the problem is.

chk071 · Post by **chk071** » Sun Jul 31, 2022 7:14 pm

"Limitations are an inspiration."

"Only 16 macros to automate."

Anyway, IMO, the inability to automate everything is a big omission as well. I'm still waiting for the big update which addresses all those things.

I'm really wondering how development of such synths work. Do they get a set budget for the development, then release, and then they get an extra tight budget, and work in their spare time on further improvements? Part time developers, hired for the specific job? I'd really be interested, because, it really seems like development would have had a major slow down after the release. I get that shitty Mac M1 native development takes lots of time, but, even with that, I would have expected some more updates and improvements.

Maybe MX suffers the most from M1 native development, as it makes use of specific CPU extensions, which aren't present in ARM chips.

pierb · Post by **pierb** » Sun Jul 31, 2022 7:14 pm

sQeetz wrote: Sun Jul 31, 2022 7:04 pm So you program/map the stuff you want to have controlled via the 16 macros. I don't understand what the problem is.

You don't understand the issue with not being able to have a DAW macro set to a fixed parameter in the synth (not a synth macro)?

sQeetz · Post by **sQeetz** » Sun Jul 31, 2022 7:15 pm

pierb wrote: Sun Jul 31, 2022 7:14 pmYou don't understand the issue with not being able to have a DAW macro set to a fixed parameter in the synth (not a synth macro)?

Apparently not. do explain. please

_leras · Post by **_leras** » Sun Jul 31, 2022 7:28 pm

sQeetz wrote: Sun Jul 31, 2022 3:10 pm
pdxindy wrote: Sun Jul 31, 2022 2:18 pm 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

That's just ADSR for filter and amplitude. Something pretty much every decent hardware synth has dedicated controls for.

So... A very normal thing to want to map.

Massive X 1.6.1 update (September 2025)!