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

[chk071]

I announce myself as "The next big thing" since years. And look where i still am.

[Stefken]

See my picture above.

[ghettosynth]

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.

I don't want to argue about this forever because it's obvious you won't change your mind but just because there are alphas that are less finished does not make massive X not alpha and just because lots of synths have stuff added to them after release does not make massive X not alpha.

Your definition of beta is not widely accepted. Fundamentally, the difference is more about the testing environment, where it is tested and who does the testing. Is there reason to complain about unfinished features, yes, but, that doesn't automatically make it "alpha" software because the Wikipedia page asserts that the software must be "feature complete."

Here, from techopedia, not necessarily a definitive authoritative reference, but it conveys some key ideas about "beta testing."

In the end, beta testing and how it is done has much to do with whoever is handling the development process. The same cannot be said for alpha testing, which is still internal and housed under a conventional engineering workflow. That said, there is an element of beta testing that is more “PR” or consumer-facing than exclusively focused on testing criteria. This can be seen in the gaming world, where a “beta phase” may function as a way to let audiences play around with game mechanics, get used to characters and preview other features.

Now, if you want to argue that this appears to be the product of a rushed testing and release process, I would agree. I would label this as maybe an RC1 that needs two or three more phases prior to release. But I think that you are using a very lay understanding of alpha and beta to try and make a point. There is no widely and commonly accepted definition of what level of feature completeness is necessary for alpha vs beta, the terms are about process.

[pdxindy]

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.

I don't want to argue about this forever because it's obvious you won't change your mind but just because there are alphas that are less finished does not make massive X not alpha and just because lots of synths have stuff added to them after release does not make massive X not alpha.

I think these days the terms Alpha and Beta software are less distinct. For example, MX seems pretty solid in terms of bugs... and the sound engine seems complete... but it does seem 'alpha' like in other areas. The browser seems like something thrown in there just to have anything. It barely constitutes a browser. The search is missing, no favorites, no tagging etc. The envelope graphics are mere placeholders. No midi learn.

It is true these days that nothing is ever really feature complete. However, there is a difference between that and having obvious missing or incomplete functionality. For example, Valhalla Delay, u-he Twangstrom are a couple recent 1.0 releases that are solid and ready to go. There are others.

[vurt]

This is also an old saying in my language:

are you a freemason?

[midi_transmission]

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

You get the point... It's always the same when you have a big marketing department. That why I prefer the communication from smaller engineer focused organisation usually.

[ghettosynth]

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

You get the point... It's always the same when you have a big marketing department. That why I prefer the communication from smaller engineer focused organisation usually.

Cmon ED, even Nick Batt of Sonicstate made the same point that I did referring to the static envelopes as something that you'd expect on a DX7. I truly hope that is part of a planned update, at the moment it's almost funny.

[Reefius]

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.

I do

[EvilDragon]

Yeah I'm pretty sure there's gonna be more visual feedback down the road, but let's see.

[pdxindy]

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

They also don't take up 10% of the GUI with useless and static envelope graphics

[Vortifex]

Yeah I'm pretty sure there's gonna be more visual feedback down the road, but let's see.

What makes you sure about that?

[EvilDragon]

Just a hunch. Also, NI is very much following these diatribes

[Stefken]

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.

I do

Hello amigo.

[vurt]

Just a hunch. Also, NI is very much following these diatribes

in that case


cup holder!

[mladi]

At least he didn't said MX is pre-Alpha.