Samples are a mixture of Spitfire, Berlin, Cine, 8dio, etcĪnyone have any idea what could be the culprit? I’m used to audio glitching sometime even on a fast system, but it seems crazy to have to restart twice ever time this happens (which is. Putting some tracks in sampler mode also seems to be helpful, but I’ve never done that in the past on far inferior systems.Ģ x 2 TB OWC Accelsior 4m2 cards for samples, with SoftRAID from OWC If you need more information about a specific part of MASSIVE, here is where you will find it. The raw tone a constantly shifting textural pad is generated by the FM Growl wavetable in Oscillator 1, and a tempo-synced. The main patch, ‘Massive X 1’, is a bright, minor-key chordal affair with a choppy, gated feel and plenty of harmonic movement. The only things that seems to have helped a bit was setting the DFD lower (which seems counterintuitive). covers all aspects of MASSIVE and provides usability hints as well as technical information. Download Nmak's patch, then enter for a chance to win Native prizes. This only temporarily relieves the issue.

You can then use the Remote Octave control to trigger them on your keyboard, meaning you get truly playable. If I try hitting the ‘!’ in Kontakt, I get a spinning beachball. Native Instruments Massive X v1.3.6 MacOSX. If I stop playback and try to play a single note on any Kontakt patch, the disk meter will flash red even though it remains at 0% usage.Īny time this happens, I am not able to restart the Mac, so have to do a hard power off, and then do a fresh restart after powering back on.

When I’m running more than say, 15 tracks at once, I’ll suddenly get a disk overload in Kontakt, and all samples from that point forward will cut off right after the initial trigger. Have been dealing with an extremely frustrating issue, and can’t seem to get to the bottom of it. I’m running Kontakt 6 in Logic Pro X on a new Mac Pro, Catalina.

Massive native instruments trigger