Is anyone else having constant bugs and errors from Massive X after this update? I have resorted to spam saving all my projects that include a Massive X track after every change. Automation, including the use of the animator, makes Massive X more of a Massive Liability. I have many projects with Massive X tracks prior to this update (the synth is awesome), but now I have to freeze all my channels in fear of crashes. Sometimes the freeze process itself crashes the synth. Here's a conversation I had with AI about a recent crashdump (I have many):
The crash log indicates the crash occurred at the address
0x7ffd3326d44a
within the Massive X VST3 plugin. This is a very specific address, and while it doesn't give a function name, the log states it's an
access violation (c0000005) caused by a read from a null address (0000000000000000).
Don't worry, I double checked if it hallucinated those memory addresses, and it did not. Apologies for the AI use, I was tired at the time.
What's happening here? Is this just a buggy update? I can't find any broad testimonial threads that are talking about this. Any ETA for a better quality update with some stability improvements? My workflow has gotten very hellish and god Massive X is just so damn good I don't want to learn another synth when I know this one like the back of my hand…
Extra details for my specific case: Cubase 14 Pro. Older projects with old instances of Massive X have much higher chance of chain crashing. Sometimes the plugin just won't play sound. In this case, I can get it working again by hitting the A/B switch (switching it to the same exact config as A, but for some reason, now it plays sound). You could see how this can get exhausting if a project has many such Massive X tracks. Between having to chain save, freeze everything like a madman, and A/B switching I am having nightmares of having to sit at my DAW.
Anyone else?
