Tracks Live for Multitrack Recording

Before you start

Tracks Live is a local multitrack recording application. The recording happens on the computer where the software is installed and where the audio interface is connected, not through a web service or an online platform. Treat network access, cloud storage, and file sharing as optional parts of your own workflow rather than core recording features.

Before opening the software, connect the audio interface or mixing console you plan to record from and confirm that the computer recognizes it. Close other applications that may also try to use the same audio device. Check the available storage location and make sure there is enough free space for the planned session, because a multitrack live recording can create several large files at once.

Think about whether you need every input to be recorded to its own track or whether a stereo mix is sufficient. Multitrack recording requires assigning each source to a separate input channel. If the audio device or driver does not expose individual channels, the software will only be able to capture the signals that the system presents to it.

Step-by-step instructions

Start by opening Tracks Live and creating a session. Choose a project name and a destination folder that is easy to locate later. Some versions offer a template or default track setup; if you are not sure which option to pick, start with the simplest available session and add tracks manually.

Open the audio preferences or device settings and select the connected audio interface. The name shown depends on the driver and manufacturer. If the device does not appear, check the physical connection and whether the driver or control application for that interface is running.

Set the sample rate and buffer size before recording. Lower buffer settings reduce monitoring delay but can cause clicks or dropouts on a computer that is under load. For a live recording, reliability is often more important than minimal latency, so start with a moderate buffer and reduce it only if you can monitor comfortably and the recording remains stable.

Create one track for each source you want to record separately. For example, a vocal microphone, a guitar input, and a stereo keyboard feed should not share the same mono track if you need independent control after the show. Open the input routing for each track and assign it to the matching hardware input or channel.

Arm the tracks that should be recorded. Arming tells the software that a track is ready to capture audio; unarmed tracks remain silent in the recorded project even if you can hear them through monitoring. Check each track meter while the source is playing to confirm that signal is reaching the intended channel.

Adjust input gain at the audio interface or console so that normal program level keeps the track meter healthy but not constantly peaking. The exact optimum depends on the source, but the goal is a strong signal with enough headroom for louder moments. Avoid correcting an already distorted input with a lower software fader, because the distortion is recorded before that fader.

Press the main recording transport button when you are ready. Confirm that the elapsed time is advancing and that the armed tracks show movement. Record a short test before the main performance, stop, and play it back through the same monitoring path so you can catch routing mistakes while they are still easy to fix.

Check the output

Stop the recording and locate the session folder when the test is complete. You should see audio files created for the armed tracks, not just a project file. If only a stereo mix appears when you expected individual files, the routing was likely set to a combined output rather than separate inputs.

Play each recorded track back in the software and confirm that the expected source is present on the correct track and in the correct left or right position for stereo inputs. Listen for obvious distortion, repeated dropouts, or a constant tone that may indicate a clock or driver problem.

The number of files, file format, and naming depend on the session settings and software version. Do not assume that all projects use the same format. Check the settings that control file type, bit depth, and sample rate if a specific delivery format is required later.

Common problems and next steps

If a connected interface is missing from the device list, close Tracks Live, verify that the interface is powered and connected, then reopen the software. On some systems, another application or browser can hold exclusive access to the audio device and prevent Tracks Live from using it.

If the recording stops unexpectedly or the transport freezes, do not immediately restart the computer. Note the approximate stop time and check the destination drive. A full drive, a slow external disk, or a USB connection that is being shared with other high-bandwidth devices can interrupt a multitrack recording.

For clicks, pops, or small gaps, increase the audio buffer size and test again. If the problem continues, disable system sounds and notifications during recording and close unused programs. A higher sample rate or many simultaneous tracks can also increase the load on the storage system.

After a successful recording, copy the session folder to another drive before making edits. Keep the original session intact so you can return to it if a later edit or conversion does not behave as expected. If you need to share files, use a transfer method that your team has already approved and verify that privacy and file access settings match that workflow.