The Transport Panel offers you the basic controls to start and stop the MuLab sequencer.
It also offers controls to set the tempo, the cycle, toggle the metronome etc...
For detailed info on recording, see Recording.
- The Play button starts/stops playback of the composition.
Right-click the play button for extra options like a panic function etc.
Tip: You can also assign a key shortcut to the panic function.
- The Rewind and Forward buttons move the play position backward/forward in the composition.
When simply clicking the rewind/forward button it does a normal rewind/forward, when also holding [Shift] it does a fast rewind/fast forward.
The normal rewind/forward steps per composition grid. If no active grid or inside a part editor it steps per beat.
The fast rewind/forward only steps to the marker positions and the start of the first selected part (if any).
Note that you can flip this behavior via the "Standard Rewind-Forward = Fast" preference.
Both the standard rewind/forward and fast rewind/forward can be put under a shortcut.
By default it are the [Arrow Left] and [Arrow Right] keys.
Note that on top of that you can also use shortcuts to any of the "Goto..." functions, eg Goto Composition Start.
- The Record button toggle the record state.
Right-click this button for extra recording options like the metronome countdown etc.
- You can directly edit the Tempo with the mouse wheel. Double-click on it to set a specific tempo.
- Right-click the Tempo display for its context menu where you will find all kinds of tempo related options like:
- Insert a tempo automation event
- Show the Tempo Slider with which you can also record tempo automations
- Edit Tempo Changes
- Set the composition's time signature
- Set the MIDI Clock output module
- The Swing knob controls the amount of swing for the focused composition.
Note that also each sequence part has its own swing parameter, they emphasize eachother.
So a composition can easily use different swing amounts for the different parts, resulting in multi-swing
- The CPU meter measures the 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 types of values, they cannot be compared. Cfr the explanation here above.
The CPU meter can be set to different display modes. Click on it to toggle between the various modes:
- The default graphical bar
- Avg = Average CPU load
- Max = Max CPU load
- O = Overload count. An overload is when the audio processing takes too much time. Often this results in a (little) click or a similar artifact.
- The Metronome control has 3 states: OFF, ON Play+Record, ON Record Only
- The first metronome beat is played at full velocity, the next beats are each played a bit softer each time. (100,95,90,...)
You could use this difference to make a custom metronome patch that, for example, uses different samples/volumes/pitches for each beat. (using multi-sampler velocity zones)
- Right-click the metronome to edit its sound.