Loading existing project with new Massive X 1.2 update resets the patch to "init" [en-us]

Pinned Featured Answered

Comments

38 comments

  • Avatar
    Jesus Oseguera

    I just started having this issue again when opening an old project and massive x preset I created is now at init. I tried my best to recreate what I had done, and once I closed it and came back to it it still goes back to init even when saving as a new preset. I have already checked and confirmed it is massive x 1.2.1, I even reinstalled it to try for a third time and it continues to open as init. I don't want this to happen to my other files so I am currently avoiding opening them because of fear of losing everything.

    Please help. I am using the latest version of Studio one 4. This is happening on my windows 10 lap top

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Jesus, we contacted you by email regarding this, please check your inbox.

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    Has Native Instruments given up on fixing Massive X and will they issue refunds to their customers?

    0
    Comment actions Permalink
  • Avatar
    Alessandro Donin

    Same problem here. But it happens to me randomly, not every time.

    By the way, sometimes if I close the "corrupted" project, and I open it again, it works 

    And, just to know if it happens to someone too, I have sometimes the same patch problem with Battery 4 and Kontakt

    MacBook Pro (15-inch, 2019)

    Logic 10.4.8

    0
    Comment actions Permalink
  • Avatar
    Phil Greiss

    Still not fixed? it's been 5 months

    0
    Comment actions Permalink
  • Avatar
    Phil Greiss

    but reverting to 1,1 doesn't even help! sets are broken the moment you load them with 1.2.1

    what makes this a non urgent and damaging issues?

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    AAHHHH !!

    just updated Massive X to ver 1.3.0 and i can now load my old Massive X projects again and they ALL work fine again !!

    (using Maschine on macOS Catalina 10.15.5)

     

    0
    Comment actions Permalink
  • Avatar
    N/A N/A

    Glad it worked for you, Rudy.  Unfortunately, I tried to load my project on Windows 10 after your good news with v 1.3.0, and still have all patches defaulting to <none>.  I have 4 instances of Massive X loaded, and they all look exactly the same.  They play the correct sounds back, but I can not tell what those patches are.  Bout to give up on Massive X, very disappointed in the timeline to fix.  NI said they would reach out to me (on this forum) but I never did hear from therm.  

     

    1
    Comment actions Permalink

Please sign in to leave a comment.