Native Instruments Massive X Synth - Sequel to Massive (Out Now!)

[BDeep]

Another thing. The CPU usage is super nifty, unless I'm missing something. I can use 6 times unison, audio rate modulation, a poly pad, and it doesn't have nearly the impact on overall CPU that you might think.

[EvilDragon]

What's happened to Komplete Kontrol mapping - am I missing something?

There are only 2 pages in KK for Macros 1 -16, nothing else is mapped at all and many of the presets have a naming mismatch between the Macro name in Massive X and what's displayed in Komplete Kontrol and on the S61 screens. Did NI drop the ball on this - anybody else seeing the same issue?

You're not missing anything. 16 macros is all that's automatable.

Another thing. The CPU usage is super nifty, unless I'm missing something. I can use 6 times unison, audio rate modulation, a poly pad, and it doesn't have nearly the impact on overall CPU that you might think.

Yeah, there's been lots of optimizations at the end of the beta cycle. And AVX definitely helps, too.

[Vortifex]

Don't quote me on this but I don't think you can

WTF? That seems like a pretty big omission to me.

Not at all. It's a mono path up to the effects stage where it becomes stereo. To do otherwise would either force the modular signal path to be stereo which would double the CPU for all of the other poly modules, or complicate the path by making the modular environment stereo and then having the modules either default to mono with one connection or be stereo otherwise.

Icarus, Hive, Dune and Synthmaster manage it just fine. Ah well.

Edit: quoted wrong person but point is the same.

[Shoom]

I've been looking at people reviewing the beta version and it seems like a whole bunch of presets, like loads, have been removed since the beta. Even whole categories (Blip n Blop, Impact, Sweep n Swell, Zap etc) have vanished.

Anybody know anything about it? I know they said it would continue to be updated but it seems strange to remove stuff that was already there.

[Elektronisch]

Another thing. The CPU usage is super nifty, unless I'm missing something. I can use 6 times unison, audio rate modulation, a poly pad, and it doesn't have nearly the impact on overall CPU that you might think.

I did noticed that aswel, CPU usage is not too bad at all!

[yehboy1]

Blip n Blop is gone???

There goes my producer career.

[drdriller]

Speaking of CPU consumption... is it just me or is Massive X surprisingly... light? It doesn't chug much at all. Maxing at 64 voices will still just barely consume much at all. I wonder is there like a "HQ mode" that I'm missing or something?

yep cpu charge is far more light than expected, even on my old laptop (i7 4710u)

[Echoes in the Attic]

What's happened to Komplete Kontrol mapping - am I missing something?

There are only 2 pages in KK for Macros 1 -16, nothing else is mapped at all and many of the presets have a naming mismatch between the Macro name in Massive X and what's displayed in Komplete Kontrol and on the S61 screens. Did NI drop the ball on this - anybody else seeing the same issue?

You're not missing anything. 16 macros is all that's automatable.

Wow, even reaktor exposes all it's parameters (if you want them exposed). Massive X just hides everything but the macros? That sucks.

[EvilDragon]

What's happened to Komplete Kontrol mapping - am I missing something?

There are only 2 pages in KK for Macros 1 -16, nothing else is mapped at all and many of the presets have a naming mismatch between the Macro name in Massive X and what's displayed in Komplete Kontrol and on the S61 screens. Did NI drop the ball on this - anybody else seeing the same issue?

You're not missing anything. 16 macros is all that's automatable.

Wow, even reaktor exposes all it's parameters (if you want them exposed). Massive X just hides everything but the macros? That sucks.

Did you ever automate 30 parameters at once from a single plugin in the same track? Like, honestly.

Reaktor also has a limit on how many automation parameters can be reported (1000, IIRC). I guess they wanted to keep it simple here for majority of people? Not sure. Either way I don't see this as a huge detriment. A good setup of macros goes a long way.

[mholloway]

Yeah, every YT video I watch seems to have a different set of categories in the Preset Browser....not sure what's up, and can't download until after work today.

[Functional]

You're not missing anything. 16 macros is all that's automatable.

Wait, what? I mean, in Cubase at least everything seems automatable.

[karrikuh]

Speaking of CPU consumption... is it just me or is Massive X surprisingly... light? It doesn't chug much at all. Maxing at 64 voices will still just barely consume much at all. I wonder is there like a "HQ mode" that I'm missing or something?

Can confirm. My initial tests suggest it might be one of the most efficient synths currently in the market. No comparison to Serum, Pigment and the likes.It might even beat Massive 1 in terms of efficiency!
Only bummer is the RAM usage (300-400 MB per instance). Hope they can improve on this (e.g. by sharing resources between instances)

[jeffb01]

None of the wavetables or noise tables are available in my demo, is this a bug or is that how the demo is?

no. You're having a problem with the additional stuff. Rescan Presets again - just do it. when that's done, close Massive X and reopen it.

Already did that twice and nothing happened, did it a third time and it worked. Ah well, temporary gremlin.

I'm having the very same issue, unfortunately rescan didn't help in my case. tried it at least a dozen times, including uninstalling/reinstalling MX. My setup: Massive X Demo, Win10, REAPER.

I verified that the content is located in
C:\Program Files\Common Files\Native Instruments\Massive X
(it contains Wavetables, Noistables etc. folders)

A registry entry ContentDir is present in
HKEY_LOCAL_MACHINE\SOFTWARE\Native Instruments\Massive X
and points to this directory.

Anybody else experiencing this?

Content directory doesn't contain factory presets. Have you installed the MX factory library? It's a separate download.

The issue is about wavetables/noisetables, not presets! The presets are there

I kind of did. I had to click rescan presets. then wavetables were there, but not noises, so I had to hir rescan presets again. Just click on "rescan presets" again. let it do it's thing, close your daw and reopen. rinse and repeat. don't reinstall because then it's starting all over again. definitely a 1.0 release.

[EvilDragon]

You're not missing anything. 16 macros is all that's automatable.

Wait, what? I mean, in Cubase at least everything seems automatable.

How do you mean "everything"? Only 16 parameters (the macros) are reported to host for automation.

[Functional]

Speaking of CPU consumption... is it just me or is Massive X surprisingly... light? It doesn't chug much at all. Maxing at 64 voices will still just barely consume much at all. I wonder is there like a "HQ mode" that I'm missing or something?

Can confirm. My initial tests suggest it might be one of the most efficient synths currently in the market. No comparison to Serum, Pigment and the likes.It might even beat Massive 1 in terms of efficiency!
Only bummer is the RAM usage (300-400 MB per instance). Hope they can improve on this (e.g. by sharing resources between instances)

Yeah seems to be the same here, 300-400mb per instance but I can live with that personally. I seldomly use all that much RAM, in fact it's usually Chrome and 200 pages open that chug it