Massive X 1.2 Update [en-us]

Pinned Answered

Comments

12 comments

  • Avatar
    Matt Ward

    Upon project load in Logic Pro X it is not loading my preset just default sound

    5
    Comment actions Permalink
  • Avatar
    andrew kiser

    Same happened to me, opened a project I've been working on this week(first project to use the 1.2 update) in Ableton 9.7 only to find every instance of massive X reset to the default patch. I didn't save the patches as presets and Massive X is About 50% of the session,,, . It has only happened on the project made with the 1.2 version of Massive x. Opened some older projects and Massive x is able to recall patches and presets.

    3
    Comment actions Permalink
  • Avatar
    Jason Malan

    Same here, just opened a project and massive X has jumped back to the init default patch. I worked on a sound for ages, it's crucial to the song. Even earlier save versions of this project have the same problem. I closed the sessions without saving so i hope they will provide an update to fix this soon!

    0
    Comment actions Permalink
  • Avatar
    Peter Major

    This happens to me as well in Cubase 10.5 on Windows after the 1.2 update. It seems very random though. Some old projects open fine, others have all Massive X instances loading the Init patch. A project I worked on yesterday, opening and closing many times with Massive loading the proper sounds, today only opens with all Massive X instances set to the Init patch.

    We need a fix for this asap or a way to downgrade please!

    0
    Comment actions Permalink
  • Avatar
    Daniel Hatadi

    Link on how to downgrade:

    https://support.native-instruments.com/hc/en-us/community/posts/360008669398/comments/360001235858

    0
    Comment actions Permalink
  • Avatar
    Elena Kolpakova

    Well, at least I can finally record now! The issue I had with 1.1 where the sound spontaneously dies, appears to be fixed. TY NI.

    0
    Comment actions Permalink
  • Avatar
    Claude Samard-Polikar (Edited )

    Hi, since i updated to Massive X 1.2 ProTools stops launching when trying to scan the Massive X plug in. ( error 9178 ) I have to remove the plugin from my plugins folder to be able to launch PT . I tried with Ableton Live, Live can launch but when i try to open Massive X the app just logs out....do you guys hear of similar symptoms ? Thanks

     

     

    MacMini 2018 Mojave 10.14.6/ 64 GB Ram/     PT 2019.12 / Live 10 Suite

    0
    Comment actions Permalink
  • Avatar
    Michael Kranich (Edited )

    Same here.  open massive X and  its jumped back to the init default patch. also my preset bank is empty. AND YES - I've installed the Massive X Library separately with Native Access. Ican't believe you release a so buggy software. I bought it 5 months ago and have not even been able to use it properly. It's sad and unbelievable!

    I´m using Ableton 10.1. actually with the new MacBook Pro 16". Catalina 10.15.1

     
     
     
     
     
    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey all, if you have issues with presets turning to initial sound, please check this community post :

    Loading existing project with new Massive X 1.2 update resets the patch to "init" 

     

     

    1
    Comment actions Permalink
  • Avatar
    New Loops

    We desperately need a proper browser for user presets. When is this going to be released?

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

    I am running machdep.cpu.brand_string: Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz  and I was googling around found that MassiveX requires AVX.   This CPU supports both AVX and AVX2 (2017 iMac Pro)  but MassiveX won't install as it says the CPU is not AVX compatible ...but it is.

    0
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey dear user, we contacted you by email regarding this issue. Please check your inbox. 

    0
    Comment actions Permalink

Please sign in to leave a comment.