MASSIVE X browser is so bad the synth isn't getting used

We delete non-english content whenever we see it.
There's a German sub-forum so it seems like a pretty fitting place if you want to discuss anything in German.

 

I have created a solution for myself, which took a little time, but is good for me until NI updates it:
I put a number in front of each preset and this number corresponds to a preset pack. Better than annoying me further
Again, sorry to those I annoyed with my bad mood.

 

Duly noted, Sarge!

 

I've read in this forum, there should be Apple Silicon version of MX soon. So, maybe also other changes will come.... Maybe even the browser.

 

Yeah, "relatively soon-ish"..

 

It will be the Rosetta 2 update first since the browser one will take a bit more time.
I'm trying to find more information on the compatibility update now and I'll report back when I hear more

 

I see, so MX will work under Rosetta 2?

 

That's going to be the first compatibility update so we can get something going before finishing up the native one. It seems like the ETA should be around 3-4 weeks if there's no extra delay coming along.
We'll share updates if we hear more about the progress.

 

Just got komplete and had a look at Massive X - I honestly thought I was missing a browser button or page because not in my wildest imagination did I expect such a bad browser experience. No buying preset packs for this one - back to the U-He synths instead .

 

why is MassiveX always rescanning the user-folder when inserting "him" into a new track in Cubase? that´s weird time-stealing

 

hmm, maybe that’s the reason it takes so long to load the patches in Komplete Kontrol? I like to play some notes while I browse patches from KK/Maschine. And every time I run into a Massive X patch it plays a sine wave for a little bit before the patch actually loads. I haven’t noticed this happening with any other synth.

 

Bummer! Having the experience I have with this synth, I couldnt imagine not using it, browser or no browser. It never creates any weird sine wave for me when I run it, browse patches, etc, FYI. That may be an audio interface or other environmental issue. Serum gives me about 500% more trouble than mX, so I feel the same way you feel about mX, but about Serum, lol.

Honestly its browser is a lot like many steinberg UI interfaces. If you quit the plugin or quit cubase, then come back to that same plugin after re-running it, hitting "next" on the browser always goes back to the start of the whole patch list instead of advancing to the next one. I find that incredibly annoying, but not annoying enough to not experience these things. I come from the late 90s VST/DAW/DSP era, so you could just give me a folder of FXPs and make me manually load them, and I would still be happy. I know not everyone is as adaptable as me, though. ; )

 

Hehe, interesting. My rig feels pretty smooth with everything else (I don't use Serum though). I'll do some testing on other computers.