Massive X: Status/Future?

No mystery here folks.

MX apparently doesn’t run on AS.
I wish it did. I hope it does soon.
It’s a great synth, but AS is the future of my rigs, so there’s no point in me investing any more time on MX until there’s an assurance that NI will make that happen.

It’s their prerogative not to, but I’ll be learning on a different synth in the meantime.

 

AS support is definitely happening, rest assured.

 

Not addressing anyone, but, it's kinda funny. People talk so much about stress in their daily job, and how it eats them. Yet, when they buy a NI product, all has to be done, yesterday. Well... I'm sure especially in Corona times, they have as many problems with manpower as any other company out there as well.

I'm not directly affected by lack of M1 support, but, it'd be nice to have some patience. I'm sure they work with all they have on it already (meaning everyone who is involved in Massive X development, of course).

 

No, I do not know him.
I guess it is #1 for 99%. Sort of joke....

 

Bit not f it’s too much work / time for you.

 

That’s great news. Cheers.

 

I can assure that we'll have to make sure all our products are compatible with AS sooner or later. Software developer can't really ignore the entire Apple ecosystem and Silicon is a huge part of it.

 

I started this thread FIVE MONTHS ago.
NOTHING has happened since then. Nothing noticable, that is.
It`s so lame.
It`s so frustrating.
Reading all the other threads created since then with basically the same topics (and answers) is so frustrating.
People arguing pros and cons, mostly ending up justifying why it´s necesessary or not to defend the way NI approaches the current issues, having to weigh one´s words... Reading all those disputes without a result is just frustrating.
Waiting is frustrating.
NI STILL not being able to communicate a schedule for the addressed issues is frustrating.
NI STILL not being able to communciate a schedule for the issues that stand in the way of resolving the addressed issues is frustrating.
It feels as if there is no plan.

I started this thread FIVE MONTHS ago.
Massive X was on the way to turn 2 years old by then. Now it´s older, and nothing has happened.
It´s sad. It´s frustrating.

 

There is no issue. Massive X works on CPUs it is designed for, and does not work on CPUs it is not designed for.

You know nothing about SW development. Things may be simple or not so simple. Five months is nothing in SW development.... Just testing and tuning may take several months.... Anyway it looks like Rosetta 2 version of Massive X might come soon.....

 

I know that...
...Massive X's browser was and still is pathetic.
...Massive X exists for over 2 years now with no real progress (even if my thread is 'only' 5 months old).
...Apple is an issue for me, because they are dictating NI's schedule in a way that NI are not able to communicate a roadmap to their users for native product development.
...Massive X is advertised - still in the user manual - by "MASSIVE X will grow, adapt, and evolve with regular updates". That has not been not true for a long time now, and that is very disappointing. And the user still hasn't got any hint if and when this might change.
...I'm repeating myself over and over against people who a) either tell me I don't have a clue, b) don't tell me anything precise or c) don't reply at all.
And I know that...
...I have paid money for all that.

It's frustrating.
I might not understand much of software/hardware development, but it obviously sucks nowadays. And it' s more and more at users' expense.
But please don't tell me on which levels I'm wrong, please tell me something constructive instead.

 

NI doesn't publicly share roadmaps, they kinda never did. And there are very good reasons for not doing that.

 

Yes, EvilDragon, you have told us so before. And that's both frustrating as well, because a) NI appear not to have any roadmap to share (guesstimates), and b) you have something to say about everything, whether helpful or not. Constructive, please!
This is all so annoyingly sticky...

 

IMHO NI has very limited development ressources.
Am I frustrated? NO! I take what works - and that's a lot - and leave anything else behind.

Concerning synths there are many very good alternatives mith MPE support and every state of the art feature one could require. AND they are developed constantly, e.g.

https://surge-synthesizer.github.io/

https://vital.audio/

 

They of course do have internal roadmaps. They just choose not to publish them. And that's entirely within their right.

 

DeepThumb: Thank you! I know there's other very good synths out there, and I use quite a lot of them, but in my opinion Massive X is among the very best, soundwise as well as concerning options, and it's a shame that it has such a hindering preset organisation, and that there's lacking time and power to progress their flagship synth to future realms.

EvilDragon: I said "appear" . I can imagine NI work by a plan. Your comments aren't helpful.

 

Neither is your constant repeating of the same exact thing.

 

If repeatedly raising my voice just ebbs away ineffectively, then you're absolutely right.
And that is, eh?, frustrating.

I guess DeepThumb is right , it's time for leaving...
Very sad.

 

It is disappointing how long we're having to wait for support/updates for Massive X. It still has the clicking issue, still bugged preset browser etc. At least a sign they're working on these things would be cool.

 

EvilDragon, what are your suggestions on advancing the Massive X situation? Currently the only options I see for users like me is a) just waiting (still, and without knowing for how long) and b) reminding of the drawbacks here in this forum from time to time (which you call not helpful). Any ideas further than that?

Anyone from NI around here with some ideas or news?

 

It has been comunicated by NI person, that Rosetta 2 implementation should come soon (within weeks if no problem). And also that a new version will have better preset browser. So, that means it is confirmed neofitialy by NI, that NI works on it and that it is comming....

I would add, as computer programmer, that porting Massive X to Rosetta 2 or even AS is not simple task at all. The very inner workings of MX have to be revorked. :-( And so it needs hell of testing, testing, testing. There might also be performance issues. So, need for optimizing, optimizing and optimizing. And testing, testing, testing, again. It takes lots of time.

Would you prefer to have MX sooner but bugy and half functional? I guess no.