I load a preset and change it. Everything's fine. If I reload the saved project or the saved preset, the sound no longer sounds as expected. Does anyone have a similar problem? I use Massive X under KOMPLETE KONTROL (latest Version).
How do you save the preset exactly and how do you recall it? From your user library?
You mentioend saved project, what DAW are you using?
Do Komplete Kontrol and your DAW have full disk access? How to Enable Full Disk Access on macOS
Can you provide screenshots, or even better a small video showcasing the issue so we can see what could be wrong?
Me too man, it's makes me crazy, how can we contact the developers
Hello Jeremy, I hadn’t seen your reply. As for me, the bug happens randomly. I’m using Ableton, and I’ve reset my entire Mac M2 to factory settings and reinstalled everything, but the bug is still happening, so the issue is with the plugin. My problem is major because, in addition to the presets with values that change when I reopen my project, I also have another bug where, as soon as I try to remove the Massive plugin, the project crashes. This only happens after several hours on a project and in a completely random manner.
I managed to locate one of the current bugs in Massive. Aside from the fact that some presets do not recall all values properly every time a project is reopened, there’s another bug that occurs when I deactivate the plugin, save the project, reopen it, and then delete the track — the project crashes. Once the project is saved with a deactivated Massive, it’s no longer possible to delete tracks where Massive is involved. It’s hard to explain, but this is what’s happening.
@Hakkah Are you able to reproduce the issue in a project, zip it here and upload it? Maybe a video showcasing the issue would also help. this way we can try and reproduce the issue on our end, show it to devs, etc…
Alright, I think I’ve found the source of the problem. It seems that Massive starts bugging as soon as you create your own “user” presets. I deleted my user preset folder and the bug stopped. It’s really annoying.
I don’t think you can reproduce this bug by opening a file I’ve prepared, since the bug seems to come from reading my folders related to Massive.
What I don’t understand is why you don’t have this bug, while I’ve rebooted my Mac three times since and the bug keeps coming back every time. It really feels like the issue is with the plugin’s coding itself.
Finally the bugs didn't come to this
