Mux modular

Is not from an identified developer", click Open Anyway.3. Rescan MUX Modular VST from your DAW. You will get this message: "MacOS cannot verify the developer of MUX Modular. Are you sure you want to open it? By opening this app, you will be overriding system security which can expose your computer and personal information to malware that may harm your Mac or compromise your privacy".4. Click Open.Inserting Your MUX Modular Plug-In User KeyWhen purchasing a MUX Modular Plug-In User Key, you instantly get an Initial User Key that you can use immediately. Note however that this Initial User Key is only valid for a limited time.Soon after your purchase, and certainly before the Initial User Key becomes invalid, you'll also receive your Personal User Key via email.Make sure you also enter your Personal User Key as that's the permanent one.A MUX Modular Plug-In User Key is a multi-line text which looks like this:========================================================================[[MuTools User Key - Keep Private - Keep Intact][Public Data][Product=MUX Modular 8 Plug-In][User=Anna Peeters][Email=AnnaPeeters84@yahoo.com][Digital Data][D1=jtCMlKQdRiHPg4bHnfUqzEbWc+9oo9E7z4bFXJTotvTD4G5KfrIv9rwyjY0w1pN4][D2=J5EUrTQURXg898O9mI1TCHKk2AjtKn1CfEUcXLkBtB4QIXTU7oGJtAJiJAqUOw56][D3=hqpQtclLGWvmMN8aUmHzmg+URo5Om9gBnLftRG6Q5x3JmyLGxDwqhqkcw3CVxd4d][D4=OL3MfQ-LAvS3VNy5ijpOcDJQaekC4EDzt7+2hxNmGqfEFk2GYGmG4rzjO6IWBsye]]========================================================================Open the MUX Modular editor, click the main options menu at the top-right and choose "Insert User Key".Copy your complete user key (best including the dashed lines) to the clipboard and paste it into the dialog window. Then click OK (or press return/enter).Now close all host DAW projects and reopen the one you need. That should be sufficient for your user key to take effect. If that doesn't work (ie. MUX still in demo mode) then restart your host DAW.Updating an existing MUX Modular Plug-In installationFollow these steps:Download the new MUX Modular Plug-In zip package and unzip it to a new folder.Goto your previous MUX Modular Plug-In installation folder and copy the User sub-folder to the clipboard.Goto the new MUX Modular Plug-In installation folder and delete the User sub-folder.Then paste the User sub-folder from the clipboard into the new MUX Modular Plug-In installation folder.Finally replace the previous MUX Modular Plug-In installation folder by the new MUX Plug-In installation folder.This way, the new installation will use all your previous user settings and files.Removing Your MUX Modular Plug-In User KeyOpen the MUX Modular editor, click the main options menu and choose "Insert User Key".Just click OK while the License Key field stays empty. You'll get the question "Are you sure to remove your user key?". Click "Yes".Simply delete the MUX Modular Plug-In folder. MUX Modular Plug-In does not put any data outside that folder.

Note Filter module before the Note To Modulation Converter.Where the audio comes into MUX Modular.By adding audio input modules, this MUX also gets more audio input jacks!The "Project Audio Input" is specific for the project modular area.Where the audio goes out MUX Modular.By adding audio output modules, this MUX also gets more audio output jacks!The "Project Audio Output" is specific for the project modular area.The "PolySynth Audio Output" is specific for the PolySynth.Where the events comes into MUX Modular.By adding event input modules, this MUX also gets more event input jacks!Note that MUX Modular needs at least 1 event input jack in order to receive parameter automation events.The "Project Event Input" is specific for the project modular area.The "PolySynth Event Input" is specific for the PolySynth.Where the events go out MUX Modular.By adding event output modules, this MUX also gets more event output jacks!The "Project Event Output" is specific for the project modular area.Where the modulation comes into MUX Modular.By adding modulation input modules, this MUX also gets more modulation input jacks!Tip: You can use a modulation input in the PolySynth to input a global LFO modulation signal which will be applied to all voices at the same time!The "Project Modulation Input" is specific for the project modular area.The "PolySynth Modulation Input" is specific for the PolySynth.Where the modulation go out MUX Modular.By adding modulation output modules, this MUX also gets more modulation output jacks!The "Project Modulation Output" is specific for the project modular area.The composer is described in detail

Important note:The below installation info only applies to the MUX Modular Plug-In version.In MuLab, MUX Modular is completely integrated.See this doc pageMUX Modular Plug-In System RequirementsVST 2 compatible host application.Windows Vista and up.MacOS 10.9 up to MacOS 10.14.x.Download the MUX Modular Plug-In zip package and unzip it to a new folder.Then move the resulting folder into your preferred VST plug-ins folder.MUX Modular Plug-In comes as a self-containing folder. It does not install anything on your system outside this folder. You can move the MUX Modular Plug-In folder after you have installed it. You can even put it on a USB stick and carry your MUX Plug-In with you.Of course it also depends on the host application if that is also that flexible.WindowsOn Windows 7/8, it may be better not to install the MUX Modular folder under the 'Program Files' folder, but rather in a non UAC protected folder like C:/VstPlugins/MuTools/MUX.This is to avoid access problems caused by Windows' UAC mechanism.The reason for this is that MUX Modular stores your user settings in a couple of files in MUX/User/Settings. The good thing about that is that your MUX Modular installation is easily movable, and can be put on your USB stick for example. Another advantage is that you can have multiple independent MUX Modular installations on the same system, for example different versions of MUX.Therefore it's best that the user settings are store inside the MUX Modular folder and thus this folder must be writable.MacOSTheoretically you can put the MUX Modular Plug-In folder anywhere you want as long as it's on a writable location.Practically the standard location is System Disk/Library/Audio/Plug-Ins/VSTMacOS Sierra and up:Due to some new security "feature" in MacOS Sierra called 'GateKeeper Path Randomization' it may be that on plugin in MUX Modular it alerts "Can't find app sub-folder" or "Folder is not writable".This is because MacOS Sierra and up heavily distrusts 3rd party apps and MacOS Sierra puts all extracted files from a downloaded zip package into quarantine by default.Nothing wrong with MacOS trying to be secure but at least it should give the user an easy way to bypass it when the user wants so but MacOS doesn't do that.To solve this MuTools has made a little tool called "Quarantine Remover" to remove that default Apple quarantine.The Quarantine Remover is included in the downloaded zip package.How to use it:Launch Quarantine Remover, eventually via right-click -> OpenDrag-drop the MUX .vst files onto the green window area, each file separately.From now on, MUX Modular Plug-in can be used normally.Catalina:MUX Modular Plug-in is not yet directly compatible with MacOS Catalina.However there is a way to bypass the restrictions Apple dictates to its users:1. Rescan MUX Modular VST in your DAW. This will force MacOS to give you this fail message: "... cannot be opened because the developer cannot be verified. MacOS cannot verify that this app is free from malware".2. Go to System Preferences -> Security & Privacy -> General tab, the last line with "was blocked from use because it