The controller consists of hardware and software. Both hardware and software work together, with the software hosted within your DAW as a plugin, to create a unique workflow.

The MP MIDI controller consists of an 1920 x 1080 IPS Touchscreen display, the enclosure, the controller board and the 32 endless rotary encoders.

The software, MP Host or MPH in short, is a plugin itself that can host other plugins. So, it is a plugin that you can load up in your DAW just like any other plugin, on mac and pc in VST3/AU/AAX formats, and from the MPH you can load third party plugins (VST2/VST3/AU). 
MPH multiplugin host allows you to load and host multiple third party plugins on every loaded MP Host plugin in the DAW and there are two versions of MPH, Audio Effects and Instruments.
Its virtual encoders can be mapped to parameters on third party plugins and on the hardware midi controller. 

Audio passes through the MPH unchanged, the MPH does not process any audio and there is zero latency to the audio signal.
You can think of it as a virtual midi controller within the DAW, acting as an intermediary between the DAW and the MP midi controller hardware.
Played notes and tempo are passed from the DAW to the third party plugin loaded in MPH.
*In the case you choose to oversample, then audio will be oversampled by the MPH.

The third party plugin’s parameters, the virtual encoders of the MPH and the endless encoders of the midi controller are linked and always in sync.
Meaning that moving either one, moves the other two. They become entangled.

So if you move one parameter of the 3rd party plugin with the mouse, it moves the virtual and hardware encoders of the MP Midi Controller. If you move the virtual encoder, it moves the other two and so on. 

The MPH stops responding to incoming midi controller messages when its window is closed. This means that MPH accepts input from the hardware only if the MPH plugin window is open.
Open another MPH plugin instance and the control is transferred to that instance.
So in essence, you are controlling only what you see, just like a hardware unit. This controller was made to allow you to control software just like hardware.

There is of course, a way to override this, so you can turn on/off manually the remote control by the hardware. If you want to have two or more windows of the MPH open, you just check the remote control checkbox.

The MPH plugin exists in the form of VST3, AU and AAX (all 64 bit) for Mac and PC. 
The Mac plugin allows hosting of VST2/VST3 and AU plugins regardless of DAW. For example, If you have loaded MPH in Logic Pro, you can host VST2/VST3/AU. If you have loaded MPH in Cubase on a Mac, you can host VST2/VST3/AU. In Pro Tools on the Mac you can host VST2/VST3/AU.
The PC plugin allow hosting of VST2/VST3 plugins only. So in Pro tools,Cubase, Ableton on Windows, for example, you can host VST2/VST3.
AAX hosting is not possible as the AAX framework is not open to hosting. AAX hosting is only possible by Pro Tools.
The MPH is allows hosting multiple plugins per instance. You can switch between the hosted third party plugins within the MPH. You can also bypass them and save presets for each multihost instance (mxml) and save individual MPH single presets (xml).

The complete state of your hosted 3rd party plugin can be saved as MPH presets. This means total recall is guarrantied along with existing mappings you made and background images. Presets are portable (they work) from one DAW to another.

The only plugins that can be hosted are VST2/VST3 and AU. Native DAW plugins (ie Logic's plugins or Ableton's native) cannot be hosted as they are proprietary plugins and designed to be hosted only in their DAW.

Width: 403mm
Length:255mm
Back height: 102mm
Front height: 35mm

Yes, you can use the MP MIDI like a regular MIDI controller, without the MP Hosting plugin and you can have the DAW mixer in the controller's screen. However, if you have it the MP Controller enabled in the DAW and you load the MP Host plugin on the Mac it will respond to both, the DAW and MP Host at the same time, which is something you may not want. In Windows, it the MP Host will not respond to the controller because Windows lock the midi devices to be used only by one program at a time.

The MPH scans all your existing plugin’s folders and lists them so that you can recall them when you open the MPH. 

The MPH has been tested with hundreds of plugins and works well regardless of the loaded plugin. MPH was tested in Cubase, Protools, Logic, FL Studio, Studio One, Reaper and Ableton on Mac and PC. It should work on any other DAW that supports plugins. If a plugin has parameters that can be automated, then the MP Controller can control them.

MPH offers total recall so that you can 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 midi controller so it becomes fully synced with what you see. 

