Native Instruments – Massive X 1.2.1 rev2 – NO INSTALL, SymLink Installer (VSTi) [WiN x64]

By | April 9, 2020

 

Year / Release Date : 01.2020
Version : 1.2.1 rev2
Developer : Native Instruments
Developer’s site : native-instruments
Format : VSTi
Bit : 64bit
Tabletka : cured | VR
System Requirements : Windows 7, 8, 10 (64-bit, latest Service Pack)
Intel Core i5 or equivalent CPU, 4 GB RAM (6 GB recommended)
Please note: MASSIVE X requires an AVX-compatible CPU to run.
MASSIVE X does not currently run in standalone mode.


Description : New generation flagship synthesizer
– Flawless sound and total sound freedom for advanced sound design
– Create with a new level of dynamic, kinetic sound, with truly flexible routing and extensive modulation
– Created on the basis of the MASSIVE synthesizer for the new decade and intended for development
REALIZATION OF LEGENDS – Rethinking, remounting and reincarnation – MASSIVE X is the successor to the cult synthesizer, which helped to generate entire genres. Get everything you need to create any sound you can imagine. Quickly create complex routes to bring your ideas to life – no matter how far they can go – and move further than you thought with expressive game modulation. Think, make and determine how the future will sound.
Oscillators – At the heart of MASSIVE X you will find a completely new section of oscillators that can generate more variations than entire synthesizers, right from scratch. Choose from more than 170 wave tables and 10 different reading modes – from the aggressive Gorilla family to the mode of bending wave tables, Hardsync, Formant and many others – each with its own unique submodes and additional controls. Install two phase modulation generators to add extra movement to the main oscillators.
ROUTING – Connect any output to any input and see what happens. The intuitive routing setup allows you to essentially reprogram parts of MASSIVE X, which means that you can bypass, recall, and route the audio in any way you like. It is also possible to direct modulators as sound sources to drive elements such as a comb filter.
MODULE – Draw precise modulation schemes in the Performer section and assign them to parameters for complex, evolving patches or for controlled changes to your sound. Then you can use the Remote Octave control to launch them on the keyboard, which means that you get really playable modulation and a huge expressive variety in one patch.

 

Installation :

1. Run .exe or extract its contents by the 7-Zip archiver to any drive for permanent storage (not deep by nesting folders, briefly by name);
2. Save operating time (presets, etc.) Uninstall (or delete if there is no uninstaller) previous versions.
3. Check the absence of folders in the places of creating symlinks. Delete the folders remaining after uninstalling (IF THE FOLDERS ARE LEAVED, SIMPLINKS WILL NOT BE CREATED);
4. Launch SymLink Installer.cmd . If you need to register with keygen, patch, etc. (everything you need will be in the REG folder);
5. run DAW by setting the scan path C: Program Files VstPlugins, scan for new plugins.


For the programs and plugins to work correctly, the following must be installed in the system:
Microsoft Visual C ++ 2005-2008-2010-2012-2013-2019 Redistributable Package x86 & x64


Special thanks to users of PossibleWorlds and katromkatrom


What is a symlink?

A symlink (symbolic link) is a special type of link to a folder or file that is accepted by programs that read them as a regular folder or file, although the real data source may be on a different drive.


ATTENTION! Removing a symlink does not delete the folder that this symlink refers to.
ATTENTION! Removing something when entering the symlink folder leads to a real deletion of the deleted one.
ATTENTION! The RMDIR command does not delete the contents of a folder if it is not empty.

Is it possible to bypass SymLink Installer without .CMD files?

Yes. SymLink Installer CMD files are optional, you can simply copy files according to the folder names inside the distribution and also pay attention to the presence or absence of * .reg registry files, keygen … etc. inside the package.

Leave a Reply