Massive X forgets my settings ?

Fhin
Fhin Member Posts: 2 Member
edited October 2024 in Massive X & Synths

Hey everyone,

So, I opened my session this morning to put the final touch on a song. Nightmare mode is on since all my massive X tracks are doing a "000" init type sound, and all those show blank LFOs, blank FXs, filters etc.

Everything is ok on other sessions it seems. I didn't save my presets and i'm terrified because I started from an existing preset but worked a lot on it afterwards, and I have no clue on how to get it back again. I have to finish my EP this week, I have been on this for more than a year and this happens now 😊

I am on a M1 max mac, 12.6, last version of Massive X, last version of Logic Pro, tried Rosetta and Silicon mode. Here's what it looks like.

Screenshot 2022-10-26 at 13.19.07.png

Hope you guys don't have that issue, but if you do or did, I'd be so relieved to fix it !


Thanks πŸ™πŸΌ

Tagged:

Best Answer

Answers

  • Fhin
    Fhin Member Posts: 2 Member

    I am really lucky, I found an older version of that project where my presets were intact. So, easy to solve my issue, but I can't imagine the struggle if I did not. Hope this will be fixed, I'm curious if some of you ever had this issue and how you managed to solve it. (I made a support ticket, I'll write here what they tell me about it).

  • Nico_NI
    Nico_NI Administrator Posts: 1,123 admin
    edited October 2022 Answer βœ“
    https://community.native-instruments.com/discussion/comment/37001#Comment_37001

    Glad to hear you managed to save your project, those kind of stress though 😰 Hopefully our support will be able to tell you more!

  • merges
    merges Member Posts: 6 Member

    I also experience a similar problem on a regular basis with Massive X 1.4.0 in Ableton Live 11.2.5. Duplicating tracks so that there are multiple instances of Massive X, re-ordering tracks, force-quitting, sometimes just saving and re-opening tracks, and other unknown conditions, cause the patch to change or reset. The most common issue I have is that the same patch is loaded, but the Macros change.

  • shields.up
    shields.up Member Posts: 2 Newcomer

    Same, just bought massive X and noticed it with my first project that has more than one instance. Really frustrating, it actually happens every time I close and open the plugin window even. I'm on Logic pro 10.7.8, on an M1 Max laptop.

  • Sanjyn
    Sanjyn Member Posts: 1 Newcomer

    Same here, happening everytime I close a project. I'm on FL Studio 24, Massive X up to date.

    The only work around for me is to save every instruments as user presets.

    Just annoying to reload every instrument hope they do something about it…

  • Mark Oxley
    Mark Oxley Member Posts: 376 Pro

    Same has been happening to me for quite a while. I've largely given up on massive x since bugs go ignored and updates to the plugin are non existent. I've got no time for products that aren't supported and have moved on to other synths that are regularly updated.

  • NKFortySev
    NKFortySev Member Posts: 3 Newcomer

    Has anyone found a solution for this? I’ve heard several people complaining about this with Kontakt and Massive, but no fixes. I refuse to buy another NI product until this is fixed.

  • Vilming
    Vilming Member Posts: 3 Newcomer

    Just chiming in to say I've had a similar issue for a long time - even with the latest version (1.4.4+48). I reached out to the very friendly and helpful Support, but we didn't conclude on root cause. However, I discovered that the setting of my NI Komplete Kontrol S61 mk1 may be related to this. I have a few MIDI presets created for it, using Controller Editor, to play standalone versions of Arturia synths, etc. Whenever one of these presets are loaded, the Massive X patch I use changes (often, it seems, the macro settings have changed). If instead I turn the NI S61 to its Default mode before starting my DAW (Presonus Studio One Pro 6.6.2), the Massive X patch remains unchanged. There's no difference if I use a factory patch or one I created myself. Behavior seems consistently related to the setting in my keyboard on load. Hence, my workaround is to always use the Default mode on the NI S61 before I start my DAW. Same behaviour in Cubase, but not in Pro Tools if I recall correctly. Would be great to know if posters above happen to have the same MIDI keyboard as me.

This discussion has been closed.
Back To Top

Categories