Upcoming in Massive X 1.1

Great news about the update (and manual!) coming this week. Looking forward to it!

 

Greetings. Will the 1.1 update released today or this week as stated before? Thanks

 

Just a quick update: the team is still busy with some last fixes on the 1.1 update and therefore it will only be released next week — same for the manual which is already including the 1.1 features. Apologies for the delay...

 

Delay and Masive X are intertwined forever. Not only because of the FX delay. I don't get it why a big company like Native doesn't know when a beta product is ready for the public. And it's not the first time it's delayed, so if I were the manager, I would make sure the product was beta tested a triljon times, before announcing an release update. Especially after all those prior delays.
It comes across as unprofessional. Just would like to know why, as a company, you're announcing a release you're not completly sure it's 100% working? (Just curious) Nontheless...........

I just bought Massive X, and I have to say I'm impressed. Not a logical "classical" synth layout. In my opinion it's rather complicated layout. So much options, which causes the layout to be complicated, but if you invest some time it's great. I'm eager to find out about the visual feedback. That's one option I really miss. Had to share this as a costumer which has bought more products from Native.

O and btw like the dark skin!

 

It’s the usual story. Some people ask for update news before any official announcement. Someone from the company give us some informal news, which is cool, but if there is any unlucky delay, people go angry about it. The delays for the official 1.0 release were another more serious thing, but latest news by Mick was not official. Unexpected things can happen. By reacting like this to his informal post, result will be you won’t have any news before official release day. You might prefer this, I don’t.

 

"but latest news by Mick was not official. Unexpected things can happen"

I know it's actually a teaser. Just to get people excited. But hey, after the prior Masive X delays, If I were the manager would totally commit to a time table. Deliver an actual product on time to your customers. Release news for an upcuming update when, as a manager, I knew the product could be released for certain in X days. Or maybe better. Product allready is costumer ready. Announce it and release it. Native instruments has to many examples of delays, not living up to their promises, not realizing multiple idears, where costumers were excited (can give you examples). Thats just my experience buying products of Native. Its the question how you communicate with your costumers in an respectfull way and making promisses happen on time. If I would be late on my job I would be fired. Costumers would be angry. And I can relate why they would be angry. Especially after all the delays prior. Native should know better. After this history should treat customers better. My two cents.

 

This is never a real thing in actual development world.

 

O so you're always missing your targets? I see. Resembles Native.
Point I want to make is that with the history of not delivering, as a company you cant be trusted. I would avoid that in all ways. As a software engineer/manager would try all my best to avoid the same mistake. But hey here we are. O and you also know that Native made more promises. Its just about the principle. If you want to start making things better the above would be a great startingpoint.

O btw love it you can say what's on your heart. Not deleting posts etc. Sad that the real developers never answer here. I really think it would make things better but hey, who am I, huh?

 

any word on standalone and nks support?

 

It already supports NKS? And what's not mentioned in the changelog in the first post is not the focus of v1.1.

 

Xmas time ?

 

Last, this or next year?

 

As a software developer, I've got a question - are you always hitting your targets?

 

As the manual is out, do we get the updated MX later today?

 

Yeah likely.

 

It's there

 

I see the Factory presets have been updated. Will any custom patches made from previous versions also have to ?

 

Custom patches are custom patches, they are not affected by factory library updates.

 

yes obviously, my thought was about 1.1 modifications that could require re-saving for full compatibility purposes. Anyway I will try as soom as I can get to my computer.

 

Nope, nothing like that is necessary. Old patches just work as they used to. Nothing changed in v1.1 regarding patch format or browsing etc.