Login / Register 0 items | $0.00 New @ KVR
Massive XbyNative Instruments

User Reviews by KVR Members for Massive X

Rate & Review Massive X Now!

Reviewed By Ficciones [read all by] on 13th July 2019
Version reviewed: 1.0 on Mac.
Last edited by Ficciones on 26th July 2019.
2 of 7 people found this review helpful.
Was it helpful to you? Yes No

Edit: I've spent even more time with Massive X, working around the poor GUI performance on Mac, and I have to say, the sound is top notch. In particular, it growls and grunts and rasps in a way that maintains its character when pushed to extremes, where other synths would dissolve into white noise and buzzing. And in less extreme settings, the sound still has a certain je ne sais quoi, a dimensionality that is hard to put your finger on but is nonetheless there. Sorry if that sounds like audiophile voodoo. I doubt it's an illusion on my part, because my initial response to the synth was overwhelmingly negative. I'm going to let most of my old review below stand because IMO the criticisms are valid and not nitpicks. Raising my rating though, in light of the great sound engine and in expectation of some nice updates.

Here's what I don't like:

- It handles like a cow. It's awkward and sluggish.

- it uses huge amounts of CPU on Mac when the GUI is displayed. I think this is the first Mac product from NI that uses retina resolution, and it appears they have some work to do in the optimization department. In the meantime I run it at 50% size, which helps.

- it's obscure. Nothing is obvious. Very poor ergonomic design, compounded by the lack of a manual.

- the GUI looks tired. It's full of wasted space, and paradoxically manages to look empty and cluttered at the same time. And it also makes me think that this is fundamentally a polyphonic Reaktor blocks ensemble with the hood welded shut. That could explain the performance issues, compared to the first Massive which looks to have been coded from the ground up.

- You can't import wavetables.

- The "switcher" LFO clicks when it's switched. Whaaaaa...? What... is the point??

- Want to map a MIDI controller to a control? Forget about it, you have to map it to a macro and then map the macro to a control. Why??

What are the good points? Well, hopefully my criticisms can be addressed in updates. And the sound is very, very good. It'll do that skronky womp womp post-dubstep EDM thing that people will want to use it for, and more.

Looking forward to raising my rating when the updates drop.

Click here to read all 3 reviews



Discussion: Active
30 June 2019 at 9:52pm

It may be great, however I would give Native Instruments ZERO stars for the tiny notice of Massive X being AVX dependent. And what is AVX anyway? Try finding out if your CPU is AVX or not or to find any information on upgrade CPU with AVX suitable for your computer. The great workhorse MAC Pro 2009-2013, the only module built MAC up til comming fall, does not have AVX. I guess many people are pissed by Native almost hiding the limit information of Massive X. Just before Massive X was released Native started a marketing campain for upgrading Komplete. The new Massive was one of the most focused selling points in the campain. You really need to look hard to find any information on the AVX limit. I know techonolgy moves ahead and sooner or later there will come a product that your old computer cannot handle, I do however question Natives marketing moral and I also question how the Native standing is the MAC Pro community these days.

1 July 2019 at 2:03am


Thanks for the heads up, that's good info.

I have one of those old Mac Pro's, actually mine is even older, 2008 (just collecting dust). However I have a 2011 iMac core i5 and it supports AVX. The iMac was a hold over until they released another tower, but the new Mac Pro's are too expensive. I can see how people would be upset, then again those are pretty old.

2 July 2019 at 8:48am

I've added that criticism to my "bad points" list.

15 July 2019 at 7:38am

Get used to it, AVX is going to become the norm. The latest DUNE update requires it, too, and others will follow.

15 July 2019 at 8:06am

Nope. Dune 3 (and previous Dunes) runs ok on non AVX CPUs. I may run better with AVX but it does not depend on AVX to run. Same as a couple more instruments. They run on both AVX and non AVX CPUs. Massive X is, as far as I know, the first to run ONLY on AVX. I do not mind Native developing products for the future, and I see that at a given time old computeres will not be able to run new products. I am totally fine with that. What I however think is not very good customer service is not to give proper information during a heavy upgrade marketing campain where MX was one of the selling points. It is right that there is a sentence there telling it requires AVX, but who knows really the impact of that sentence? And if you have stumbled accross the term before and bought or downloaded anything that had AVX in the specs, your experience would be that is does in fact run, giving the term AVX no further worry. Native is using their mail database for the campain and it would be of almost no effort to send out a kind of warning to the huge community of MAC Pro users that MX will not run on their computer, or at least add the word "Only" in the AVX sentence. As it was a lot of people feel fooled. Native is, with the sentence they added to the specs "lawfully protected", but as for customer service it is way under acceptance.


Please log in to join the discussion

Massive X

Average user rating of 4.67 from 3 reviews

Native Instruments
 My KVR - Version Control & Lists
Not In Your MY KVR Groups
(or group limitation prevents versioning)
32 people have added Massive X to 4 My KVR groups 38 times

KVR Rank (Based on page views)

Overall: 85  65  85

30-Day: 201; 7-Day: 294; Yesterday: 429

KVR Audio Plug-in Marketplace