Factory And User Library

When you install MuLab on your computer, it comes with a library full of sounds and effects.
This is called the Factory Library.

When playing with the factory presets and editing them, you will come up with nice new sounds and effects that you want to save.
When you edit such factory preset and save it using the "Save Preset" button at the top of the editor, the presets will be automatically saved in your User Library, and the original factory preset is preserved.
Using "Save Preset As" you can choose any location on your system.

By default your user library folder is located at the MuLab/User/Library subfolder in the installation folder.
But you can set a specific folder on your system to be your MuLab User Library folder.
This is done by editing the "User Library Folder" preference.
Similarly you can also overwrite the default factory library location by editing the "Factory Library Folder" preference.

Sample File Management

There are two ways to include samples in a MUX preset: Link them or Embed them.

When embedding samples in a MUX preset file, the MUX preset file size will be much bigger as it includes the embedded sample(s).
Embedding can be done via the sample's context menu -> Embed, or via the Project Browser -> Samples -> Options -> Embed All.

When using sample links and you want your project / MUX preset to be used on another system (eg sharing with other users), then it's highly recommended to copy/move the used sample files into an "Audio" subfolder in the preset file's folder. Then upon saving the preset MUX will use a file reference relative to the preset file. So then it's easy to move MUX preset file + subfolder together (eg. share a preset via a zip file) as thanks to the relative file reference, the reference will stay valid.
 
Note however that oscillator waveforms are always embedded within the project/MUX preset file, even when you loaded the waveform from an audio file.
Multi-form oscillator 'sample grains' are sample objects though so there the above linking info applies too.

Specific Presets

There are some specifically named presets:

• Sample Player.Mux
• Sample Player Rack.Mux
• Sliced MultiSample Player.Mux
• Sliced MultiSample Player Rack.Mux

 
When adding a "Pitched Sample" or "Render To New Sample":
If there is a "Sample Player Rack.Mux" in your Mux/Racks or Mux/Racks/New Rack Templates subfolder that MUX preset will be used.
Else if there is a "Sample Player.Mux" in your Mux/Instruments/Templates subfolder that MUX preset will be used in a new default rack.
Such MUX preset should contain a "Sample Player" module.
 
When doing "Add Sliced Multi-Sample":
If there is a "Sliced MultiSample Player Rack.Mux" in your Mux/Racks or Mux/Racks/New Rack Templates subfolder that MUX preset will be used.
Else if there is a "Sliced MultiSample Player.Mux" in your Mux/Instruments/Templates subfolder that MUX preset will be used in a new default rack.
Such MUX preset should contain a Multi-Sample Player module.
 
If no such MUX preset in the user library, the default version will be used.

Preset File Names

In some cases you may (accidentally) choose a different name for the internal object name and the corresponding preset file name.
In that case MuLab will popup an alert to make you aware about it, and give an option to resolve it:
 

 
Here is an example how this happens:
 
Start with a new project with the default Basic Synth.
Tweak that Basic Synth sound a bit until you like it.
Popup Basic Synth's options menu -> Rename -> rename it to "My Basic Synth".
Now also click Save Preset As... and use the new file name "Basic Synth 1".
So now there is a different name for the MUX object in RAM and the MUX preset file name on disk which may be a rather confusing situation.
 
That's what that popup alerts about, and it gives the option to resolve it by clicking "Rename This MUX Modular" which will automatically update the MUX patch in RAM to have the same name as the MUX preset file on disk.
If you do "Keep As Is" however then the different names will be preserved and the result is this:
 

 
So it's recommended to choose "Rename This MUX Modular", where "MUX Modular" can be another object type you are saving, eg a sequence, an envelope, etc...