M7 Docs   Settings & Preferences

Global Preferences

Almost all preferences can be edited via the main menu -> "Edit Preferences".
The "Edit Preferences" dialog panel lists all preferences and shows a description of the preferences.
You can double-click a preferences to edit it, or click the "Edit" button.

 

Edit Colors

You can also tweak many of the used colors in the UI. This can be done via the main menu -> Edit Colors. Several color preferences can also be set to "Auto Color" which means that a automatic default color will be used, which may be the color of another color preference. For example if "Top Panel Display Color" is set to Auto Color, then the "Top Color" will be used. This allows for quicker color preferencing as several colors can be set by a single color preference, if you want.

 

Editing Setup Files

Besides all the preferences that can be edited via the UI, there are also some settings that are more technical and normally don't need to be changed, and so normally you don't need to read the following info. These advanced settings are only editable via the settings files. In the folder where the MuTools application is stored there is a sub-folder User/Settings. This folder contains files that define how this app must work. Below is detailed info about these files.

Directly editing these setup files is meant for experienced users only!
If you are not sure about what you're going to do, then don't edit these files and only edit preferences via the UI.

How to:

  • If you want to change something in these files, then first quit the app, then make the change and then launch the app again. So don't make changes while the app is active.
  • Settings in .txt files are always written on a single line in the format "SettingName=SettingValue". Settings and preferences in .xml files follow the standard XML syntax.

 

AudioSetup.txt

AudioSetup.Txt file contains all settings regarding your audio device. It is only used by stand-alone apps like MuLab, not by plug-in apps like MUX Modular Plug-In. Everything can be edited via the user interface and it's not recommended to edit this file manually.

 

MidiSetup.txt

MidiSetup.Txt file contains all settings regarding your audio device. It is only used by stand-alone apps like MuLab, not by plug-in apps like MUX Modular Plug-In. Almost everything can be edited via the user interface, there only is one extra preference:

MidiOutputMicroTimeCompensation

It defines the time offset in microsecs to finetune the timing of MIDI output. This can be handy in case there would be a sync problem anywhere in the MIDI chain.

 

MainSetup.txt

  • Logging : 0=No, 1=Yes.
  • PreferredProjectWindowRectangle : X,Y,W,H. Defines the default project window size when opening a new project window. If this is not defined new project windows are opened full screen.

 

PreferredFilesAndFolders.txt

This file is automatically maintained by the app and contains info regarding your preferred files and folders.

 

VstPlugins.xml

This XML file contains all info regarding your VST plug-Ins. Almost everything can be edited via the user interface -> VST Plug-In Manager. Directly editing this file is not recommended except for the special cases explained below. Anyway, whenever you would edit (or delete) this file, make sure it is not in use i.e. MuLab or MUX Modular are not active.

If you delete this file, then the VST Plug-In Manager database is emptied.

To ignore a plug-in: set <Valid> to 0.

To delete a plug-in: delete the relevant <plug>...</plug> block.

If you want a VST plug-in to always receive zeroed output buffers, then set this line in that plug-in's xml block:

<MustZeroOutputsBeforeProcessReplacing>1</MustZeroOutputsBeforeProcessReplacing>
Normally this is not necessary, but some plug-ins do not 100% follow the VST guidelines and need zeroed output buffers.

About ReGrouping a VST plug-in's IO pins

Normally, when a VST plug-in has multiple inputs/outputs, it will properly tell the app how these ins/outs are organized, i.e. whether these are mono or stereo.

Unfortunately there are VST plug-ins that don't properly report this. Technically: They don't support the effGetInputProperties/effGetOutputProperties calls.

In such case the app will default to group the ins/outs as stereo.

If this default behaviour does not match for a certain VST plug-in, then you can overwrite how its ins/outs should be grouped by adding these lines to the relevant plug-in block:

ReGroupAudioInputs=i1,i2,i3,...
ReGroupAudioOutputs=o1,o2,o3,...
where i1,i2,i3... and o1,o2,o3,... are numbers that indicate the number of VST pins per MuTools audio jack. Note that the sum must match the total number of ins/outs for that VST plug-in.

For example, if a VST plug has 4 input pins, but they should be grouped as 2 stereo jacks, then add this line to that plug-in item in User/Settings/VstPlugins.Xml:

ReGroupAudioInputs=2,2
Similar story for outputs.

Of course all this is only necessary for VST plug-ins that don't tell the host how its IO pins are to be grouped. Normally a good VST plug-in will report that to the host, and so you don't have to take this extra action.

 

MidiControllerNames.Txt

This is an optional text file where you can list the preferred MIDI controller names. The format is: 25=My Controller Name 25

Note that the first controller is controller 0. Controller 1 is the second one.

It's recommended to create / edit this file when MuLab / your MUX Modular Plug-In host is not active. After restart the changes will take effect.

Table Of Contents