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 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 VST/AU/AAX formats, and from the MPH you can load third party plugins. You can also use it with your DAW’s native plugins but, more on that later.
MPH allows you to load only one third party plugin at a time 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 for Mac and PC.
The Mac plugin allows hosting of VST3 and AU plugins regardless of DAW. For example, If you have loaded MPH in Logic Pro, you can host AU or VST3. If you have loaded MPH in Cubase on a Mac, you can host VST3 or AU.
The PC plugin allow hosting of VST3 plugins only. So in Pro tools for example, you can host VST3.
AAX hosting is not possible as the AAX framework is not open to hosting. AAX hosting is only possible by Pro Tools.
MP MIDI will be available only via pre-orders and if you would like to find out more please contact us via our website form.
The complete state of your hosted 3rd party plugin. This mean total recall guarrantied. The MPH, much like any DAW, passes the memory block to the plugin that is being hosted so that the plugin saves the data into the memory block, Then the MPH uses a 64bit encoding system to convert the memory block data into a string of ASCII characters and then it stores it into the xml file. So, presets are portable (they work) from one DAW to another.
The only plugins that can be hosted are 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.
Approximately, the finished unit will be 50cm x 30cm and the height in the front will be 5cm and at the back 9cm.
Yes, you can use the MP MIDI like a regular MIDI controller and you can have the DAW mixer in the controller's screen.
The MPH scans all your existing plugin’s folders and lists them so that you can recall them when you open the MPH. 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.
You don't need to load the default MPH plugin every time, as you can save plugin file presets.
What this means is that you can generate plugin files, so that you can load them up in your DAW.
The reason this was done, is so that you can load up straight from the DAW different MPH plugins.
Each plugin generated by the MPH has a M- in front of it as you can see from my Mixer in Logic here. This is done so when you generate new plugins, you don’t overwrite your existing plugin files.
The MPH has been tested with hundreds of plugins and works well regardless of the loaded plugin. It has also been designed to be crash-proof. The code does not allow any memory leaks and it is super stable. MPH was tested in Cubase, Protools, Logic and Ableton on Mac and PC. It should work on any other DAW that supports plugins.
MPH offers of course 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.
The third party plugins are automatically positioned in the center of the MPH and cannot be moved.
Your DAW opens the MPH plugin at the exact same position on screen it was opened last time, perfectly placed under the encoders of the MP midi controller transparent overlay. So, if i open my DAW project, the last plugin i was working, when i saved the project, is positioned on the MP midi controller’s display.
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. The preset files can be used in other DAWs on Mac and PC, it doesn’t matter, because the MPH operates completely independent in regards to Midi mappings. So, 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, as you can see here. 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, all that is left is to map the software parameters of the loaded plugin.
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.
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.
MPH allows you to create and 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.
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 (Intel/AMD). The plugins continue to be processed by your computer.
We have tested the MP MIDI controller with hundreds of plugins from different vendors. We did not find any compatibility issues. 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. If your DAW is can host only 64 bit plugins, then the VST3 and AU plugins that can be hosted by MP MIDI will be 64 bit only.
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.