Massive X 1.6.1 update (September 2025)!

[liv]

Could there be around 1 million MX owners?

[_leras]

i tired to read some of it. the entire GUI seems counterintuitive compared to other competing products (which I won't bother to name.). Synth VI's are a personal taste. With some you get along. With some you don't.

The UI takes some getting used to. Some unintuitive controls for sure. The more you use it the more familiar it comes.

It's a pretty vast synth though, a lot, almost too many options. Exploring it all is impossible.

re: wavtables, there are plenty. I honestly don't think many people import their own either. That's not this synths issue. That said, an option would be good.

[VitaminD]

Biggest issue for me is the lag. It takes a while for the interface to open, and while that's happening it freezes my DAW. Having to double click presets is a pain in the arse too. Definitely the best sounding synth I have though.

Those are my issues with it too.

It is a bit sluggish, even on my 5900x, compared to other synths. I wonder if it is Reaktor underneath and the slowness is due to the complexity of having to initialize and then load through all the underlying parameters? A C++ based product shouldn't be so slow. Modular synths aren't even that sluggish. Maybe it is just the UI engine they are using though.

I did resolve one issue I had with it, that little pin icon on the browser window will allow us to keep the browser window visible after clicking on a preset. Very handy when cycling through many sounds. A single click, like u-he Hive, would be better though over the double to select a sound.

That said, the original Massive had the same behavior of double clicking, so I assume that's why they brought over that behavior.

[_leras]

It is a shame the browser isn't a bit better, and that seems to have paused updates. A 1.5 or even 2.0 update would be very welcome.

Lots of low hanging fruit for NI when they get the time.
Browser improvements
LFO improvements
Midi control mapping (beyond the macros)
etc

At least we've got oscialltors. And they are the best.

For sure it's a great sounding synth.

[EvilDragon]

I wonder if it is Reaktor underneath and the slowness is due to the complexity of having to initialize and then load through all the underlying parameters?

No, it is not Reaktor underneath. All the DSP was prototyped in Reaktor, but it was all rewritten in C++ with AVX intrinsics to optimize CPU usage to the bone.

It's mostly about the UI framework, I think (Qt).

[killmaster]

I wonder if it is Reaktor underneath and the slowness is due to the complexity of having to initialize and then load through all the underlying parameters?

No, it is not Reaktor underneath. All the DSP was prototyped in Reaktor, but it was all rewritten in C++ with AVX intrinsics to optimize CPU usage to the bone.

It's mostly about the UI framework, I think (Qt).

Thanks, always wondered about it's UI sluggishness.

[Lbdunequest]

Biggest issue for me is the lag. It takes a while for the interface to open, and while that's happening it freezes my DAW. Having to double click presets is a pain in the arse too. Definitely the best sounding synth I have though.

Those are my issues with it too.

It is a bit sluggish, even on my 5900x, compared to other synths. I wonder if it is Reaktor underneath and the slowness is due to the complexity of having to initialize and then load through all the underlying parameters? A C++ based product shouldn't be so slow. Modular synths aren't even that sluggish. Maybe it is just the UI engine they are using though.

I did resolve one issue I had with it, that little pin icon on the browser window will allow us to keep the browser window visible after clicking on a preset. Very handy when cycling through many sounds. A single click, like u-he Hive, would be better though over the double to select a sound.

That said, the original Massive had the same behavior of double clicking, so I assume that's why they brought over that behavior.

Ita sluggish on my 7950x too. Main reason why i dont pick up this synth when doing music stuff.

[martiu]

it is a great synth but if that is optimized to the bone we have a problem

[Medenka]

It's mostly about the UI framework, I think (Qt).

Didn't know that, why are they using Quicktime?

BTW, the Browser needs works, a lot! My +1.

[Dencheg]

It's mostly about the UI framework, I think (Qt).

Didn't know that, why are they using Quicktime?

BTW, the Browser needs works, a lot! My +1.

Whatever it is, it's not really quick

[carrieres]

It's mostly about the UI framework, I think (Qt).

Didn't know that, why are they using Quicktime?

BTW, the Browser needs works, a lot! My +1.

Qt is a cross-platform application development framework for creating graphical user interfaces https://www.qt.io/
Quicktime died in 2020
https://fr.wikipedia.org/wiki/QuickTime

[EvilDragon]

it is a great synth but if that is optimized to the bone we have a problem

I said DSP optimized to the bone. If AVX instructions weren't used it would take way more CPU.

[Medenka]

Qt is a cross-platform application development framework for creating graphical user interfaces https://www.qt.io/
Quicktime died in 2020
https://fr.wikipedia.org/wiki/QuickTime

Didn't know that, thanks for the tip! Quicktime used to be abbreviated as QT for about two decades - or more, IDK exactly. And was also a video-UI framework, so there's definitely some name overlap.

Guess we'll have to keep wondering why the Massive X interface is so slow.

[digitalboytn]

it is a great synth but if that is optimized to the bone we have a problem

I think that the CPU hit is very low considering everything that is going on under the hood and the sound quality is undisputable....

Ahhh....those filters

[swilow11]

I'm surprised at how many people are mentioning the browser. It's possibly the least exciting part of any synth, for me at least. The sound quality and ease of use are just light years more important imo. Massive X sounds 10/10 phenomenal and is maybe 6/10 in terms of UX.