A MuLab project is a collection of musical objects that make up your musical project.
It can contain plugin modules like synths, effects, step sequencers, composers, and it can contain sequences, samples, etc...
When you save your project into a .MuProject file, all these objects as well as the relations between them are saved in that file.
Each MuLab Project has a Project Modular Area which is the modular root MUX of your MuLab project and shows the connections between the various modules in your project.
The Project Modular Area can contain as many modules (Composers, Racks, MUXes, VST plugins, etc...) as you want and each MUX also is completely modular.
So you can go as deep as you want.
In MuLab App, the Project Modular Area audio inputs receive audio from the audio device, its audio outputs send audio to the audio device and its event outputs send MIDI to the enabled MIDI output ports.
On project level MIDI input is routed as defined in the MIDI Input Channel Targets map.
In MuLab Plugin, each instance of the plugin is a separate project, with each instance project having its own Project Modular Area.
That plugin's Project Modular Area has a fixed number of audio inputs and outputs which connect MuLab Plugin to the host DAW.
All modules, sequences, racks, synth and effect modules, samples etc... are part of the project.
You can work on multiple projects in parallel, and copy-paste and drag-drop modules between them.
The Project Editor is the main editor window of a MuLab project.
- At the top-left it shows the main MuLab and Project menu buttons.
- Further to the right is the project name display.
As the project window has no separate title bar, so to create more musical workspace, you can move the project window by dragging the project name display.
- Further to the right are the project modular area and Project Browser buttons.
- Further to the right is the Focused Module Keyboard.
- Further to the right is the project CPU meter.
The CPU meter measures the project's audio processing.
It's the proportion of time needed to process an audio block per available time per audio block.
The available time per audio block is the audio engine blocksize divided by the samplerate.
For example using a 512 blocksize with a 44100 Hz samplerate gives 11.6 ms per block.
If the measured amount of processing would be (average) 3 ms per block that gives a audio CPU usage of 25.8%.
Note that the CPU meter does not really measure the CPU used by the GUI nor the CPU used by disk streaming, only the audio processing.
The audio CPU usage measuring is indicative. An alternative method to measure CPU usage on your system is your system's task manager.
Note however that the system's task manager values and MuLab's CPU usage value are different measurements, they cannot be compared, cfr the explanation here above.
Right-click the CPU meter for more detailed info.
- The biggest area of the project editor is for the Main Module editor.
The Project Main Module defines the kind of project: A composer, a synth, an effect, ... (hybrid options possible, but lets keep it simple for now)
It is the Project Main Module that will be embedded into the project editor window.
How to define a project's Main Module: In the project modular area right-click a module -> Set As Main Module.
In many case the Project Main Module already is predefined, for example when opening the demo projects, or when doing "New" project, so often you even don't have to bother about it.
- When the Project Main Module is a composer then that composer's Transport Panel is also embedded at the top of the project editor:
- When the Project Main Module is a MUX module then that MUX editor is embedded into the project editor:
- When the Project Main Module editor already is opened in a floating window then you might see this:
That's because MuLab will avoid that there are 2 editors for the same module.
So if you first have the main module embedded in the project editor and then it is also opened in a floating window then it is removed from the project editor and the project editor shows this default state from where you still have control.
- It is not recommended to set a VST plugin as the Project Main Module because the VST plugin editor cannot be embedded in the project editor.
If you need a VST plugin as main module then put it into a MUX and set that MUX as main module.
- You can work on multiple projects at the same time.
When you open a project you'll get a question "Replace this project - Open Extra Project".
Choosing "Open Extra Project" will keep the current project open and open a new extra project window.
When you have multiple projects open in parallel, you can copy-paste and drag-drop clips and modules from one project to another.
Note that having multiple projects open at the same time will use more CPU of course.
You can 'mute' a project via the green power on/off button in the project modular area.