4. The MP Host Plugins

The MP Host plugins are the plugins that host third party plugins and connect directly with the MP Controller hardware.

1. Instrument and Audio FX MP Host plugins

The MP Controller hardware communicates directly with the MP Host plugin, not with the DAW.

That is why it is important to disable the MIDI IN/OUT for C1-xMP1 in your DAW. C1-xMP1 is the MP Controller’s MIDI hardware.

There are 2 versions of the single MPH plugin and 2 versions of the multi host plugin. Instrument and Audio Effect. 

The MPH single and multi host plugin can host the following plugin formats

On Windows: VST2 and VST3. On Mac: AU, VST2, VST3.

The MPH single and Multi host exists in the following formats:

On Windows: VST3 and AAX. On Mac: AU, VST3 and AAX.

Windows: The installer automatically copies the plugins to their folders, respectively

VST3: C:\Program Files\Common Files\VST3

AAX: C:\Program Files\Common Files\Avid\Audio\Plug-Ins

For Windows, it is a good practice to install the C++ Redistributables from Microsoft before installing, from here.

MP Host Audio Effect and Instrument locations on the Mac

On the Mac the installer automatically copies AU, VST3 and AAX plugins to their folders, respectively.

AU (.component files): /Library/Audio/Plug-Ins/Components/

VST3: /Library/Audio/Plug-Ins/VST3/

AAX: /Library/Application Support/Avid/Audio/Plug-Ins

There are 2 Library folders on the MAC OS one is under 
/Library and the other ~/Library which means under your user account. 
You need to visit the ~/Library/Application Support/MP/Host

MP Host receives and sends the following from the DAW

Audio FX version: 

  1. Receives audio and passes the audio to the hosted plugin in MPH. In turn, it outputs audio to the DAW. 

  2. If the hosted third party plugin introduces latency, the MPH passes this latency to the DAW, allowing your DAW to compensate for the latency introduced by the MPH plugin.

  3. DAW tempo is received from any MPH instance, so in the case you are hosting a plugin that needs the tempo information from the DAW, like a tempo delay plugin, it will receive it from the DAW.

  4. Receives automation from the DAW and passes it to the MPH’s 128 encoders. More on automation below.

Instrument version:

  1. Receives midi notes (played from a midi controller or recorded) from the DAW.

  2. If the hosted third party plugin introduces latency, the MPH passes this latency to the DAW, allowing your DAW to compensate for the latency introduced by the MPH plugin.

  3. DAW tempo and passes it to the hosted instrument.

  4. Receives automation from the DAW and passes it to the MPH’s encoders.

  5. Outputs audio generated by the hosted plugin to the DAW

Plugins that can be controlled with the MP Controller

You can control all VST2/VST3/AU plugins’ parameters that can be automated by the DAW. 

If a plugin has parameters but these cannot be automated by the DAW, then these parameters cannot be controlled by MP Host and controller. 

The MP Controller is not using CCs to control parameters, it uses the same method that the DAW uses to automate/control parameters. This is called the automation method.

After version v1.5-89f683b--H2021-09-23--B2021-09-24, the MP Host can also transmit CC messages to the hosted plugin.

The CC method is one way, only for sending CC to the plugin. The method of using automatable parameters allows complete bidirectional control and it is recommended. This is the method used when you link a parameter to an encoder.

Incompatible Plugin Type Warning

While trying to load up a plugin, if you get a pop up warning message that says that the plugin you are trying to load is not compatible, this is because you are trying to load an instrument plugin in an audio effect MP Host or the opposite. You can only load plugins effects in the MP Audio effect host plugin and only instruments in the MP Instrument host plugin.

image.png

Set a title to the pages

To set a title to the pages you need to right click in the lower area of the page button


Opening and closing the MP Host plugin - Single and Multi Host

With MPH, you can control what you see on the controller’s screen. When you press the Control and Display button of an MPH (the Controller icon), the control is transferred to that selected MPH instance. The controller icon gets a yellow highlight and it means this is an MPH instance that interacts with the controller. When you click on another MPH instance, the button gets a yellow highlight  and the controller is now interacting with that selected MPH instance. 

When you close the MPH plugin small window, the MPH stops receiving any communication with the controller.


When you open a DAW project, the first time you open the MP Host plugin the small window will open and there will not be anything display on the controller's display until you click on the controller icon.

This is only necessary the first time after opening a DAW project. The rest of the times when you open the MP Host plugin from the DAW it will automatically open the window on the controller and highlight the icon or the multihost slot that was selected last.

 

Note that the MP Host does not interact with track selection of the DAW so it will not open a plugin when a track is selected.

If the DAW opens plugins upon selecting a track, (not just hiding and unhide them like Ableton does) then the MP Host will also open and it will display the hosted plugin.


2. DAW MIDI Settings

IMPORTANT: Go in your DAW settings and remove the MP Midi controller C1-xMP1 (midi hardware) from being used. If you don’t do this step, the controller will not be able to communicate with the MPH plugin. This applies to Mac and Windows DAWs. 

Here is how to disable C1-xMP1 in some popular DAWs: 


There are a few options on how to work around this, you may choose either: 

  1. Connect the c1-xMP1 USB cable after Pro Tools has started and before loading an MPH plugin instance. This will prevent Pro Tools from locking the c1-xMP1.

  2. Disable the c1-xMP1 in your Windows Device Manager and enable it after Pro Tools has started.

  3. Use a USB hub with a USB power on/off switch. There are few with switches per USB port. Turn On the controller after Pro Tools has started.

  4. Use this utility/script to start Pro Tools as administrator. This script will disable the controller, start Pro Tools and enable the controller again. There is a readme.txt in the zip file, please read it first. Download


3. MP Host properties and config files

The MPH stores its configuration, preset files and preset background image files in the MP Host folder.

Windows: C:\Users\USER\AppData\Roaming\MP\Host

