The MP Host (MPH) is a VST3/AU/AAX plugin itself and it can load up third party VST3/AU plugins. MPH allows to load only one third-party plugin at a time and there are two versions of MPH, Audio Effects and Instruments.
Its virtual encoders (32 per page, 4 pages, total 128 virtual encoders) can be mapped to parameters on third-party plugins and on midi controllers.
Audio passes through the MPH unchanged, the MPH does not process any audio and there is zero latency to the audio signal. The MPH is a virtual midi controller within the DAW, acting as an intermediary between the DAW and the hardware MP controller. Midi played notes and DAW tempo are passed to the third party plugin loaded in MPH. If the loaded plugin is introducing latency then MPH passes this latency to the DAW.
The MPH scans all your existing plugins and lists them so that you can recall them when you open the host. If you don't want to scan your plugins, you can just drag and drop a plugin file (.component, .vst3 etc) onto the MPH and it will add it to the list.
MPH can save presets that can be recalled at any time.
MPH has been tested with hundreds of plugins. If a plugin can be controlled via standard MIDI then it works with MP MIDI. It has also been designed to be crash-proof. The code does not allow any memory leaks and it is super stable.
Pickup Control where you left it when working/switching between multiple plugins, just like a hardware unit.
Upon opening up an instance of the MPH plugin in the DAW, immediately transmits the current instance’s parameter values to the MP controller (or any midi controller).
For example, you are working on MPH - Synth ABC and you close this window to open window MPH - Compressor DEF. Upon opening from the DAW, the loaded MPH - Compressor DEF plugin, MPH sends automatically all the CC values to the hardware, so when you reach for any knob, it is exactly at the position you see on the MPH screen. Just like a hardware unit.
Each DAW has implemented controller mapping in a different way. MPH mappings have nothing to do with the DAW mappings and are completely independent. All mappings are done internally and can be saved as xml presets within the MPH or presets of your DAW.
The hardware encoders are mapped on the MPH virtual encoders and the virtual encoders are mapped onto the 3rd party plugin’s parameters. All three are interlinked and moving either, will move the other two.
Mapped encoders change values as you scroll through loaded VST/AU plugin presets
Going through the presets of your loaded third party plugin, changes the values on the mapped virtual encoders and the hardware controller so all three, the loaded plugin, the virtual encoders and the hardware encoders are all in sync, all the time.
For example, you have loaded Sylenth1 in MPH, going through Sylenth1’s presets immediately reflect on the virtual and hardware encoders.
Automatic Remote Control On/Off
Control only what you see.
The MPH stops responding to incoming midi controller messages when its window is closed or not selected (option). This means that MPH accepts input from the hardware only if the MPH window is open or selected, if this option is enabled.
Opening another MPH instance, the control is transferred to that instance. So, in essence you are controlling what you see, just like a hardware unit. There is of course, a button to override this, so you can have control input on/off manually.
Oversample/Upsample your plugins, eliminate aliasing
The sample rate of your project can affect the processing of sound in the DAW (in the box). In the cases of virtual instruments, amp simulators or even when pushing the volume hard on plugins, the effect can be quite noticable.
The problem is called 'fold-over distortion' or 'aliasing' and this is because a digital system (ie a DAW) can only produce audio that is half the sampling rate of the project running. This is known as the Nyquist limit. So when a plugin generates harmonic content above the Nyquist limit this is reflected back in the audio spectrum creating ugly, unwanted sound material.
Some plugins have oversampling options. Many plugins though don't have this oversampling option and this is why we included this feature in the MPH so that you can upsample plugins up to 8x. Oversampling is a process that can induce latensy in the signal path, and we account for that by passing the latensy to the DAW.
With MP MIDI you can set the working mode of each encoder. Absolute mode uses standard 128 steps. With absolute mode you can use the Magnitude setting to increase resolution or scale up the turning effect. Relative mode allows setting a custom resolution of each encoder from 1 to 999.
This is a scaling factor for each encoder, ranging from 0.01 to 50. So your incoming CC can be scaled accordingly.
For inverting the incoming midi CC message. Moving the hardware controller clockwise, moves the virtual encoders anticlockwise.
Set the minimum and maximum range, from 0 to 127, you want the Virtual Encoders to respond.
Set the same CC number to multiple virtual encoders and create macros. Combine this feature with M-P-R and you can create complex macros. Opening up the cutoff filter of a synth while lowering its master volume, at a smaller rate using the Magnitude.
MPH allows you to load background images, so that they look like a part of the loaded third party plugin.
With a custom background image, you can “group” the virtual encoders, so that they match the layout of the actual third party plugin.
Each, can be assigned to the hardware midi controller encoders and to a parameter on the loaded third party plugin. More often, loaded plugins, like a Software Synth, carry more than 32 parameters. So, we created 4 pages, each can be customized to your liking, mapping values as you like. Each page can have a different page background, so that the page can be recognized at the first look. Switching page on the Software, automatically changes on the MPH Midi Controller.
You can create presets, that will load up your favorite plugin fully recalled from the last Save, the mappings/assignments you made and the page backgrounds you used.
You can save presets from your DAW, as channel strip presets and would still recall everything.
MPH presets though, are completely portable from and to any DAW.
MPH will allow you to save a preset as a plugin file in a category (ie by instrument, or manufacturer, or by type of audio effect, or any name that you want).
In addition, for AUs, you can export the MPH and the loaded third party plugin combined as a .component plugin file, so that you can load it directly in your DAW, as a plugin, rather than opening up the MPH and then recalling the preset.
Creating templates for any plugin is easy. Loading the default MPH preset, has all the encoders mapped to the controller. The only thing left is to map the parameters of the third party plugin you would like to control. Also, you can create a cool background image 1920 x 1060 px, and just drag and drop on the plugin.
We also create templates and presets for popular plugins, so you can download these from our website.
Send us a list of your 20 most favorite plugins, we create templates based on popularity.
You can create combinations of mappings as you like.
For example, you can have the Cutoff Filter and Resonance of a synth mapped on every page. You can create combinations of parameter sections on each page as you see fit.