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

[perpetual3]

Sure there is stuff that's not finished yet, that alone is obvious. That does NOT make it alpha software - alpha versions usually don't even have the GUI sorted out. You should've seen the early beta version Also, I can't honestly remember a lot of plugins (if any?) that were just released as v1.0 and being feature complete, without having a single non-bugfix update.

ED, graspee does have a point. I can’t recall you agreeing with a single criticism about MX. Even if it is a 1.0 program, that standing alone doesn’t inoculate MX from criticism. Of course, you may not find anything deficient about the synth, or find that the pros outweighs the cons sufficiently so to render those deficiencies so negligible as to be unworthy of criticism. But it does seem odd.

Do you find anything deficient about MX? Anything disappoint you? What don’t need you like about it? You’re extremely helpful and very knowledgeable, so a critique coming from you would be more significant than someone like me, for instance.

[EvilDragon]

BTW, i noticed that there are some phasing issues when i add a insert FX oscillator. Are those phase retriggered by default? And... can i set them to free running as well?

Phase related stuff is in Voice tab, Engine Setup, but I think those oscillator phases are only valid for the dual wavetable. Not sure.

[Stefken]

Sure there is stuff that's not finished yet, that alone is obvious. That does NOT make it alpha software - alpha versions usually don't even have the GUI sorted out. You should've seen the early beta version Also, I can't honestly remember a lot of plugins (if any?) that were just released as v1.0 and being feature complete, without having a single non-bugfix update.

ED, graspee does have a point. I can’t recall you agreeing with a single criticism about MX.

Yep. That's biased right there.
In my language they say: Who's bread you eat, his words you speak. Well, to be fair, they say: "Wiens brood men eet, diens woord men spreekt", but I don't think most people around here would understand this.

[EvilDragon]

Sure there is stuff that's not finished yet, that alone is obvious. That does NOT make it alpha software - alpha versions usually don't even have the GUI sorted out. You should've seen the early beta version Also, I can't honestly remember a lot of plugins (if any?) that were just released as v1.0 and being feature complete, without having a single non-bugfix update.

ED, graspee does have a point. I can’t recall you agreeing with a single criticism about MX. Even if it is a 1.0 program, that standing alone doesn’t inoculate MX from criticism. Of course, you may not find anything deficient about the synth, or find that the pros outweighs the cons sufficiently so to render those deficiencies so negligible as to be unworthy of criticism. But it does seem odd.

Do you find anything deficient about MX? Anything disappoint you? What don’t need you like about it? You’re extremely helpful and very knowledgeable, so a critique coming from you would be more significant than someone like me, for instance.

I have mentioned things that I'd like to see in MX (that I consider as unfinished) - I have agreed that browser is incomplete, but apart from that, being able to lock PB range globally, add MPE, constant rate glide mode (this is what I miss the most, weirdly enough - OG Massive had the option)...

As I said, it is evident it's not "finished", whatever that means these days when everything is a rolling release. But NI stated early on it's going to be a long-term project with stuff being added as we go along - and that's alright, too.

[McLilith]

It's not false. Beta is feature complete but may have bugs. What we have been given is not feature complete therefore it's alpha.

Wrong. Features can always be added during the lifetime of the product. Zebra 2 had a bunch of updates in 10+ years it's been around, for example. In modern times, there's no such thing as "feature complete" really.

Quite true.

I'd like to add, we're not the people who dictate the feature set for a version 1.0.0 release of Massive X — or any other piece of software. Only the developers get to decide that, and they've decided the current feature set is satisfactory for a version 1.0.0 release. By definition, it's "feature complete" for this iteration. Those of us not on the Massive X development team can always create a wish list of features we'd like to see added in the future, but that doesn't mean version 1.0.0 is incomplete.

Also, it's quite normal for additional features to be added to a piece of software in subsequent versions. That also doesn't make the initial public release a beta version, let alone an alpha version.

[EvilDragon]

I'd like to add, we're not the people who dictate the feature set for a version 1.0.0 release of Massive X — or any other piece of software. Only the developers get to decide that, and they've decided the current feature set is satisfactory for a version 1.0.0 release. By definition, it's "feature complete" for this iteration. Those of us not on the Massive X development team can always create a wish list of features we'd like to see added in the future, but that doesn't mean version 1.0.0 is incomplete.

Also, it's quite normal for additional features to be added to a piece of software in subsequent versions. That also doesn't make the initial public release a beta version, let alone an alpha version.

Both of those paragraphs are exactly the point I was trying to make. Just because it doesn't have your fav feature at v1.0 doesn't make it "alpha".

[chk071]

BTW, i noticed that there are some phasing issues when i add a insert FX oscillator. Are those phase retriggered by default? And... can i set them to free running as well?

Phase related stuff is in Voice tab, Engine Setup, but I think those oscillator phases are only valid for the dual wavetable. Not sure.

Yeah, that's what i figured as well.

Anyway, guess i can always set all phases to retrigger, and then set the phase for each oscillators, to circumvent the phasing.

[Stefken]

In modern times, there's no such thing as "feature complete" really.

But there is such a thing as having basic functionality expected @2019.
Like, ADSR curves that actually move instead of a static image.

[chk071]

Well... if there's a positive bias, then there's surely also a negative bias.

[kvr235]

Great stuff! Enjoyed it. Thanks for sharing.

Regarding the sound, Massive X does sound more new/modern/different/awesome than original Massive, so I think NI have done an excellent job at it.

Thanks! I feel with the new noises especially, you can make some pretty "organic" sounding sounds that were hard/impossible to get out of the original massive.

I like it. Is this pure Massive X, or do you also have some other instruments / effects in the track?

Thanks!

drums are ezdrummer,

all other instruments+fx are massive x.

gullfoss as a lazy eq, townhouse comp, elephant on lr.

[midi_transmission]

One thing that come to mind with the whole MX release. I think it gets a lot of criticism because it was advertised as the next big thing. So the expectations for a 1.0 were quite high by this.

[EvilDragon]

But there is such a thing as having basic functionality expected @2019.
Like, ADSR curves that actually move instead of a static image.

u-he synths also don't have moving images for ADSR envelopes (well, only Hive 2 can show something via the scope, but that's a bit different), I don't see you bitching about it

[Stefken]

This is also an old saying in my language:

[midi_transmission]

But there is such a thing as having basic functionality expected @2019.
Like, ADSR curves that actually move instead of a static image.

u-he synths also don't have moving images for ADSR envelopes (well, only Hive 2 can show something via the scope, but that's a bit different), I don't see you bitching about it

But hive was not anounced as the I quote NI here 'NEXT-GENERATION FLAGSHIP SYNTHESIZER '

[EvilDragon]

And is there a law somewhere that a "flagship synthesizer" should have animated ADSR graphs?