Massive X Crashing (Scanning Saw Filter Bass . NKSF) [en-us]

Answered

Comments

4 comments

  • Avatar
    Tim Anderson

    I solved this on my own today after being frustrated with the content library (mine got corrupted where everything is showing other since I installed the update to the Soniccouture stuff and bought the bundle which included the canterbury suitcase). That is a separate thread and the fix doesn't work for me:https://support.native-instruments.com/hc/en-us/community/posts/360008401438-NKS-categories-broken-in-Komplete-Kontrol-or-Maschine?page=1#community_comment_360001168838

     

    It seems all of the patches I made 6/27 and 6/28 when Massive X first came out and started crashing are what were causing my crashes during boot. The "saw filter bass . nksf" was a present under native instruments / user content / massive x .  When I deleted it, it crashed for a different preset I had in there... i kept deleting them until 

     

    It's frustrating over 5 months of contacting support not one of them mentioned that "Maybe it is the user patches... lets delete them and see what happens". I didn't know they weren't touched when re-installing or following all the "clean all massive x off your machine" options i followed with NI support.  it makes sense that they are not deleted in the re-install, but it still should have been brought up.

    its frustrating losing 10 hours of programming sounds, but not as frustrating as losing 5 months of being able to use the plugin when i could have deleted the user presets back in june and probably been okay.

     

    what is strange is why is massive x scanning the user patches even when they are not what you are opening? that seems like something unnecessary just causing a point of failure like i've had for 5 months.

     

     

    0
    Comment actions Permalink
  • Avatar
    Tim Anderson

    Commenting again, as NI seems to be ignoring the topic... but even after wiping my user presets and it was working... today I was working on the Deru competition and had several issues:

     

     

    1. Sounds would go silent. If I reloaded the user preset, it would pop, but then work again, but different massive X instances would randomly go silent and had to have the user preset reloaded to work.

    2. After a while my software kept crashing... I tested various things and it turns out this is the same as my original issue... All the user presets seem corrupted where if they are in the folder massive X won't load.  

     

    This is very frustrating as I spent 8 hours today working on a song for the Deru competition and now lost all the presets (and ones I had been working on since November 23rd). This is the worst piece of commercial audio software I have used in 20 years from a crashing/functionality standpoint, without any help with the resolution or acknowledgement from NI.

    1
    Comment actions Permalink
  • Avatar
    Jeremy @ NI

    Hey Silent Noise Productions.

    We have contacted you by email regarding this issue. Please check your inbox. 

    0
    Comment actions Permalink
  • Avatar
    Platypus (Edited )

    Massive X is unusable here in Bandlab Cakewalk. I'm running it inside Komplete Kontrol. I have no 3rd party patches, just the NI 1.0 and 1.1 Massive X factory libs. I can't use Massive X for more than 5 minutes before either:

    A. It crashes Cakewalk

    B. Audio in Cakewalk is completely lost and cannot be restored without restarting Cakewalk.

    I'm running a Core i9-9900, 1TB SSD, 16GB RAM, Windows 10 Home.

    This is supremely frustrating. I bought the Komplete 12 upgrade to get Massive X.

    0
    Comment actions Permalink

Please sign in to leave a comment.