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 Forward and Rewind buttons set the Play Position at the previous/next cue point. This can also be done via the Arrow Left and Right keys.
The cue points are:
Composition Start = 1.1.0000
Composition Loop Start
Composition Loop End
The last position where you have manually set the position line
The start of the selected Part
The end of the selected Part
The end of the last Part in the Composition
All markers in the Composition
[Shift]+click the rewind button rewinds to start ie. to position 1.0.0.
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 UI 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)