Massive X 1.6.1 update (September 2025)!

[Vortifex]

Edited

[Sinisterbr]

Anyone find that clicking the down arrow to go to the next preset often makes it go back to the very first preset instead?

Yes, every time I'd close the MX window and open it again, it'd behave like that. It's really annoying, as I like to cycle through presets a lot (and one of the reasons I wouldn't use MX as much as I'd like).

[LoveEnigma18]

At least until Massive X gets a better browser, I'd suggest using it inside Komplete Kontrol. I use it that way and can also favourite presets and search/filter them better there. I hope this will also avoid the problem you guys have described here.

[nirm123]

Anyone find that clicking the down arrow to go to the next preset often makes it go back to the very first preset instead?

Yes, every time I'd close the MX window and open it again, it'd behave like that. It's really annoying, as I like to cycle through presets a lot (and one of the reasons I wouldn't use MX as much as I'd like).

that drives me crazy !!!

Ive been complaining about 1 year first in the relevant NI massive x forum, tried to open two cases, never got an answer.

it's an amazing and inspiring synth but also very frustrating.

[telecode]

FWIW.. I bought into Komplete last year because of the Massive X release. tbh ... I never use it. The interface is too convoluted. I defer to the old Massive much more.

[telecode]

FWIW.. I bought into Komplete last year because of the Massive X release. tbh ... I never use it. The interface is too convoluted. @Evil.. I think NI should look at doing some more work on the Massive X GUI.

[Sinisterbr]

Oh, I disagree completely. I absolutely love MX GUI, despite some small practical issues. These NI graphic designers have a great taste, IMO.

[Sinisterbr]

Anyone find that clicking the down arrow to go to the next preset often makes it go back to the very first preset instead?

Yes, every time I'd close the MX window and open it again, it'd behave like that. It's really annoying, as I like to cycle through presets a lot (and one of the reasons I wouldn't use MX as much as I'd like).

that drives me crazy !!!

Ive been complaining about 1 year first in the relevant NI massive x forum, tried to open two cases, never got an answer.

it's an amazing and inspiring synth but also very frustrating.

Yeah, it's deeply frustrating, and I'm surprised how few people did complain about it (even in NI forums), AFAICS.

[dayjob]

recently updated. it sounds fantastic. haven't spent lot's of time w/it yet but so far so good. browser is weird.
wondering how apple silicon will affect it and all other software that require AVX compatible processor. not that i'm going that route any time soon/ever. I know nothing about the M1 apple silicon processor but i'm guessing it has none of that AVX business in its instructions. gonna be a fun ride for devs.

oh, found an article about that.

https://liliputing.com/2020/11/rosetta- ... chips.html

Some newer instruction sets and processor features including AVX, AVX2, and AVX512 vector instructions are also untranslatable.

more info at apple's developer site

https://developer.apple.com/documentati ... nvironment

[v1o]

recently updated. it sounds fantastic. haven't spent lot's of time w/it yet but so far so good. browser is weird.
wondering how apple silicon will affect it and all other software that require AVX compatible processor. not that i'm going that route any time soon/ever. I know nothing about the M1 apple silicon processor but i'm guessing it has none of that AVX business in its instructions. gonna be a fun ride for devs.

oh, found an article about that.

https://liliputing.com/2020/11/rosetta- ... chips.html

Some newer instruction sets and processor features including AVX, AVX2, and AVX512 vector instructions are also untranslatable.

more info at apple's developer site

https://developer.apple.com/documentati ... nvironment

Apparently ARM's Neon instructions can do alot of the AVX stuff. It just has to be completely rewritten.

[EvilDragon]

There are libraries out there, like SIMDe which make translating SSE/AVX to Neon very easy without any huge rewrites. This was done for Surge, so it can run on ARM (Raspberry Pi, for example, but it will be ready for ARM Mac as well).

[ScrLk]

There are libraries out there, like SIMDe which make translating SSE/AVX to Neon very easy without any huge rewrites. This was done for Surge, so it can run on ARM (Raspberry Pi, for example, but it will be ready for ARM Mac as well).

It does not promise no performance penalty for translated code. ARM for music production will cause fragmentation and steps back in performance for heavier plugins (read: not Pro-Q).

It will be worth it for Apple, but it will only cause more busywork for developers. As for end users, it will probably benefit unplugged laptop producers most.

[EvilDragon]

Obviously if the instruction doesn't exist on the CPU it cannot be done without some conversion into multiple matching commands, but that should be a given. What's more important is that your code will still run regardless, even if it incurs some minor penalties.

[simon.a.billington]

At least until Massive X gets a better browser, I'd suggest using it inside Komplete Kontrol. I use it that way and can also favourite presets and search/filter them better there. I hope this will also avoid the problem you guys have described here.

While Kontrol is a powerful tool, especially for browsing your entire library, I have a couple of issues with it.

One, is that it is very slow and sluggish, a lot of other people think the same way too. Two the little pane you get for browsing presets is all too often very tiny.

The third is a problem inherent with the design. If I have 10 instruments in a mix that’s 10 Kontrol instances, each one saying “Kontrol” in the mixer. I can’t just look at my channel strips and tell what instrument I’ve used and where. Sure there are track labels, but there’s always those moments that in the heat of composition you end up with something like half a dozen tracks that all have no labels. What is what?!? You have to dive through each instance or go around soloing things listening etc.

I just like having that second point of reference where I can tell which instrument is which just by looking at the channel strip inserts. It’s a seemingly small thing, but it’s a relatively important element to me.

So I tend to use one instance of Kontrol as a browser, find my sounds, figure out which instrument it is and then load them up in a different instance with that dedicated instrument.

[LoveEnigma18]

^ I agree with your points here, and the last point is actually a good way to use KK software in a project, especially for the third problem that even I find annoying.

I was just trying to propose a better way for browsing (and favoriting) Massive X presets, because Massive X browser sucks and is unusable (at least for me).

I am waiting for a major update to KK software for some time now. Hopefully we will see it next year.