(Type %appdata% in the explorer's address bar and press enter, then navigate to folder MP)

Mac: /Users/USER/Library/Application Support/MP/Host

or ~/Library/Application Support/MP/Host

There are 2 Library folders on the MAC OS one is under /Library and the other ~/Library which means under your user account. You need to visit the ~/Library/Application Support/MP/Host

To open the MP Host Folder from the MP Host plugin, on the controller's window,
right click and Select Presets > Show Presets Folder and it will open the MP/Host folder. 

See video

4. Show Preset Folder - Go to the MP/Host properties folder

To open the ~/MP/Host folder in Windows file explorer or the MacOS Finder:

1. Load the MP Host plugin in your DAW and open it

2. Right-Click on the MP Host window empty area and navigate to "Presets/Show Preset Folder"

See video here

 

5. Finding your existing third party plugins

Load up the MP Host Single FX plugin and click on the Controller Icon button. 

The window of the MP Host plugin will open. Right click on the empty area. 

Click on the PLUGIN LIST button.

The first time you do this, it will display a message that MPH is "Reading Installed Plugins". Depending on how many plugins you have, it will take a few seconds to complete. 

The MPH scans quickly your installed plugins in the standard VST and VST3 folders, even if you have them in other sub-folders. 

The MP Host does not scan in depth the plugins at first. To save time and not having to wait for the dreadful scanning process, the MP Host reads and display just the filenames of plugins in their folder at first and fully scans a plugin once you choose to load/use the plugin.

On Windows the path scanned for VST2 is     

and for VST3 is C:\Program Files\Common Files\VST3

The Plugin List will show all the plugins installed on your computer, however you should use this to load up a plugin and create an MP Host preset where it will load the plugin, its state, the mappings and background images. See MPH Presets

Plugins not shown in the Plugin List

For Windows, if VST2 plugins are not shown in the plugin list see this article.

For Mac, if the Plugin List does not show all the plugins you have installed, you may need to reset the permissions as shown in this article or check that these were not added in the ~/MP/Host/Plugin-Exlude-List.txt.

Category, Manufacturer and Version columns 

When you first scan (Quickscan) the plugin list, you will see that the Category, Manufacturer and Version columns will not have any data. These columns will be filled once you open a plugin for the first time, or right click on a plugin and select Scan.

Until installed plugins are opened once or perform a right click > Scan, will be displayed in the plugin list of both MP Host types (instruments and effects).

You will notice instruments and effects are shown in the same list, until you open or right click > Scan them for the first time. When you scan an instrument while in MPH FX you will see the plugin be removed from the list. It will only now appear in the MPH Instrument Plugin List. 

The same applies to audio FX while in MPH Instrument.

Loading an incorrect type of plugin

If you try to load an instrument plugin in the MPH FX you will get a pop up window saying that you are trying to load the wrong type. The same will occur if you try to load an audio effect plugin in MPH Instrument.

Waves Plugins Waveshells

Waves plugins because they are bundled in a shell, do not have this option. Instead, you have to find the Waveshell in the list and right click > Scan. The MPH will scan the Waveshell and populate the list with the Waves plugins included in the bundle shell. You have to scan each Waveshell.

If there plugins missing (VST2/3) after you scan the Waveshells, check the Plugin-Exlude-List.txt file (see next section). Delete the Plugin-Exlude-List.txt file from the ~/MP/Host folder and scan the Waveshells again. The missing plugins should appear in the plugin list after you press the Quickscan button.

If you have installed a new or older Waves package of plugins and plugins are missing, make a backup of the host.properties file and delete it. Then open again the MP Host so that a new one is created. Then select your target monitor and scan for plugins again, including the Waveshells.

For plugins not showing up in the MP Host on MacOS also check this article.

Excluding Plugins from the list

When you right click on a plugin, you also have the option to add it to an Exclude list, which is a text file placed in the MP/Host directory.
This excludes plugins which will not be scanned next time you perform a Quick Scan. 

If you want to remove plugins from the Exclude list, you can delete them from the ~MP/Host/Plugin-Exlude-List.txt. 

If you want to delete them all in the exclude list, you can just delete the Plugin-Exlude-List.txt file.

Waves plugins also don’t have the option to be added to the Excluded list because they belong in a shell.

When you Install new plugins, perform a quick scan so that MPH can locate these plugins.

If a plugin causes the MPH to crash during right click > Scan, it will be added automatically to the Plugin-Exlude-List.txt file. This includes Waves plugins as well during scanning Waveshells.

On Waves v15 on Windows, delete/move the GrandRhapsody.bundle folder from C:\Program Files (x86)\Waves\Plug-Ins V15 before scanning the Waveshells, as this is not compatible with the MP Host. you can place it back after scanning the Waveshells with the MP Host.

Searching for plugins

Searching for plugins is easy. You can just type in the bar on top of the list and it will search the manufacturer and plugin name once you press enter. The Manufacturer column will only be searched if a plugin has been opened at least once, or has been scanned using right click > Scan.

Reporting Issues with Plugins

If you would like to report plugin-specific issues please submit this form 

If your DAW crashes (for any reason) and causes the MPH to exit abnormally, the next time you open it you will need to click the Control & Display button twice instead of once (or the Plugin Holder area in the Multihost) in order to display the MP Host in the controller’s touchscreen.

6. Linking Parameters and Options

There are 3 methods to link parameters. See video

 

Automatic Mapping

Note that in version v1.7-d8422138--H2025-04-19--B2025-04-19 we have introduced the Auto Map function, which links all the parameters of a plugin upon loading the plugin from the plugin list.

It will set a different color to each encoder, unless:

- the parameters belong in the same group (plugins can have parameter groups, see U-He, Fabfilter)

- the parameters are not in the same group and the next parameter begins with the same 3 letters of the previous parameter, it will set the same color as the previous parameter (for example, Delay Type, Delay Size, Delay Mod...)

This option is enabled by default and it can be disabled via the right click menu.

 

Method 1 - Mapping/Linking one software encoder to a plugin parameter

Click or touch on the “Link” button to activate the Linking Mode, then click on the hosted plugin’s parameter you want to control,  then click on the MPH encoder you want to link or move the encoder you want to link. 

The “Link” button becomes not highlighted and now all three, the plugin’s parameter, MPH software encoders and the controller’s hardware encoders are linked. Moving either, will move the other two. 

You will notice that the linked parameter’s name is now set to the encoder linked. You can double click and edit that name. The MPH links parameters that are set to be automatable in the hosted plugin and retrieves the names of these parameters.

You cannot map the same hosted plugin’s parameter to more than one MPH encoder on the same page, however you can remap a hosted plugin’s parameter again on another page. This is handy when you want to control some parameters in every page. For example, you may want to control the filter section of a virtual synth on every page.

When linked, an encoder gets the value of the hosted plugin’s linked parameter.

In version v1.7-d8422138--H2025-04-19--B2025-04-19 the link button works in continuous mode. This means you can click/turn an encoder and continue to link parameters. You may select an encoder or the parameter first and it will still link them. 

For example, if you link the Cutoff parameter to encoder 1 in page 1, then link the Cutoff again in page 2, page 3 and so on, all links will be connected to encoder 1 in page 1. 

This is done so that we don't report to the DAW the same parameter multiple times. 

Only the firstly linked parameter will be reported to the DAW as an automatable parameter. 

You can use the encoders in other pages to control the Cutoff and if you record automation it will be recorded regardless of which page you are.

In the case of the Multihost, you will notice that you cannot assign an automation ID (it is greyed out) on encoders that have been linked with the same parameter in other pages. This is done to prevent reporting the same parameter to the DAW as an automatable parameter.

You can replace a linked encoder too. Press the Link button, click/move the parameter you want, click on the onscreen encoder you want and it will replace it with the new parameter. It does not replace it if you turn the physical encoder.

 

How to troubleshoot issues when linking parameters


Some plugins (Waves, Plugin Alliance, Kush and others) may be reporting multiple parameters at once. In this case the single LINK parameter method will not be able to link the parameter.

The MP Controller controls parameters reported by third party plugins as "automatable". These are the same parameters your DAW has access to and can control via automation. To check which parameters are automatable you can click the LINK GROUPS button and see the list of parameters that can be linked to encoders. You can link parameters via the LINK GROUPS method as well.

If you are having issues with a specific plugin you may try other formats of the plugin, VST2, VST3 or AU on the Mac as there have been cases where on format may not link parameters properly and another format links parameters normally.

If the parameter is linked but does not behave smoothly when turning an encoder you can enable ABS (absolute mode) on the encoder under Encoder Options.

Lastly, ensure that you have the latest version of the plugin you are using. There have been reports on some older versions of plugins (like PA plugins) that were not reporting their parameters correctly and this was addressed in newer versions of the plugins.

 

UI rendering Issue on Windows with specific VST3 plugins on some DAWs

If you encounter an issue with VST3 plugins (like Plugin Alliance) not updating the UI when moving the hardware encoders, use VST2 plugins instead.

We were able to confirm the issue in Ableton Live 12 with VST3 P.A. plugins, however in other DAWs like Reaper this issue does not occur.

 

 

Method 2 - LINK MULTIPLE  

Mapping/Linking many parameters at once

Click or touch on the “LINK MULTIPLE” button and it will show a list on the left of the MPH big window. Begin clicking on parameters on the hosted plugin. The parameter names are added to the list. To remove a parameter, double click on a parameter name on the list.

It is possible to assign colors to each parameter to be linked by clicking on the color cell in the parameter row. The selected color will be automatically assigned to all previous rows until a row with color assignment is found. This makes it possible to assign colors to groups of parameters (ie ADSR). To change a color just click on the cell and the color palette will appear.

It is not possible to reorder the parameter in the list. Once you are finished with the parameters you wish to link click on the “LINK MULTIPLE” button again and it will ask to enter the encoder number (0 to 127) to begin linking the parameters.

If you want to link parameters which are already linked again in another page, then you need to be in that page when you initiate the link multiple procedure and enter the encoder number that corresponds in the page. 

 

 

Click on the Unlink button and then click on the encoder to unlink it. See video

Note that in version v1.7-d8422138--H2025-04-19--B2025-04-19 the unlink button stays activated so you can unlink multiple parameters. Press the unlink button again to stop the unlinking process.

 

16 Pages of available encoders to be linked to parameters

With the April 2024 update, the MP Host has increased the number of parameters that can be controlled, from 128 to 512 parameters, allocated to 16 pages. Each page can carry a title which can be set by "double right clicking" on the lower area of the button, for the text editor to appear.

The Pages are divided into groups of 4 pages per group, a total of 4 groups.

Group 1: Pages 1 -4, Group 2: Pages 5 - 8, Group 3: Pages 9 - 12, Group 4: Pages 13- 16

Each Group carries the following encoder IDs:

Page 1: 0 -31, Page 2: 32 - 63, Page 3: 64 - 95, Page 4: 96 - 127 

Each page can carry its own background image.

 

Here are video 1  and video 2 on how to link parameters of plugins

 
Method 3 - Link Multiple parameters via Link Groups

See here for the Link Groups method for linking parameters.

 

 

Learn from Encoder

When you open MPH, the default preset has already mapped the controller’s encoders to the MPH encoders, from CC 0-31 in page 1, CC 32-63 in page 2, CC 64-95 in page 3, CC 96-127 in page 4, and this repeats for the next groups of pages (ie page 5 has encoders with CC 0-31 and so on). 

To see the CC numbers right click on the controller window and choose the ENCODER OPTIONS from the right click menu. 

The CCs are editable and you can change the numbers as you like. You can have the same CC on more than one encoder. This allows you to create macros and control more than one parameter per encoder.

See video on controlling multiple parameters using one encoder.

The Learn From Encoder button allows you to control a parameter that has been linked to another encoder. 

Let's say you have linked 3 parameters on 3 encoders and then you want to control all 3 parameters using one encoder.

One way of doing it is by manually going and changing the encoder CC IDs

If you set on all 3 the CC to 0, then the first encoder (encoder 0) will be controlling all 3 parameters.

The other way of doing this is by pressing the button Learn From Encoder, click/touch on the parameter's virtual encoder on the screen and then turn the encoder you want to use.

The linked parameter learns and has now assigned the CC from the encoder you have turned.

When you do this on multiple parameters you control multiple parameters with that one encoder.

Furthermore, you can adjust the Range, Polarity and Resolution on each linked parameter so that they behave differently when you turn an encoder. 

An example would be to control the Resonance and Cutoff parameter with one encoder. However, you want the resonance to perform a less change in value than the Cutoff. In this case, you increate the Res (resolution) on the Resonance and it will change in value less in comparison to the Cutoff when you turn the encoder. 

 

 

Single MPH Control and Display (the Controller icon on the small window) 

  

With MPH, you can control what you see on the controller’s screen. When you press the Control and Display button of an MPH (the Controller icon), the control is transferred to that selected MPH instance. The controller icon gets a yellow highlight and it means this is an MPH instance that interacts with the controller. When you click on another MPH instance, the button gets a yellow highlight  and the controller is now interacting with that selected MPH instance. 

When you close the MPH plugin small window, the MPH stops receiving any communication with the controller.

When you have multiple MPH instances open in the same DAW project and you click on the Control and Display one MPH instance, it will sync the controller by sending to it all the parameter values and page number of the MPH Instance.

When the small MPH plugin window in the DAW is closed and you open it, it will automatically open the plugin in the controller’s screen. This means you don't need to click Control and Display to open it in the controller.

 

 

Sending CC messages to hosted plugins

The MP Host plugin can now send CC messages to hosted plugins. This is useful as some plugins make certain parameters to work only with CC messages, for example changing the presets. CC messages unlike automatable parameters are not bidirectional (from/to the plugin). A plugin can only accept CC messages, therefore when moving a parameter with the mouse or when changing presets on the hosted plugin will not update the MP Host and the controller. This is because plugins don’t have MIDI interfaces to transmit CC messages. 

To activate sending CC messages per encoder select ENCODER OPTIONS from the right click menu and check the yellow box.

If the hosted plugin can accept CC messages and has MIDI Learn functionality you can send CC messages from the MP Controller. The CC message ID sent to the hosted plugin, is the same as the CC ID in the ENCODER OPTIONS per encoder. Note that CC ID 0 may not be received by certain plugins.

When CC sending is active, the M-P-R and Resolution options do not apply to the encoders.

 

 

Pitch Bend automation not playing back

In the case you have recorded pitch pend automation with your keyboard for a virtual instrument, depending on the instrument it may not playback the pitch bend automation and/or cause other automated parameters to not work during playback. In this case, link the pitch bend parameter to an encoder and record the automation in the DAW using the encoder.

7. Automation in the DAW

Single MPH Automation

The MP Single Host reports the parameter names of the hosted plugin (ie Cutoff, Resonance etc). The parameters to be automated need to be linked on encoders so that they can be reported to the DAW.

In Ableton Live, you click on Configure and move the parameters with an encoder or the mouse and it will appear on the plugin area, as usually done with any other plugin.

(Ableton Live update: If you are using the AU version of the MPH you need to have one automation point before recording automation in Ableton Live, in VST3 this is not needed)

Multi Host Automation

The MP Single Host reports the plugin and parameter names of the hosted plugin (ie Cutoff- Sylenth1, Resonance - Sylenth1 etc).

The parameters to be automated need to be linked on encoders so that they can be reported to the DAW. 

In the Multi Host, you need to set in the ENCODER OPTIONS the parameter ID to be automated. This is the number with red font on the bottom right corner in the ENCODER OPTIONS (see below). 

To automate in the Multi Host, click ENCODER OPTIONS, there are 2 options:

1. The automated method

From the right click menu select "Set parameter ids" and it will automatically assign ids to all encoders that have been linked but don't carry an automation id. 

This option works per plugin slot and the ids will continue to increase from slot to slot. For example, if you have linked 4 parameters in the first slot, then it will use ids 1 to 4. On the second slot it will use ids 5 and onwards.

In Ableton Live, you click on Configure and move the parameters with an encoder or the mouse and it will appear on the plugin area, as usually done with any other plugin.

2. The manual method

set an ID in the red box from 1 to 128, 0 means automation is disabled and it’s the default value. 

Once you set the parameter number, move the parameter so it is being recognized by the DAW (like you would normally do automation without the MPH) and that’s it. You can only use one automation ID per encoder. If you enter an automation ID number (1 to 128) that is already used you will get a pop up notifying you where that id is being used so you can use another one. When saving a multi host preset the automation IDs are not saved in the preset.

See video

In the case of the Multi Host, you will notice that you cannot assign an automation ID (it is greyed out) on encoders that have been linked with a parameter which has been linked on an encoder in another page. This is done to prevent reporting the same parameter to the DAW as an automatable parameter.

For example, if you link the Attack parameter in page 1 and then link it again in page 2, you don't need to enter an automation id on the encoder in page 2. You will see that the id field is greyed out and it will use the automation id from page 1. This way we report only one time the parameter to the DAW and avoid conflicts.

For linking the same parameters in multiple pages see here

Update: In the v16-2d9a51a2--H2023-12-19--B2023-12-19 version of the MP Host, it reports the names of the plugin parameters to the DAW for automation.



8. Side Chaining

You can use side chain in the Single and Multi FX Hosts. Instrument hosts do not accept side chain signal.

To side chain, send the side chain signal on the MP Host from your DAW as you would normally do with any plugin.

Then enable the side chain feature on your hosted third party plugin.

9. MP Host Presets

There are 3 preset types in the MP Host plugin (MPH):

Loading a third party plugin from the Plugin List menu in the MP Host plugin, will not load the linked parameters to encoders. Loading a plugin from the Plugins List menu will allow you to link parameters, and save it as an MPH Single xml Preset.

An MPH Single Preset xml, loads the hosted third party plugin, mappings to encoders with colors, the state of the plugin as it was last saved and optionally, background images per page.

Comparison of the MP Host presets

Preset Type

Loads the third party plugin

Loads links to parameters (mappings)

Can be loaded in the Single Host

Preset File 

Extension

Single Host presets

Yes

Yes

Yes

.xml

Multi Host presets

Yes

Yes

No

.mxmli for instrument and .mxmlf for audio effects

MPH Link presets

No

Yes

Yes

.mphlink

The Single MPH presets are saved in .xml format. The MPH single presets include (save):

These are saved via the button from the controller screen on the top left corner.

There are 3 ways to load a MPH xml preset. 

1. The first method would be from the top left corner of the main window to use the Open Button.

2. The second method is by right clicking on the background area of the MPH and select Presets.

It will show you the Preset structure as it is on your hard drive, the main category being a folder and in the folder you will see the plugin list which corresponds to the preset xml files saved. Each preset xml must be saved in a folder to be seen by the right click menu of MPH. This is very handy because you can categorize your presets as you like and this reflects the folder structure as it is on your hard drive. (See more info below in the section Preset Categories)

3. The third method is by using the MPH Presets button

To remove the loaded plugin, right click on the background area of the MPH and select Remove Plugin. It will remove the hosted plugin, background image and all mappings and load the default.xml.

(The default.xml cannot be overwritten from the MP Host and you should never manually overwrite it because it may create loading issues)

The Multi Host presets are saved in .mxmli for instrument and .mxmlf for audio effects.

The Multi Host presets save whatever is loaded at the given time in a multi MPH. It’s a preset that holds a chain of multiple plugins (or multiple single MPH slots). These are saved from the Multi small window.

Additionally, while using the Multihost the controller window provides the same menu to save MPH single .xml presets. This is because the multihost is a collection of single MPH plugins (or a chain of single MPH plugins). 

This means that from within the Multihost you can open Single Host .xml presets from the menu on the controller window or the right click menu as shown above.

The MP Multi Host. Each slot (row) of the Multi host is an MPH Single Host plugin

Preset Categories in the MPH Single xml presets

There is an option to create a Preset and have it listed in the MPH Preset Menu. Go to Presets again and select "New Category". A Category is a hard drive folder created inside the Presets folder (under ~\MP\Host\Presets). The MPH plugin will read folder items that exist inside the Presets folder and list them on the menu. 

Therefore, if you create a category and a preset, it will create a folder on the hard drive and the preset will be placed in that folder. The folder and preset will be listed in the MPH Menu.

The 3rd type of preset of the MP Host plugin 

(introduced in version v16-a91f8a59--H2022-08-10--B2022-08-11) 

is an additional portable type of preset with extension mphlink. 

These presets carry the

But unlike the MPH xml presets, do not save/hold the state of the plugin or reference to the plugin.

The mphlink presets should be loaded after a third party plugin is hosted/loaded in the MP Host.

This makes these presets portable, cross platform (Mac/PC) and cross plugin type (VST/2/3/AU) compatible that can be easily shared.

For example, if you have created an mphlink preset on an AU plugin on a Mac, you can use this preset on a VST in Windows. This provides more flexibility to create presets for many plugins and share them with users. 

The mphlink presets are saved in a folder under the MP Host folder at  

Windows: C:\Users\USER\AppData\Roaming\MP\Link Presets

Mac: ~/MP/Host/Link Presets

IMPORTANT: Before extracting from the zip file the downloaded MPH Link preset files, go to the MP Host and right click. From the menu go to Link Presets and choose Save. 

The MPH plugin will generate the folder named "Link Presets" in the MP Host folder ~\MP\Host\


Then, from the right click menu choose to Open the MP Host folder.


Create an xml preset from an mphlink preset.

We provide portable mphlink presets so that you can create your MPH xml presets.

  1. Load a third party plugin you want to control in the MP Host plugin. 

  2. The load an MPH LINK preset.

  3. Then save it as an MPH xml preset 

The next time you want to use that plugin, you will load the MPH xml preset which will automatically load the third party plugin as well.

Tutorial videos:

1. How to extract and load the .mphlink MPH LINK presets

2. How to create an MPH preset from an .mphlink preset

You can download the MPH Link presets zip file from your account.

Here is the up to date list of MPH Link presets.

Opening the mphlink presets

image.png

"Open by Name" option for mphlink presets (default)

This option uses matches plugin parameters with encoders using the name of the parameter instead of the parameter id. This is useful because some plugin developers don’t use the same IDs on different plugin types. For example, VST2 ids may be different from AU ids. Loading the MPH Link Presets using this method, solves this problem. For example, if the parameter name is Cutoff and the mphlink preset has a parameter named Cutoff it will match it.

"Open by id"

This option maps the plugin parameters in order using the index number of the parameter. This method may cause some parameters to be mapped on another parameter in the case that the plugin developer has changed the order of parameters.

Changing 3rd party hosted plugin presets

When you change or load up a new preset on any hosted third party plugin in MPH, the hosted plugin sends the new loaded values in its parameters to the host plugin and the controller. 

There are some exceptions though to this rule. Some VST2 plugins do not send a notification to their DAW automatically when they change via a preset change. Such an example is our beloved Reveal Audio Spire Synthesizer. 

Although this is not often found in third party plugins, if you notice the MPH encoders not being updated then hit the Sync button to receive the current parameter values from the hosted plugin. This is the only purpose of the Sync button and should only be used on such occasions. If you have changed a preset in such a hosted third party plugin and have not clicked on Sync and you Saved or Save As, the MPH encoders will automatically sync with the hosted plugin and be saved properly in your preset. 

Updating MPH Presets when new 3rd party plugin versions are released

If a new version of the third party plugin is released by a third party vendor, depending on the update there is a possibility (although rarely, ie in the case of N.I. Kontakt) that the updated version will cause the MPH (and perhaps your DAW) to see this update as a new plugin. 

In this case, your MPH xml presets may not show the third plugin plugin when loaded.

Install the update of your plugin as you would normally do and load up the MPH xml preset you have created. 

If the hosted 3rd party plugin is not showing up in the main window, choose it again from the PLUGIN LIST. It will load the plugin in the already loaded preset.
All the linked encoders should work and there is no need to link them again.
Then, Save the MPH Preset again. 

Alternatively, you can save your MPH xml preset as an mphlink preset and load it after you load the third party plugin. Then save it as an MPH xml preset.

In the case you have created M- file plugins on the Mac, choose Create Plugin to replace your M- file with an updated one.

Autosave

The MP Host plugins, single and multi host, autosave the current working instance as autosave.xml every few seconds.

10. MP Host Favorites

MPH Favorites

The Favorites screen has placeholders for favorite plugins, so that they can be loaded instantly using the touch function or mouse click. 

For every placeholder, an image can be selected to be displayed and an MPH preset. Clicking on touching on the placeholder’s area loads the MPH preset.

Right click on a box area in the Favorites window and select the placeholder’s favorite mph .xml file preset. The placeholder will take the name of the .xml preset file. 

Within the same menu you can select an image of your favorite plugin. You can take screenshots of your plugins (using your OS or other software) , save them as jpg on your computer and then select these screenshots via the Favorites menu to appear in each box. 

Note that the images selected will be automatically resized and then copied in the ~/MP/Host/Images/Favorites folder.

See video on how to create Favorites

Suggestion for taking screenshots:

Install Lightshot — screenshot tool for Mac & Win 

Load up a plugin in the DAW or the MPH.

Take a screenshot of the plugin by pressing "print screen"

Then click the Save icon to save it on the desktop.

Then choose that saved image file to set it as a favorite background.

 

Categories

The favorites are separated into categories, each category has a placeholder in the top two rows of the favorite screen. The category placeholders can be renamed by right clicking and typing the name you want.

There are 16 categories of favorites and each category can carry 24 favorite plugins, in total 384 can be selected (384 for audio effects and 384 for instruments).

The favorites are separated for audio effects and instruments, so you can set different categories and favorites for audio effects and instruments.

The favorites screen can be optionally set to load on startup from the same right click menu.

The above options can be selected by right clicking on each of the favorites placeholders.

The favorites are stored in two separate files FXFavorites.xml and InstFavorites.xml in the ~/MP/Host folder.

Here is a demo video on favorites

 

Moving to a new Mac computer

In the case you will get a new Mac, copy the MP/Host folder to the new Mac (delete the hardware id and mph license files and get ones from the server). 

If your username is different from your previous Mac, you can open FXFavorites.xml and InstFavorites.xml files in a text editor and check that the path to presets is the same. 

You can change it by doing a find and replace ALL in the text editor.

For example on your previous Mac, it could be:

/Users/USERNAME/Library/Application Support/MP/Host/Presets/Comp/preset-name.xml

And on your Mac, if your username is different, then the absolute path will be different. You can replace the username with the current one for all favorites and the path will be correct again.

11. Encoder Options

Encoder Resolution and M-P-R Options

Each encoder has a number of options and these become visible by each MPH encoder when the M-P-R checkbox is checked.

Each encoder has two working modes, Absolute and Relative. 

Absolute mode is activated if Abs checkbox is checked. In absolute mode, the encoder receives and sends standard MIDI cc messages, each message contains the value, hence it is absolute. There are 128 CC values, therefore the standard resolution (steps) of the encoder is 128, 0 to 127. If Abs is checked, the M option becomes available. 

M checkbox for Magnitude for Absolute mode. This is a scaling factor for each encoder when it receives MIDI messages from the controller, ranging from 1 to 50. So your incoming CC can be scaled accordingly. If you set the Magnitude to high values, such as 50, then the encoder will behave like an on/off switch. 

Relative mode is activated if Abs is unchecked. Relative mode interpretes MIDI messages from the controller as pulses of plus or minus (-1 or +1) and sends them to the software encoder and to the target plugin parameter. In Relative mode we can set the resolution (shown as Res) of each encoder in the Resolution box from 1 step to 999 steps.  Absolute and relative modes may seem the same but with the In absolute mode, values transmitted from the controller are absolute (0,1,2,3..127) once we reach CC max or min (value 0 or 127) anything sent after max/min will not make any difference, but in relative mode there is no max or min, it just keeps on increasing or decreasing.

The following can be used whether in absolute or relative encoder mode.

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

R checkbox for Range. Set the minimum and maximum range, from 0 to 127, you want the Virtual Encoders to respond. If Polarity is checked then the range is inverted (the min becomes max and max becomes min).

CC checkbox for Control Change Number. Set the same CC number, by clicking in the CC box, to multiple virtual encoders and create macros. Combine this feature with M-P-R and you can create complex macros.

Red font number for multiplugin automation ID (explained above). Shows up only in Multiplugin host.

High Resolution Button

The Hi Res button located on the bottom right of the big window allows you to temporarily select a higher resolution factor for the encoders. The right button allows the selection of the factor from 2 to 10 and the left button enables/disables the function. This setting is saved in the MPH xml presets.

Oversampling

Oversampling will operate the hosted plugin in a sample rate multiple to that of your DAW project. This is a unique feature of the MPH, and it is made possible because MPH hosts the 3rd party plugin. The Oversampling options are 2x, 4x, 8x. MPH features anti-aliasing filters when using oversampling. Oversampling tends to be most useful and shows results when pushing a plugin to its limits or when using overdrive/distortion type of plugins. It is standard that the oversampling process will consume CPU and introduce some latency, which is reported to the DAW. When you choose an oversampling option, the hosted plugin will automatically reload in MPH. If you plan to use oversampling with specific plugins, it is best to test that it works well with the hosted plugin, prior to using it in a work project. Some plugins, when oversampled too high, will create problems, even crash the DAW. This is outside of our control.

This video explains well the process of oversampling a plugin.

Linked Parameters List

The Linked Param button displays a searchable list with all the parameters that have been mapped to an encoder. This is useful when a lot of parameters have been linked and you want to check the corresponding encoder of a parameter, or to reference automation of an encoder.

12. The MP Multi Host

Plugin holders in the Multi Host

To open a plugin on the controller monitor click on the area on and around the lcd screen on the plugin holder.

The lcd area will display the name of the third party plugin loaded. If you save an MPH xml preset, then it will display the name of that preset.

When you add a new plugin holder an empty instance of the single MPH is created. Each plugin holder can host one plugin. To remove a plugin holder right click on the red area and select Remove Plugin. A pop up menu will appear to ask if you want to remove the plugin holder. When a plugin holder is removed it removes the plugin hosted in it as well and there is no undo for this.

When you click and drag up/down on the area marked in red below on the Multi Host of each plugin holder you can change the order of the plugin.


Add/remove plugin holders (slots)

Right click in the area shown below in red on a plugin holder or left click on the corners of the slot (where the little screws are). 

Or

You can add a new slots on the Multihost from the touchscreen from these buttons

 

Changing the order in the audio effect MPH will affect the audio signal path which is routed from top to bottom plugin holders, feeding from one plugin holder to the next. Changing the order of the instrument MPH just affects the visual order but not the signal path as in the instrument audio is output in parallel for every plugin loaded.

When the MPH plugin window in the DAW is closed and you open it, it will automatically open the plugin holder that was selected last, in the controller’s screen.

Within the Multi host you are able to bypass and solo plugins, change their order of audio processing in Audio effects by dragging up/down and save Multi Host presets. In the Instrument version, you can still drag the plugin slots up/down but since the processing of audio is parallel (each plugin instrument produces audio concurrently) changing the order will only affect viewing order on the small window.

Power Off/On button: Default is On. When Off, It unloads the plugin completely from the host plugin and the CPU usage is zero. This, as expected, when off uses less computer RAM but when it is turned off and then on it will take a couple of seconds to reload the plugin.

Plugin Bypass button: Default is Off. When On, It bypasses sending audio instantly to the hosted plugin and CPU usage is zero. The hosted plugin remains loaded in the host plugin. Bypass works faster than power on/off.

The Off/On and Bypass operations on the Multi host should not be performed during playback as unpredictable latency will be introduced. For the Bypass, if the hosted plugins do not have any natural latency, the Bypass will not cause the audio be out of sync. If there is latency reported by the hosted plugins, then the Bypass will actually bypass the plugin from the routing chain of the Multi host, thus causing the audio to fall out of sync. Therefore, the Bypass on the touchscreen should be used instead of the Multi host one during playback.

You can also bypass a plugin slot from the controller window by long pressing on the button in the Multi host menu. Long pressing again will remove the bypass from the slot.


Solo button: Default is Off. When On, the selected plugin is soloed and the rest of the plugins stop processing audio and therefore do not consume any CPU. You can Solo multiple plugins.

Output led meter: The meter shows grey when no output is present, green when signal above -40 dB is preset up to -6dB, yellow when signal above -6 dB is present up to 0 dB and red when signal above 0 dB is present. Of course some plugins may produce sound that is not clipping above 0 dB because we are in the digital domain, but some other plugins that are emulating hardware may be producing unwanted artifacts, so the meters should be taken into consideration according to the plugin hosted. As a general rule it may be safer to keep the signal under 0 dB so that you don’t have to worry about clipping.

Multi Plugin Control Button

As of version v16-a91f8a59--H2022-08-10--B2022-08-11 a new screen was added to the Multi host, where it allows controlling with the controller all the automatable parameters of the MultiHost. These are parameters that have been assigned automation ids. 

See this article for Automation in the MultiHost.

The purpose of this screen is that from a single screen we can now control parameters from multiple plugins hosted in the MultiHost. 

The screen is activated by clicking on the Multi Plugin Control button located at the top of the Multi host plugin.

Multiplugin Presets

The MPH stores its configuration, preset files and preset background image files in:

Windows: C:\Users\USER\AppData\Roaming\MP\Host

Mac: /Users/USER/Library/Application Support/MP/Host

multi host presets have an mxmlf file extension for audio effects and mxmli for instruments. They can be loaded via the multiplugin only. When you save a multiplugin preset it contains the current state of all loaded plugins including mappings, background images etc. However, it is still possible to Save individual xml plugin presets, with the Save button in the main controller screen, so you can use them in new future multiplugin instances. Saving a multiplugin preset will not automatically save individual single plugin xml presets.

Multi host maximum number of hosted plugins

We have set a 12 plugin holders limit in the multiplugin version. Although we don’t have to implement a limit, we did set one because in a DAW channel everything runs on the same audio thread. Even without the MPH all the plugins you load in a DAW channel run in a single CPU thread so that the audio processing is uninterrupted (not switching from one thread to another). Since, with the MPH you now have the ability to run 12 virtual instruments on a single thread, this can put extreme load on a single thread of the CPU, not because of the MPH but because of the number of plugins you have in a single channel. With a limit of 12 it means you can run 12 instruments and 12 effects with just one MPH instance for instrument and one for effects. Of course you can load as many MPH instances you want per channel, but even with the latest computers this may not be such a good idea, and it is in general better to spread the load across channels. We may increase this limit of 12 plugins in the future depending on feedback we receive.

In the July, 2024 update, the MP Instrument host (Single and Multi) plugin supports up to 16 stereo outputs



For setting up automation parameters in the Multi host see the article here

July 2024 update, for using the MP Host in Bitwig on Windows, see this article here

13. Background Images and Encoder Colors

Background Images

You can load background images to each page of the MPH. You can drag and drop an image, jpg or png format to the current page you are working on, from your file explorer. The image must be of 1920 x 1080 px resolution, jpg or png. The image will be saved when saving a preset and be placed in the Images folder on the same folder level as the Presets folder, in the MP/Host folder on your computer.


Encoder Background Colors

Right clicking on the inner area of each encoder will display a palette of colors which you can select to color code the encoders. It’s a good practise to color encoders that belong in the same group, like an ADSR envelope.  These encoder assigned colors are saved in multi host and single host presets.

14. M-Plugins on the Mac

Generate M-Plugins as Audio Units on the Mac

This feature is only available when loading MPH Single host as an AU and hosting AU third party plugins.

When you host an AU third plugin in an AU instance of the MPH in a new folder (which is displayed as a Category in MPH menu), you will see the option in the MPH Menu (right click in main window > Presets) to see the option Create Plugin. This will create a new .component file (AU) in /Library/Audio/Plug-Ins/Components/  that can be seen by the DAW as a new plugin.

Creating a new M-plugin is useful because when loaded in the DAW directly it will show the name that you chose.

This plugin's name will always start with "M-" so the file name of the plugin generated will be  

M-the_name_you_entered.component.  (Do not write the M- )

M-plugins have the exact same  functionality as the MP Host. However, in an M-plugin you cannot remove the hosted plugin.

Once you create a new M- plugin, scan for your plugins in your DAW or in case of Logic Pro X reopen Logic and it will scan and find the plugins. 

New AU plugins need to register with Mac OS so sometimes, depending on the DAW a reboot may be necessary. If your newly created M-plugin does not pass the validation scan in Logic, reboot the Mac and open Logic again. It should scan it again and it will pass validation. Otherwise you can manually scan it in Logic's Plugin Manager.

This M- plugin has all the settings, mappings, and references to the third-party plugin. It can be recalled from the MPH Menu or your DAW.

The default xml preset for the M-plugin saved in the .component file is the xml preset you have created. So, when you load the M-plugin, it will open the xml preset you created, without having to load another preset. Last, you can load other presets in the M-Plugin, because like mentioned before, the functionality is exactly the same as the single MPH.

If you save the M-plugin preset in a folder inside the ~/MP/Host/Presets folder, then the folder name will be used as the vendor (manufacturer) name for your M-plugin.

For example, if you save a Pro Q3 by Fabfilter in a folder ~/MP/Host/Presets/FabFilter then in your DAW you will find the M-plugin listed under the manufacturer FabFilter.

In Logic's expandable plugin menu you will find your M-plugin under manufacturer FabFilter.

If you don't use a folder name and save it directly in ~/MP/Host/Presets/ then the manufacturer will be set as "AU".

 

 

Update M- AU Plugins

This is an option in the main window menu, that should only be used when you have installed an updated version of the MP Host. When selected, it will place the new version of the MP Host inside the M- plugin  .component files. 

When you download and install a new version of the MP Host, click on Update M-Plugins option and it will update all your M- plugins to the newest MP Host version.

After the update you will see a report of all the plugins updated to the version updated.

 

 

Troubleshooting

M-plugins are not being created

If the M-files are not being created in the Audio Units directory
/Library/Audio/Plug-Ins/Components/ , (you cannot see the newly created M- plugin in the Finder under the components folder) it is because the OS permissions do not allow the MPH to write the new M-file. 

To solve this issue, run in a terminal:

sudo chmod 777 /Library/Audio/Plug-Ins/Components/

It will ask for your Mac's password. Type it and hit enter. 

There should be no output on the terminal and you may close it. 

Reopen Logic and try to create the plugin again.

M-plugins not loading in the DAW

If you have migrated to a new Mac, and copied over the plugins from the previous Mac, it may cause Mac OS to prevent opening M- plugins due to permissions.

Run in a terminal:

sudo chmod -R 777 /Library/Audio/Plug-Ins/Components/M-*.component

It will ask for your Mac password, type it and hit enter. 

There should be no output on the terminal and you may close it. 

Reopen Logic Pro X or the DAW and try to load the M-plugin.

 

How to remove M-plugins

Delete the M-name.component file from /Library/Audio/Plug-Ins/Components/

Open Logic's plugin Manager and search for the M-plugin. Select it and then choose the "Reset and Rescan Selection".



15. Plugins with external VST3 AU Presets

Some vendors create their plugin presets as .vstpreset files for VST3 or AU plugins. One such example is Plugin Alliance plugins. When you host in the MPH such plugins, upon loading the third party plugin the MPH will search under:

Mac /Users/USER/Library/Audio/Presets

Win C:\Users\USER\Documents\VST3 Presets\

the folder with the plugin’s vendor name (ie Plugin Alliance) and within that, the folder with the name of the plugin loaded and it will display these vstpreset files in the menu on the controller’s window. 

When a plugin with VST3 Presets is loaded the MPH will automatically display a button on the top encoder row named “VST3 Presets”. This button brings up a list with the available VST3 Presets of the hosted plugin.

Alternatively, to view and load VST3 Presets: Right click > Presets > VST3 Presets

From that list you can choose any preset and it will be automatically loaded in the hosted plugin.


16. How to Reset the MP Host Plugin

All the settings and scanned plugins references are stored in the host.properties text file located in:

Windows: C:\Users\USER\AppData\Roaming\MP\Host

Mac: /Users/USER/Library/Application Support/MP/Host

To navigate to the host.properties file via the MP Host plugin see here

To reset all the settings and return to default delete or rename this host.properties file.

To reset the default preset, just delete the default.xml and it will be recreated the next time you load the MPH in the DAW.

When you delete the host.properties file your MPH presets will not be affected. When the host.properties file is deleted, you will need to select the target monitor the first time you run the MP Host plugin.

If when loading the MPH is loading a preset you created instead of the empty preset, delete the default.xml from the Presets folder.

17. Windows Unified Option

This option can be accessed from the right click menu. 

When it is unchecked (default), the hosted plugin has its own Window instead of being embedded the MPH Window. If checked, the hosted plugin will open inside the MPH existing Window. 

The default value is "unchecked - not enabled".


After you check the box, right click anywhere on the black area of the MPH big Window to display the menu.

Click again to hide the menu and this will reload the GUI of the hosted plugin and the change will take effect.

This "Unified Window" option is helpful if you are using multiple 4k monitors and you encounter the hosted plugin to appear outside the controller monitor. It ensures that the hosted plugin will always be placed at the center of the MP Host window.

This option is saved in a plugin xml preset so next time you recall your preset it will be part of it.

18. Hiding the controller window and moving the hosted plugin

These options is available via the right click menu.

This is particularly useful when working on a laptop and when you don’t have the MP Controller with you.

Hide Window will hide the controller’s big window and will show only the hosted plugin. The hosted plugin will have a title top bar and it can be dragged with the mouse. Closing and reopening the small MPH window, will hide the hosted plugin and display it in the center of the monitor. This option is global, meaning it will affect all plugins of the MP Host.

Show Plugin Top Bar will add a title bar to the hosted plugin and allow to drag the hosted plugin to another display with the mouse. You will still be able to control the plugin with the controller. This option is global, meaning it will affect all plugins of the MP Host. 

In the 2025-04-30 update, we introduced a new button on the left side of the top bar that restores the plugin window to its original position on the MP Controller.

image.png

Note: if you move a plugin to a different position and then resize it, the way the plugin handles resizing may affect how it appears when returned to its original location. In some cases, it might not be perfectly centered, and you may need to adjust it manually. To avoid this, use the plugin’s “Set Default Size” option (if available), save it with that size, and it will correctly snap to the center when restored.

Some plugins have automatic monitor resolution detection and change their size automatically when moved to a new monitor with a different resolution. Such plugins may shown cropped and magnified when hosted in the MP Host and moved to a monitor with a different resolution than the MP Controller.

19. MP Gain Utility

The MP Gain Utility plugin enables you to control the  +/- gain on your tracks from the MP Controller. With the MPGU plugin you can control up to 128 gain parameters.


Download

The MPGU can be downloaded from the user portal.
The MPGU plugin can be used with and without having the MP Controller hardware connected.


How it works

The MP Gain Utility consists of two plugins. One server plugin and one client plugin. Both are lightweight plugins and consume negligible amounts of cpu and ram resources.

The MP Gain Utility will display the manufacturer in your DAW as MPUT.

You only need to load one instance of the server plugin per DAW project. You will notice that it looks like the MPH plugin, except that the software encoders are set in the center by default.

Turning an encoder to the left will reduce gain, turning an encoder to the right will add gain. The values are displayed in dBs and the range is -40 to +40 dB. 

Once you load the server plugin (it can be on any track), then load a client plugin. The server plugin does not process any audio, it allows audio to pass through it unaltered. The client plugin processes audio with its only function being adding or subtracting volume to the signal.

Each client plugin carries an id starting from 001 to 128. Each id corresponds to an encoder on the server plugin and the controller.

For example if you load one client plugin, it will take id 001 and it will be controlled by encoder 1 on the controller and soft-encoder 1. If you load another one it will take id 002 and so on up to 128. 

You can load multiple client plugins per track, there is no limitation. For example, you can enter a client plugin before an audio effect and one after an audio effect, on the same track.

You will need to create a new client plugin every time you want to add one, not copying and pasting existing client plugins because the client will not take a new id.

You can edit the id on a client plugin by double clicking on it, so that it can be controlled with another encoder.

The server window will be displayed on the same monitor that the MPH is set to be displayed. There is no option to change the monitor on the server plugin as it reads the same properties file as the MPH.

Naming and Coloring

Once you add a client plugin go to the server plugin and name the next available encoder. For example, if you add a client on the Drum Bus and has id 004. This means that you are already using the previous 3 encoders.
So, double click on the name box on the server plugin and type in Drum Bus.

You can also assign a color to each soft encoder via right click at the edge of each soft encoder, just like in the MPH.

Reset to 0 dB

Click or touch in the center of each soft encoder and the value will return to 0 dB.

Automation

If you would like to record gain automation using the MPGU, you can do it at the track you placed the server plugin. Each encoder is automatable like in the MPH.

The client has no controllable parameters and it only displays the value in dB.

Total Recall

When you save your project, all the values and state of the server and client will be saved with your project. When you open your project everything will be recalled.

The MPGU, unlike the MPH, does not save presets.

Using it with the MPH

You can load the MPGU and the MPH in the same DAW project. The Control & Display button works as it does on the MPH. Clicking on the C & D button will close any open MPH instances and display the MPGU on the controller. Clicking on the C & D of MPH, will close the MPGU window and display the MPH.


How does the server communicate with the client? 

The server and client use the OSC protocol to communicate. The communication is done in one direction from the server to the client. The client does not transmit anything back to the server. Each encoder transmits data on a network port, starting at port 60000. Each client listens on a port also starting at port 60000. 

Each time a new client is created, the new client listens on one port higher than the previous one. For example, if you load one client it will listen on port 60000, if you load another one it will listen on port 60001 and so on.

20. Audiogridder - MP Host: AG-MPH Guide

         


Audiogridder - MP Host Integrated Guide


The Audiogridder project is an open source project that enables DSP processing of third party plugins outside the DAW. See here

We have created a modified version of the Audiogridder, called AG-MPH so that it works in an optimal way with the MP Controller.  See example videos Logic on Mac and Bitwig on PC, however the principle is the same for all DAWs.

To get the installer of the AG-MPH send us an email.

The latest AG-MPH version is v1.2.0-1328f91--H2023-09-08--B2023-09-09

Why did we make this?

Audiogridder, even when used on the same computer, utilizes much better the CPU and allows running more plugins than when running then directly in the DAW. In fact, on a recent test we did on a Mac M1, we found that we could run almost 3 times more - heavy on resources - Acustica plugins than when hosted the same plugins in Logic. (We were able to run 10 instances of an Acustica Eq plugin directly hosted in Logic. We were able to run 28 instances of the same Eq plugin via Audiogridder).


You can run the AG-MPH without additional latency by setting the buffer block size to 0, however for taking advantage of the DSP offloading we suggest to set it to 1 or 2 blocks of buffer size where the latency is hardly noticeable (that of course also depends on your computer and the DAW project you are running).


As the number of plugins loaded in Audiogridder increases, you may want to increase the buffer size (blocks) of the Audiogridder to avoid audio dropouts and the exact same applies when using the AG-MPH.

What we have changed

  1. After opening the AG-MPH plugin in the DAW, click on the + symbol and it will load an instance of the MP Host on the MP Controller. (It is required that you have the latest MP Host VST3 installed, Audio and Instrument plugins).


  1. The AG-MPH hides the small window of the MP Host, thus you don’t have an extra window floating.


  1. It automatically gets the name of the hosted plugin or preset from the MP Host and displays it on the AG-MPH slot.


  1. Selecting a plugin slot in the AG-MPH plugin automatically opens on the controller’s screen.


  1. We made the bypass coloring of the slot more obvious and now displays the word  “bypass”.


  1. The processing of DSP works and other settings/options, exactly as the original Audiogridder and we have not changed that.


  1. Switching from one instance of the AG-MPH to another, unlike the original AG, it un-highlights the current plugin slot and highlights the selected one. This applies when running the MPH host directly in the DAW. The two, AG-MPH and MPH single/multihost can be loaded in the DAW at the same time and switching from one to the other will un-highlight the previously selected slot.

  2. We added a Slot Selector. This allows to select plugins from the touch screen via the Select Slot button. To enable/disable the button from showing, uncheck the top-right box on the AG-MPH window. This is a universal option and it will affect all instances of the AG-MPH.


Prerequisites and Settings

You need to have the latest MP Host installed (after March 23, 2023) for the AG-MPH to work. The MP Host installer is not included in the AG-MPH installer. There are 2  separate installers.

You need to install the AG-MPH using the AG-MPH installer. It will install

  1. The AG-MPH server and AG-MPH plugin tray.

  2. On Mac, the AG-MPH VST3, AU and AAX, all universal binaries x64.

  3. On Windows, the AG-MPH VST3.

In Windows, the AG-MPH server is placed in C:\Program Files\AG-MPH\

Create a shortcut on your desktop or taskbar for convenience. 

On the Mac, it will place it in Applications.

For both Win and Mac, you only need to run the Server once.      

The plugin tray will automatically launch when you load the AG-MPH plugin in the DAW.

Check that you have these settings in AG-MPH Server (From the menu choose Settings)



Once you load the AG-MPH plugin in the DAW, click on "add server" and type in 127.0.0.1

This IP address (127.0.0.1) is a universal address on all operating systems for the local machine. By adding this as the default server you ensure that the AG-MPH will always connect to the local machine via the fasted route (instead of going through virtual ethernets or your router).


Check that the MPH Single Instrument and Audio effect were found and scanned by the AG-MPH

Right click on the AG-MPH icon on the task bar while it is running. 

Select the option Plugins.


You should see the 2 MPH Single Plugins. If you see any other plugins in red font you can ignore them.


Knowhow and limitations

  1. You can have both Audiogridder and AG-MPH installed on the same computer, however, you cannot run Audiogridder server at the same time you run AG-MPH server. Only one server can run at a time.


  1. When using the AG-MPH server, it automatically loads the MP Host plugin VST3. You cannot load directly in AG-MPH any other third party plugins, but only through MPH.


  1. You need to run the AG-MPH server app and then the AG-MPH plugin in the DAW, just like the original Audiogridder.

 

  1. If you plan to run an AG-MPH server on another computer, then the MP Controller should be connected on that computer, because the server is the app that runs and displays the hosted third party plugin. You can run AG-MPH on a Windows computer while running the AG-MPH plugin on a Mac computer, just like the original Audiogridder. See Video


  1. Via the AG-MPH plugin, you can connect on an AG-MPH server in the same way you connect on an original Audiogridder server.


  1. On the Mac, you need to give the AG-MPH permissions in the Mac Accessibility settings, so that it does not complain when starting the server, just like the original Audiogridder. Press the + button in Accessibility and navigate to AG-MPH to add it to the list.


  1. Audiogridder server scans all plugins on start. This is an option you should disable from the Server settings. AG-MPH and the original Audiogridder share the same settings, so AG-MPH will not rescan your installed plugins. However, AG-MPH has been programmed to only scan the MPH Single Audio Effect and Instrument.


  1. The AG-MPH was built using the codebase from Audiogridder version 1.2.0 stable which is the latest as of May 2023. 


  1. The third party plugins are being hosted by the MP Host and the workflow remains the same as when using the MPH in the DAW including presets etc.


  1. You can install MP Host updates when we issue them, and it will continue to work normally with AG-MPH. There will not be a special edition of the MPH in order to work with AG-MPH.


  1. There is no additional CPU load when using the AG-MPH, compared to the original Audiogridder. There is no additional latency either when compared to the original AudioGridder.


  1. AG-MPH should be set to “Chain Isolation” mode on the server settings (which is already the default)


  1. We noticed that the AG-MPH AU does not load on Ableton on the Mac, however the same issue occurs with the original Audiogridder AU plugin. The Ableton Live's 11.2 log says “Failed to initialize the plugin”. This may not be the case on your Mac. The AU runs fine in other DAWs. The VST3 works fine in Ableton Live.


  2. Resetting the Audiogridder server settings on the Mac (by deleting the files) will reset the AG-MPH as well. To reset Audiogridder/AG-MPH go in your home folder and Press Command+Shift+Dot this will show your hidden folders. You will have a folder .audiogridder grayed out and delete it.


      16. How to Uninstall AG-MPH on Windows:


17. When using Wavelab, for the AG-MPH plugin to connect to the server, an audio file needs to be imported in Wavelab and press play. See video here


Setting Permissions for AG-MPH server on the Mac


If you see this message when you start AG-MPH

Go to Settings > Privacy & Security > Accessibility


Click the + sign and add AG-MPH


Restart AG-MPH

Troubleshooting on the Mac


If you see an error, it may be that the VST3 plugin cannot be accessed by the AG-MPH.

AG-MPH works with MP Host VST3.

Quit the AG-MPH server.

Check that the MPH Host VST3 is installed in your VST3 folder.

If yes, let's reset the permissions, in a terminal run
sudo chmod 777 -R /Library/Audio/Plug-Ins/VST3
and it will ask for the password, enter it and it should return nothing.

Then reset Audiogridder/AG-MPH go in your home folder and Press Command+Shift+Dot this will show your hidden folders. 


You will have a folder .audiogridder grayed out and delete it. 
Then start the AG-MPH server and check that the plugin is listed:

When you reset AG-MPH, you need to check the server settings and set them again as described in the section above.

21. Activating the MP Controller on other computers

You will need to generate a new mph.license file if you plan to use the MP Host on another computer, but you don’t need to enter the controller serial again.

To generate a new mph license for another computer you need to upload the new hardware.id file and download the mph.license file. Then place the mph.license in the ~/MP/Host folder.

DO NOT USE HARDWARE.ID or MPH.LICENSE FILES FROM OTHER COMPUTERS.
YOU NEED TO RUN THE MP HOST TO GENERATE NEW ONES.

For every new computer you need to upload the new hardware.id file generated when you run the MP Host plugin the first time and then download the mph.license file. 

There is a limit on the activation server for 5 different computers.  If you need activation for more computers, please send us an email at hi@mpmidi.com.

If you see the message “License not found, Controller Not connected” see here.

22. Get the mph.license from the user portal

Open the /MP/Host folder as shown here and upload your hardware.id file in the user portal

The hardware.id file is automatically generated when you run the MP Host plugin.

If the hardware.id file is not being copied to the Mac's Desktop when trying to setup for the first time, see here

Download the mph.license and place it in the /MP/Host folder next to the hardware.id file

23. Receiving update notifications for the MP Host plugin

As many tend to keep their studio computers offline or behind firewalls, this would prohibit our plugin to connect on our server and check for updates.

We publish new versions in the mpmidi.com/latest-readme first page and on https://mpmidi.com/mph-versions.html

We don't have a notification system yet, but an easy way to get notifications for new versions is by registering at one of the following free services:

https://www.wachete.com

https://distill.io

https://www.followthatpage.com

and enter this link to monitor

https://mpmidi.com/mph-versions.html

24. Best Practice recommendation

MP Controller transforms your third party plugins into a hardware console so that you can control them as if it were hardware. 

We suggest that you start with one favorite and mostly used plugin, ie like an equalizer or compressor or synthesizer plugin you use all the time. Make the most convenient mappings/links to you and incorporate this in your workflow. 

After a few projects and heavily using it, you will feel like you know this interface and reach for the controls intuitively. Repeat this process with another plugin and so on. 

Trying to use and map many plugins at once and use MPH in every plugin, may not help improve your workflow as you introduce too many new things at once.

Enjoy your new controller!

25. Controlling UVI Workstation, Omnisphere by enabling Host Automation

The way the MP Controller works is by controlling automatable parameters of a third party plugin.
These are the parameters that can be automated in the DAW.
Typically, all parameters of a plugin are automatable (or at least the most)
This is a bidirectional communication method and instant. Much better than just sending CC Messages.

UVI Workstation and Omnisphere plugins require that you enable host automation in the plugin in order to automate parameters in the DAW, hence control parameters with the MP Controller.
See this guide:
https://support.uvi.net/hc/en-us/articles/360002133277-Automation-in-UVI-Workstation

To use Omnisphere VST3 in the MP Host on the Mac,
open the plugin list, search for Omnisphere,
right click on the VST3 row and choose scan.
Quit the DAW and reopen it.
Open the MP Host and load Omnisphere VST3.
You should be able to use it normally onwards.

Please note, on the Mac, the Omnisphere AU reports 2 parameters at the same time when linking. 

This means that when you try to link a parameter, ie the Cutoff it will report the Cutoff and the Part Level parameter. 

To overcome this problem, use the LINK MULTIPLE method and when the Part Level parameter is added to the list, just double click to remove it from the list.

Alternatively use the LINK GROUPS method and select the parameters you want to link. (Given that you have enabled the Host Automation on the Omnisphere parameter)

26. Controlling Steinberg plugins such as Halion, Padshop and Retrologue

You may find that when linking some encoders on parameters of Steinberg plugins may seem stuck or behave erratically. To overcome this issue click on Encoder options (right click menu > Encoder Options, on the MP Host) and choose Absolute mode instead of Relative mode which is the default.

In addition, via the right click menu enable Windows Unified

If some parameters have MIDI CC assigned to them, right click and Forget CC. This may conflict with the VST method that the MP Controller uses to control parameters.

27. Windows - Transferring the keyboard focus on the DAW

In the April 2025 update, v1.7-f4941c72--H2025-04-22--B2025-04-22, we have introduced an automated way to pass the keyboard focus to the DAW.

Clicking on the MP Host and/or the hosted plugin in the MP Host will cause the keyboard focus to be transferred there and not on the DAW.

On Windows, with this update, the MPH passes automatically the space key to the DAW. 
When you have the MP Host big window selected and working with the plugin, if you press the space key it will send it to the DAW, while before it was not possible and you had to click to the DAW. The only requirement for this to work is that the MPH window needs to have the keyboard focus, not the hosted plugin.

Pressing the space key will not only pass the key to the DAW, but it will also transfer the keyboard focus onto the DAW.

When you have the MP Host big window selected and working with the plugin, if you press the space key it will send it to the DAW, while before it was not possible and you had to click to the DAW.

The only requirement for this to work is that the MPH window needs to have the keyboard focus, not the hosted plugin.


Using UPDD:

In UPDD enable this setting: "Reset keyboard focus after a gesture action ends"

Note that "Reset mouse cursor after a gesture action ends" will take the mouse cursor back to it's previous position before the gesture was made.

Using Auto Hot Key:

We have created a small app for a few popular DAWs to transfer the keyboard focus back to the DAW by pressing Win key & z together.


You only need to run the app once. You can add it to your Startup folder so that it starts automatically with Windows

You can download the app for each DAW from here

Zip file password is 123456


More information:

The apps to transfer the keyboard focus were created with Auto Hot Key. A great free scripting platform for creating automation on Windows.

We have included the ahk script in the web folder, in case you want to extend it for more automation.

28. Mac OS - Transferring the keyboard focus on the DAW

In the April 2025 update, v1.7-f4941c72--H2025-04-22--B2025-04-22, we have introduced an automated way to pass the keyboard focus to the DAW.

More specifically, on the Mac the keyboard focus is passed to the DAW when a key is pressed is transferred to the small window of the MP Host which means all the keys will be passed to the DAW.


The information below applies to older versions of the MP Host.

If you want to pass the keyboard focus back to the DAW (press space to start and stop the playback in the DAW) you can switch easy to the DAW main window using UPDD  or a Mac automation tool like Keyboard Maestro or Better Touch Tool.

For Logic Pro X use the Better Touch Tool (see below).

Using UPDD

In UPDD Commander enable this setting: "Reset keyboard focus after a gesture action ends"

Note that "Reset mouse cursor after a gesture action ends" will take the mouse cursor back to it's previous position before the gesture was made.


Using Better Touch Tool (BTT)

We have created a preset for Logic Pro and you can download it from here

Depending on your DAW, you may need to choose to create this workflow as a global option. To set this workflow as a global option, follow this article.

Choose Import Preset from the top bar menu


Here is how to create the same workflow in BTT:

Run Logic Pro

Choose "Select app from running apps" and then choose Logic Pro.

Then choose Keyboard Shortcuts and record the key "Space"

In the Trigger Conditions on the right pane choose "Prevent recursive triggers" 


Then in Actions create the following actions:

    1. Activate Specific Window and set the App Name to: Logic Pro

    2. Set the action to "Send Keyboard Shortcut" and record the key "Space".


Using Keyboard Maestro

Keyboard Maestro is a great app used by many music professionals on the Mac to automate tasks.

Here is an example of how to do this in Keyboard Maestro:

Open your DAW

Open the Keyboard Maestro app.

Create a new Macro in Keyboard Maestro.

Chose the trigger key. In our example below we have chosen 

Then in Actions choose from the list of actions "Bring a Window to the Front"


Choose the DAW from the list "in"

Choose "Windows with title containing"

Type in the title of your main DAW Window. Here we use logicx which is a text that always appears on Logic's main window.

Your Macro should look like this:

You can also download this example Macro from here


Try it by pressing the Run button on top or by trying the key combination assigned.

The Macro will bring the DAW to the front if you are in MP Host or any other app on the Mac.

29. Mac OS - Running one DAW in Rosetta and another DAW in ARM mode

In case you run one DAW under Rosetta and another in ARM, this will result in the DAW that runs second to not been able to open the Control and Display window. 

You need to reboot the Mac and run the DAW you want to use first.

 

30. Switching a track in Ableton Live does not open the last MP Host

When you have the option to auto-hide plugins in Ableton Live, 

switching a track hides the small window of the MP Host while the controller window remains open and you can still control the plugin. This is often a benefit because you can still control a plugin located on another track (while without the MP Controller you cannot do that, unless you change the A.L. option.)

When you change a track and you choose to control another plugin via the MP Host, it will close the previous MPH Controller window from the previous track. 

Navigating back to the previous track requires that you press on the Control & Display button (the controller icon on the small window) because Ableton does not notify plugins when a track has switched.

If you don't want to use the mouse, a good practice is to drag beforehand the small window of the MP Host on the controller's touch screen. 

Once you change a track, touch the Control and Display (Controller Icon on the single host). 

Then touch the touchscreen or click anywhere on the controller window, the small window will be hidden below the big window.

Thereafter, when you switch a track again in Ableton the small window will show on top.

The same applies to the MP Multi Host.

See tutorial video here

After changing a track, Touch the Control and Display (Controller Icon on the single host) 

The MP Host will automatically open the controller window when the MP Host plugin opens from the DAW. This means that the MPH plugin is completely closed in Ableton Live and you click on the A.L. icon to open it

In other words, opening the small window will automatically open the controller window as well.

Alternatively, If you have another midi controller to open/close plugins in Ableton, like Push or other midi controller, you can program it to close the MP Host and then open it, and it will automatically open the controller window.

31. Loading the MP Host with one click as an Ableton preset in Ableton Live

Additional to the MPH presets and Favorites, you can save the MP Host, while having hosted the third party plugin you want to use, as an Ableton preset and load it with a single click.

See the video here

The same principle applies in other DAWs if the DAW allows to save presets.

32. Mac - Right click with Magic Mouse does not show pop up menu in the Favorites Window

There were reported cases where some versions of the Magic mouse would not show the right click menu in the Favorites window.

You can use a mouse with a dedicated right click button, like a PC mouse, Apple Trackpad.

On the Mac, with magic mouse, you have to press the CTRL key simultaneously to generate the right mouse click however this does not work in the Favorites right click menu.

33. Link Groups

See video

If the plugin displays the parameters in groups, selecting a group will link all the parameters within a group.

You can select a color and all the parameters will get that color on the encoders after linking.


If the plugin does not report its parameters in groups you can select them one by one or use ctrl to select individual parameters you want to link or use shift to select multiple parameters



When you select individual parameters and select a color, it will assign the first parameter the color you selected and assign the next color in line to the next parameter and so on.

34. Switching to other Plugins via the Plugin Panel

The Plugin Panel is part of the Beta update v1.7-dbe3ca3c--H2024-06-14--B2024-06-14 or later version.

With this feature we can now switch to any plugin loaded in an MPH Multihost instance. 

While previously it was only possible switching, via the touch screen, to other plugin slots of the current Multihost, with the plugin panel you can switch to any plugin slot of any Multihost.

The Plugin Panel button appears at the left bottom area of the Multihost controller window and there are 3 additional buttons

 

How it works

The Plugin Panel works only with MPH Multihost plugins, Instruments and Effects. 

MPH Single plugins will not appear in the Plugin Panel.

Each Multihost plugin has its own Plugin Panel window.


Here is a brief tutorial video on the Plugin Panel.

For a plugin to appear in the Plugin Panel, the track name must be provided by typing it in the text area of the Multihost and hit enter.

Logic and Cubase DAWs provide the track names automatically therefore the track name will appear in the text area upon loading the Multihost.

If two or more Multihosts are used on a track, these must carry the same track name, so that they appear under the same track in the Plugin Panel.

Note that on the main window of the MP Host the track name is now displayed under the plugin/preset name

Plugin panel sections

The Plugin Panel window is split in 2 parts. The left part displays the tracks (as buttons) 

and the right part displays the plugins of the selected track in columns. 

Each column represents a Multihost plugin.

Multihost Instruments will appear always first and the Multihosts Effects will be placed after Instruments.

Each column shows the plugin slots (as buttons) of its respective Multihost.

The order of the Multihost columns cannot be changed and the Multihosts will appear in the order that are opened by the DAW, typically in most DAWs this is the order that are placed and appear in the DAW.

If you add/remove Multihosts and the order does not match the one you see in the DAW, you can save and reopen the DAW project for the Multihosts to be reordered.


Selecting tracks and plugins

The active track has a yellow color. This is the track that has the plugin currently open (being viewed).

If you select another track button, this will become grey and it will list the plugins loaded in the Multihosts of that track. If you select a plugin from the right section, then this will become the selected track and the button will turn yellow.

 

Adding a new track

When adding a new track and a new Multihosts instance, after the track name is entered (Logic and Cubase provide the track names automatically to the Multihost) the track button will appear last in the track area. 

 

Moving a track button

If you need to place the track button anywhere in between the existing tracks, click and hold the track button for one second and it will turn orange. Then, click on another track button and the track will be moved to the place of that track button.


Removing tracks

If you remove/delete a track on the DAW that carries one or more Multihost plugins, these will automatically be removed from the tracks listed in the Plugin Panel.


Duplicating Tracks

When duplicating DAW tracks that carry Multihost instances, then these Multihosts will have the name of the original track copied. You need to change the name of the track to the new track name.

If the track name remains the same, then these Multihosts will appear as columns in the original track.


Opening a Multihost Preset

When you open a Multihost preset, the track name displayed on the Multihost bottom text area will be replaced (if you have already typed a name). Therefore, the track name needs to be entered after loading a Multihost preset.


Opening projects in Logic Pro X

The Plugin Panel clears the shared list of loaded plugins every time a DAW project closes. 

Logic, uses a separate AU Hosting Service to host plugins which keeps open after a project has closed. Therefore, we recommend, when working with a Logic project that carries MP Multihost instances, to close Logic before loading another project that carries MP Multihost instances. 

Alternatively, instead of closing Logic you can load an empty Logic project that carries no plugins.

You can also force quit the AUHostingservice from the activity monitor, prior to loading another Logic project that carries the MP Multihost.


Logic Pro X reports the MP Multihost as not compatible


If Logic does not load the MP Multihost open the Logic Plugin Manager and choose to re-scan the selected plugin by pressing on "Reset and Rescan Selection". 

If it gives a warning that it does not pass validation scan it again with "Reset and Rescan Selection"  and it will pass the validation.


Troubleshooting

The version of the Multi host that features the Plugin Panel uses an app allowing instances of the Multihost to communicate with each other. If you are having any issues such as a crash when you load the Multihost, ensure that the MPHCSM is installed in the MP Host folder:

Windows: %AppData% and under folders MP\Host\MPH Cache

Mac: Applications/MPH Cache.app

If the MPH Cache does not exist after you run the installer please send us an email to help you troubleshoot further.

Additionally, when you run the DAW ensure that the MPHCSM shows up as a running process while the MP Multihost plugin is loaded the DAW:


The MPHCSM process will exit automatically when the DAW closes.

Please note  that there were reports from users that when using the N.I. Maschine plugin in a DAW project, the plugin panel does not report the tracks.

 

36. Run UAD Luna on Windows

On Windows, MIDI drivers are exclusive per application. UAD Luna consumes all available MIDI devices on start, prohibiting any other applications to use MIDI devices.

To overcome this problem we created a small utility to start Luna.

Download the application from here. The zip file is password protected and the password is 123456

Extract the zip on a folder on your computer.

Run as administrator the START.bat file.

It will open Luna and a cmd window which will later close automatically.

Load the MPH Single in Luna and click on the controller icon to open the controller window.

Initially, it will display the "Controller Not Connected" message. The message will disappear in about 10 seconds and the MP Controller will be available to use normally in all MP Host instances including Multi hosts.

The CMD window will close automatically after the controller window has opened.

37. Transferring the mouse pointer to the DAW display

Mouse Back Option

If you right click on the controller window, in the menu, there is the option "Move mouse to Window".

When checked, left clicking on the MPH small window to open the plugin on the controller (both for Multi and Single Hosts) 

will automatically transfer the mouse pointer on the controller window. This option was made for convenience so that you don't need to drag the mouse from/to the controller. 

When disabled, right clicking on a MPH to open the plugin on the controller will automatically move the mouse pointer to the controller window.

There is also a button on the controller window which when clicked will transfer the mouse pointer back to your main screen.

38. Opening and closing the MP Host via MIDI CC

In update MPH Beta v1.7-c7f4c2bb--H2024-07-10--B2024-07-10 we enabled the opening and closing of the MP Multi (opening slots) and Single hosts via MIDI CC messages or notes.

Since with this feature it is possible to automate the parameter during automation recording, which is something you may not want to do, we added an option in the host.properties file to enable this option as it is by default disabled.

To enable the parameter as an automatable parameter, open the host.properties file in a text editor and change the last line from:

<VALUE name="enable_openclose_parameter" val="0"/>
to
<VALUE name="enable_openclose_parameter" val="1"/>

To open the MP/Host folder see here

If you use MIDI CC to open and close the MP Host window on the controller, it is of course a good practice to set on your midi controller the button or pad used as a toggle. 

This means, press once (send value 127) it will open the window, press another time (send value 0) it will close it.

If you press the button fast (within a period less than 1 second) the MP Host will ignore the second value received, it will follow the first press and then it will send a message (the value)
to the DAW/Host of the current state.


Here is an example in Ableton. 


When one slot opens the rest receive a message to close. Only one effect/instrument can be open at a time on the controller.


The same applies on the single host


You can assign parameters to listen on a MIDI CC message


In the same manner you can use CC to control the Bypass on the Single and Multi Hosts.

Using MP MIDI app to trigger open/close or bypass.

You can use the MP MIDI app to send MIDI CC messages to open and close plugins. Alternatively, you can use the plugin panel on the MIDI app to switch plugins from the touch screen.

If you have two MP controllers, you can have the Plugin Panel constantly open on the MP MIDI app

and use the second MP controller to switch from plugin to plugin on the first MP controller.

See article Using 2 MP Controllers

 

39. Using the Multi host plugin in Bitwig

Bitwig uses a sandbox process to host plugins. If you remove the last MP Multi host plugin and try to load another one, Bitwig will not be able to load it.

One option to address this problem is to always keep one Multi host plugin loaded.

 The other option is, if you have removed the last one Multi host plugin, just double click on the MPHCSM.exe (Windows in the ~/MP/Host folder) or MPH Cache.app (Mac in Applications) to clear the cache and load the Multi host plugin.

Important: In Bitwig setting > plugins > Plugin hosting mode
set it to: Bitwig or Together or Vendor


40. Sending MIDI notes from the MP Host

In the July 2024 update (Beta MPH v1.7-91f44c9b--H2024-07-20--B2024-07-20) we introduced the ability to send MIDI notes out to the DAW when using a plugin that has this functionality 

(like Sequencer, Arpeggiator Instrument plugins like Audiomodern Riffer).

This update applies on both the Instrument MP Single host and Instrument Multi host.

41. Plugins appearing magnified and missing parts of their UI

If you load plugins in the MP Host and part of the plugin UI is missing because it looks bigger in size or just part of it is not showing, for example:


Or the plugin appears smaller with white surrounding area, for example Serum AU.


It means that the current plugin type (for example Audio Unit) is set to resize automatically and this may cause incompatibilities with the MP Host.

The solution is to use another format of the plugin, like VST2 or VST3.


Additionally, if the plugin has the option to set the default zoom level, set it to your liking and the plugin will appear at that zoom level when you load it in the MP Host even when you open an MPH preset.


In this example, Serum VST3 on the Mac it loads at 150% and shows correctly


Note that if a plugin does not have a "Set Default Zoom Level" and just saves as default the last resized value, then when loading an MPH preset, the size of the plugin may not look correct, if you have resized the plugin in the DAW, after you have saved the MPH preset.


This is because after you have resized the plugin outside the MP Host, when loading the MPH preset, the default size would have changed, thus the MP Host may not display it correctly.

To solve issue, resize it and save the MPH preset.

If the resize menu of the plugin is not visible, then load the plugin from the plugin list in the MP Host and resize it. Then load your MPH preset.

For example:

Load the plugin from the PLUGIN LIST (not preset)

Resize it


and load your MPH preset.

Alternatively, use UPDD smart magnifier to magnify plugins on demand.