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

Pinned Featured Answered

Comments

38 comments

  • Avatar
    brian phillips

    Lost hundreds of hours of work, thanks NI

    4
    Comment actions Permalink
  • Avatar
    brian phillips

    Same thing happen here.

    2
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Justin, BNP, we contacted you by email regarding this issue. Please check your inboxes. 

    0
    Comment actions Permalink
  • Avatar
    Trevor Gureckis

    yeah just happened to me as well when I updated at 10am and now I'm paralyzed. can't open any sessions bc obviously Massive X instances will be initialized.... uhhhhhhhhhhhhhhh. Logic 10.4.8. UNDO.

    0
    Comment actions Permalink
  • Avatar
    Matt Ward

    Same issue, Logic Pro x 10.4.8.

    0
    Comment actions Permalink
  • Avatar
    Peter Major

    I have the same issue in Cubase 10.5 on windows 10.

    0
    Comment actions Permalink
  • Avatar
    andrew kiser

    Same here using Ableton 9.7 windows 10.

    0
    Comment actions Permalink
  • Avatar
    andrew kiser

    using Ableton 9.7 Windows 10

    I can reproduce this bug, to make it happen :    

    *first you needed to have installed the 1.2 update.

    1. open a project made with massive x 1.0 or 1.1 (not sure which was installed on some older projects i tested)

    It will recall the patches and presets normally so you would think everything going fine.

    2. Save the project and exit the DAW

    3. Reopen the project and all patches and presets have been reset to the default patch

    *notes* as of this comment a new project using massive x 1.2 that has no previous version instances of massive x in the project will recall patches and presets with normal behavior.

    so my take is projects that use massive x  versions earlier than 1.2 are no longer workable as of now. Either wait for a patch or roll back to 1.1 or 1.0 so you can open the projects you've been working on since massive x came out :( 

     

    0
    Comment actions Permalink
  • Avatar
    Peter Major

    Roll back works for now. All sounds load properly.

    Links to V 1.1 can be found in this thread:
    https://support.native-instruments.com/hc/en-us/community/posts/360008669398-Massive-X-1-2-Update-Loading-some-presets-doesn-t-work-en-us-?page=1#community_comment_360001235858 

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI (Edited )

    Dear all,

    The Massive X has identified the bug and are working on a fix.

    Projects saved with Massive X 1.1.0 without a preset name load the Init preset in 1.2.0.

    At the moment the workaround is to install the previous version, including the Factory Library. Here are the installers :

    Massive X 1.1 - Mac

    Massive X 1.1 - PC

    Massive X Factory Library 1.1

    We are sorry for any inconvenience. 

    0
    Comment actions Permalink
  • Avatar
    Troost

    I am also having this problem! 

    Please Fix Soon!

    Had an anxiety attack from this!

    0
    Comment actions Permalink
  • Avatar
    Marcel Schwarz

    Same here (Reaper 6.02) ... rollback completed but no help for at least one project which I saved with the init patch BEFORE I noticed it (before I came to the part where the sound was used). I don't see any chance to get it back now. That sucks MASSIVEly!

    0
    Comment actions Permalink
  • Avatar
    N/A N/A (Edited )

    Hey guys, yesterday I was using Massive X in a project and the preset I created for it was working fine. Today I opened Ableton, loaded the same project and I have found my Massive X preset just lets out a nasty sounding Sine wave-type sound. I've had instances in the past where this has happened and the problem has been a required update - either to Komplete Kontrol or Massive X.

    However I have noticed my preset was reset to the 'Init' preset - so I tried reloading my saved preset again and it played normally for about 5 seconds before the horrible Sine sound came back.

    Initially, I thought it was an issue with a Komplete Kontrol update because my Native Access is telling me I'm running Vers 2.2.1 but looking on the NI Website, the latest update is listed as 2.1.3. However, when ask Native Access to scan for updates, it tells me that all my software is running the latest versions...

    I'm not sure if the issue is Massive X or Komplete Kontrol. Does what I've described match the problems that you guys are having in this thread?

    Thanks :)

    P.s. The Massive X version I'm running is 1.2.0 and it's on Windows 10 64bit.

    1
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey dear user, yes indeed, that looks like this issue, please try downgrading to Massive X 1.1 and the library to 1.1 as well, you have the links in the official comment.

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

    Hey Jeremy, okay, will do. Thanks for the advice and for getting back to me :)

    0
    Comment actions Permalink
  • Avatar
    Michael Kranich

    Hey! When we will get an Update for our Massive X? 

    0
    Comment actions Permalink
  • Avatar
    Michael Kranich

    The Library Browser / Presets is/are empty. 

     

    I´ve installed the Massive X Factory Library from the Not installed tab. It doesn’t help.

     

    I downgraded to 1.1.0. First it works. After reopen the project and all patches and presets have been reset to the default patch. Then I get the error „Error Loading Press - Retrieving preset failed.“. After restart, (2nd step reinstall) and reopen Massive X the Library Browser / Presets is /are empty. 

     

    Then I followed the steps from your support:

    Move the folders to the trash:

    „~/Library/Application Support/Native Instruments/„

    „~/Library/Preferences/com.native-instruments.Massive X.plist“

     

    Restart - no presets. Ableton 10.1 crashed after closing not working Massive X. I used Mac OS 10.14

     

    I can’t continue my work and I can’t use Massive X.

     

    It is incredible and I finally expect a Massive X that works. I have seen studio equipment of several thousand euros and have never seen anything so unstable. I have no desire to take additional hours of support because nobody pays for the time. If you cannot help me because your product was not developed correctly, please refund my money.

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hello dear users,

    Massive X 1.2.1 is here and fixes this issue. Please install the latest Massive X update in Native Access. Let us know if it fixed it for you !

    0
    Comment actions Permalink
  • Avatar
    Andrew Bull

    Praying this has reset my saved sounds.....

     

    Been banging my head on PUSH over this one. My label guy is pretty shitty with the delay.

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    this has NOT fixed the problem.

    1) create a new project in Maschine with Massive X 1.2.1 presets as sounds
    2) save it
    3) quit Maschine
    4) open Maschine and load the project
    5) all Massive X presets are reset to INIT

    WHAT???

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Rudy,

    Please click on the little arrow next to the sound parameters : 

    Then click on the NI logo, can you confirm that it is version 1.2.1 ? If it is, please let us know your operating system.

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    yes, it's Massive X v1.2.1

    Maschine 2.9.2

    mac os Mojave 10.14.6

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

    Same for me.  Everything is defaulted to  Init sound, even though it is playing back properly with the sounds I originally chose. 

    I am trying to recreate the project for remixing and I have no idea what sounds I have chosen.  

    I'm on Win10 using Sonar as my DAW and installed every available update via Native Access.

     

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    yes, Massive X is broken bad...

    on Mac Mojave....

    Maschine:
    Massive X ver 1.1
        when you save a performance and open it up again, 9 out of 10 Massive X sounds only play very faintly
        or as if parts of the sound are missing. the sound names are still the same.
    Massive X ver 1.2 or 1.2.1
         the sounds are completely reset to INIT. names are still the same.


    Logic Pro X :
    Massive X ver 1.1 - works fine
    Massive X ver 1.2 or 1.2.1
    the sounds are completely reset to INIT. names are still the same.

    Ableton Live 10 :
    Massive X ver 1.1 - works fine
    Massive X ver 1.2 or 1.2.1
    the sounds are completely reset to INIT. names are still the same.

    0
    Comment actions Permalink
  • Avatar
    EvilDragon

    I wonder if it might be Mac-related, because over here in Win10, I tried MX 1.2.1 with FL20, Live 10, Maschine, Studio One 4, Reaper 6... made a project with a number of MX instances and randomly picked out patches and everything recalled perfectly fine when reopening the project...

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    Very interesting indeed.

    So i would agree that it must be Mac related.

    Just to make sure, i now also tested ver 1.2.1 on Maschine on Mac OS Catalina. Same problem as in Mojave.

    Patch names stay the same, but the sound is set ti INIT.

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Rudy, Brian, The Massive X will contact you by email shortly. Thanks for your patience !

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    Did you tell Brian about it as well? :)

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

    I'm on Windows 10 so unless someone secretly switched me to mac, I don't think that's the issue for me :)

    0
    Comment actions Permalink
  • Avatar
    Rudy Vogelsang

    so are there any Mac people still looking into this?

    0
    Comment actions Permalink

Please sign in to leave a comment.