N.I. Kontakt goes VST3
-
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
MX doesn't have tech debt since it is a newer plugin, of course. Although, two different teams worked on it (one in-house, the other was Lechtal Audio, Mike Daliot's company who did all the DSP). And it has been maintained and received bugfixes since release. And it will continue to be maintained.
-
- KVRist
- 128 posts since 19 Jun, 2021
You have to understand I was such a fan of it until the updates stopped at 1.3 and my faith just plummeted.
This is from the NI forums:
This is from the NI forums:
Matt @ NI wrote:It sounds like we had high aspirations when we released it. When looking at the release date, they seem to have been cut short by pretty big internal changes. Appreciate the feedback and to be fully transparent, I'm not sure we'll have a lot of these features coming super soon considering we need to address compatibility on Mac first.Lucas Howden wrote: Massive X has once been advertised like this: "As you might know already, a big part of Massive X is its continued development – the introduction of new features, parts, and so on in the future.“
-
- KVRAF
- 26931 posts since 3 Feb, 2005 from in the wilds
NI is maintaining MX...attention ♥ wrote: Fri Jul 09, 2021 5:23 pm As nice as this is to see, NI not being able to maintain Massive X has made me worried.
At this point the problem seems bigger than just old codebases, as Massive X is brand new.
The real issue is that NI is currently not capable of making an all around world class synth. According to EvilDragon above, NI outsourced the DSP coding for Massive X. I didn't know that, but it is obviously correct as the DSP of MX is top notch and the rest of the infrastructure is quite bad. Even though MX was touted as next generation tech, it went backwards in various ways from the original Massive and standard capabilities most synths have. No midi learn, no direct parameter automation, etc. MX does not support PolyAT even though original Massive did. No user preset organization at all. Etc.
As you say, the problem is not just old codebases.
-
- KVRian
- 849 posts since 11 Mar, 2010
I wonder if NI may decide to jump into MX2 altogether... By the time these supposed updates may surface, MX will be several years old (it already is), and these updates probably won't help putting it (and NI) in the spotlight again.
-
- KVRAF
- 35671 posts since 11 Apr, 2010 from Germany
They didn't though. https://www.native-instruments.com/foru ... -2.359895/attention ♥ wrote: Sat Jul 10, 2021 12:59 pm You have to understand I was such a fan of it until the updates stopped at 1.3
-
- KVRAF
- 35671 posts since 11 Apr, 2010 from Germany
Woot?... Why?
MX is a mere 2 years old.-
- KVRAF
- 1863 posts since 11 Apr, 2008
The question is what it means "maintained". Is it a full team working on it full-time or it's just one guy working on it afterhours? It feels like in case of MX it's the latter, unfortunately.
Except if MX is so convoluted and badly written that even team of developers are unable to bring more than tiny updates every few months. But I don't believe that this is the case here.
Another case can be that the company is so badly managed that developers don't even know what's going on (like Cyberpunk 2077 was screwed if I had to compare to gaming industry).
Like in comparison, Arturia must have million developers working on Pigments, when you compare amount of changes they did between version 2 and 3 in the same timeframe.
Except if MX is so convoluted and badly written that even team of developers are unable to bring more than tiny updates every few months. But I don't believe that this is the case here.
Another case can be that the company is so badly managed that developers don't even know what's going on (like Cyberpunk 2077 was screwed if I had to compare to gaming industry).
Like in comparison, Arturia must have million developers working on Pigments, when you compare amount of changes they did between version 2 and 3 in the same timeframe.
-
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
So just to drive the point home: Lechtal Audio is Mike Daliot's company, and Mike Daliot is the main developer and creator of OG Massive. So, despite "outsourcing DSP", it was actually in a round-about way done by NI from a decade ago. Time traveling shenanigans.pdxindy wrote: Sat Jul 10, 2021 1:48 pmAccording to EvilDragon above, NI outsourced the DSP coding for Massive X. I didn't know that, but it is obviously correct
-
- KVRian
- 849 posts since 11 Mar, 2010
Sure, but I bet it'll at least 3 years old when a big update arrives. I wonder, given how competitive this market has become, if wouldn't be smarter to just release it as version 2. Just look at Pigments!
-
- KVRian
- 849 posts since 11 Mar, 2010
Wait, that's your opinion. I don't agree with that.
-
- KVRAF
- 35671 posts since 11 Apr, 2010 from Germany
Speculations.Sinisterbr wrote: Sat Jul 10, 2021 2:31 pmSure, but I bet it'll at least 3 years old when a big update arrives.
-
- KVRian
- 849 posts since 11 Mar, 2010
Yeah, maybe you're right, and it won't take that long. Still, I stand with what I said. Look at how Pigments soared, as Arturia kept a steady pace of big releaseschk071 wrote: Sat Jul 10, 2021 2:33 pmSpeculations.Sinisterbr wrote: Sat Jul 10, 2021 2:31 pmSure, but I bet it'll at least 3 years old when a big update arrives.
-
- KVRAF
- 24405 posts since 7 Jan, 2009 from Croatia
Piments could use a very solid dose of CPU optimization
-
- KVRAF
- 1863 posts since 11 Apr, 2008
Yeah, maybe read to the end of paragraph before you comment back
-
- KVRAF
- 1863 posts since 11 Apr, 2008
True