You can record automation of each of the encoders in the DAW, like with any other plugin. Nothing strange there, it behaves like any third party plugin in regards to automation. In the Single and Multiplugin versions you can record up to 128 parameters of Automation.

Both, single and multi host plugins work on the new Apple Silicon computers under Rosetta. The DAW must be run in Rosetta mode and the host plugin will be able to host any third party plugins. Running under Rosetta has no significant impact on the host plugin’s performance.

You can Map and assign everything within MP Midi, without depending on your DAW mappings.
Each DAW has implemented controller mappings in a different way. MPH mappings have nothing to do with the DAW. All mappings are done internally and can be saved as xml presets within the MPH and mxml multihost presets (when hosting multiple plugins in a single instance of the MPH). The preset files can be used in other DAWs.
You can think of it as a cross over platform for midi mappings.
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. The MPH recognizes each subfolder created in the MPH folder as a category. 

No. There is an initial template that is pre mapped on all the hardware encoders. So you only need to map software parameters on the encoders you want and save the preset.
We have created presets for many plugins and will be creating more down the line, so that you don’t have to map anything. 
The empty template is already mapped on the MP controller's hardware encoders, all that is left is to map the software parameters of the loaded plugin. To map/link a software encoder with a plugin parameter you touch/click on the LINK ENCODER button and click/touch on the software encoder and then plugin parameter you want to link. 

With the MP midi controller you can control up to 128 parameters of the loaded plugin. This is possible through pages. Each page allows you to map a unique set of 32 mappings on the 32 virtual encoders. You can map the same parameter on more than one page. So, if i map the Cutoff filter and Resonance on page 1, i can map it again, on the same or different hardware encoder on page 2,3 and 4. And moving between pages, every parameter, encoder and knob are always in sync.
The same applies for the multihost plugin, that is 128 parameters in total can be automated regardless of how many plugins are hosted at the time.

In all Mac OS systems the touchscreen works as a single touch device.

In Mac OSX Catalina 10.15.4, Apple replaced the way hardware interacts with the OS. It introduced the new Driverkit and replaced the traditional Kexts with Dexts.
We provide a solution that works equally well for those looking to update to Catalina and future Mac OS versions and want to continue using the touchscreen functionality.

We collaborated with Touch-base, the creator of Universal Pointer Device Driver or UPDD where they created a custom Mac OS driver for the touchscreen of the controller. The driver additionally brings multi touch functionality and gestures in Mac OS and some applications however in our host plugin it still works via single touch. The driver is licensed per computer and offered at a heavily discounted price from its retailed price, but not free, as Touch-base issues a license per machine and provides support for 4 years in case Apple makes changes again in the OS that could affect the touchscreen functionality.
You can get the Mac OS driver from here and you can also download a demo to try it prior to purchasing. 

With MPH you can create assignment macros.
Click on the M-P-R checkbox it displays the following parameters:
M - for Magnitude
This is a scaling factor for each encoder, ranging from 0.01 to 50. So your incoming CC can be scaled accordingly.

P - for Polarity
For inverting the incoming midi CC message. Moving the hardware controller clockwise, moves the virtual encoders anticlockwise.

R - for Range
Set the minimum and maximum range, from 0 to 127, you want the Virtual Encoders to respond to hardware incoming messages.

CC - Control Change Number
Set the same CC number to multiple virtual encoders and create macros. Combine this feature with M-P-R and you can create very complex macros. 

The MP MIDI controller is just a controller in the sense that it does off load your plugin's CPU needs. The MP MIDI controller does not have a PC CPU. The plugins continue to be processed by your computer. 
The MP Host plugin adds almost zero load to your CPU as it does nothing but host the third party plugin the same way your DAW does.

We have tested the MP MIDI controller with hundreds of plugins from different vendors. VST3 and AU plugins are developed based on standards defined by these formats. If the developer has kept these standards, we expect that the plugin should work without MP MIDI without any problems. MPH is a 64 bit only plugin and can host only 64 bit plugins.

Yes, the mapped parameter name (ie CutOff) of the 3rd party plugin is passed to the MPH encoder automatically. Double clicking in the textbox you can rename the parameter.

Yes, the hosted plugins in MP sync with the tempo of the DAW.

No, the MP plugin does not introduce any latency. If you use the oversampling option, it introduces some latency which is compensated by the DAW.

Yes, it does and passes it to the so the DAW so that your project continues to be latency compensated.