A dependable Performer Lite audio setup starts with the connection between the application and the computer’s audio hardware. Driver selection, sample-rate alignment, clocking and buffer size all influence how recording and playback behave. Understanding these settings helps musicians, recording teams and technical operators configure a system that suits its intended workload.
Start with compatible audio hardware and drivers
Performer Lite uses the MOTU Audio System (MAS) as its hard-disk recording engine. MAS supports audio recording and playback, along with internal buses, aux tracks, master faders, sends and real-time audio effects. To use those capabilities, the application must communicate with an audio device through a supported driver.
Supported options include a computer’s built-in audio hardware and compatible devices using ASIO, Core Audio or Windows Audio (WASAPI) drivers. Install the hardware driver according to its instructions before selecting it in Performer Lite. Then open the audio hardware configuration from the Setup menu and choose the driver associated with the device you intend to use.
Driver choices differ by operating system:
- Windows: Performer Lite uses one active driver at a time. When available, the guide recommends ASIO for audio quality, channel availability and low latency. Windows Audio can be useful when ASIO hardware is unavailable, but it is stereo-only and may perform sample-rate conversion.
- macOS: Core Audio drivers can be selected. Multiple devices can be enabled simultaneously, but additional configuration is needed for reliable operation. When using more than one device, select a master device.
After enabling a driver, confirm that the intended hardware appears as an available input and output in Performer Lite. This is a practical first check before creating tracks or troubleshooting signal flow within a project.
Match sample rates and establish clocking
The sample-rate setting determines the rate used for recording and playback. Choose a rate supported by the selected hardware, and, when working with existing audio files, match the project to their sample rate where possible. The guide identifies 44.1 kHz as the standard rate for audio compact discs. If a file’s rate is uncertain, it can be imported into a project and checked in the Soundbites list.
Clock settings matter when coordinating audio hardware with other digital sources or external synchronization. Most audio devices offer an internal clock option. With this setting, the device runs from its own clock, and Performer Lite uses the hardware as its audio time base. This helps keep the application’s audio and MIDI playback aligned with that hardware clock.
Problems can arise when the audio device and an external digital source are not synchronized. For example, if a device receives digital audio through an input such as S/PDIF, the device and the source need an appropriate clock relationship: one can follow the other, or both can be resolved through a third device. The guide warns that unresolved digital sources can produce clicks, pops, distortion or similar artifacts.
External time-code synchronization requires particular care. If Performer Lite follows external sync while the audio hardware continues on its own internal clock, audio may not be resolved to that time code. In that situation, audio and MIDI can drift relative to one another, and audio may fail to stay aligned with the external reference. The recommended principle is to synchronize the audio hardware to the same source feeding time code to Performer Lite, using a synchronizer where needed to provide resolved digital audio clock.
Choose a buffer size for the task
An audio buffer temporarily holds samples as they move between the computer and audio hardware. Buffer size involves a trade-off between monitoring responsiveness and processing demand. Smaller buffers reduce latency—the delay that may be heard when monitoring a live input through Performer Lite or playing a virtual instrument from a MIDI controller. However, smaller settings increase the computer’s processing load and can limit how many real-time effects it can handle.
Choose the setting according to the work being done:
- Live input monitoring or virtual-instrument performance: Use a lower buffer setting to reduce latency, while leaving enough processing capacity for the plug-ins and instruments in use.
- Playback and mixing without live input monitoring or software-instrument performance: A higher buffer can reduce the real-time processing burden. The guide gives 512 or 1024 samples as typical settings for this scenario.
On macOS, buffer size is set in the Configure Hardware Driver window. On Windows, it may be adjustable in Performer Lite if the driver permits an internal buffer override. Some ASIO drivers require the setting to be changed in the hardware’s own control software, which can be opened using the driver configuration button.
Check the complete signal path
When setup is complete, verify the key settings together rather than treating them as isolated options: the intended driver is enabled, the audio device is available for input and output, the sample rate suits the project, and the clock source matches the system’s synchronization plan. Then select a buffer size appropriate to whether the session prioritizes low-latency monitoring or processing capacity.
If Windows Audio is in use and sample-rate conversion is engaged, the Performer Lite control-panel sample-rate setting turns red. The guide also recommends matching the default Windows audio device’s sample rate to the project rate when possible. These checks can help identify configuration mismatches before they are mistaken for recording or playback faults.
Build a setup around the operating requirement
Performer Lite audio setup is a balancing exercise: compatible drivers establish communication with the hardware, matching sample rates supports consistent file playback, clock alignment helps maintain synchronization, and buffer size determines the trade-off between monitoring latency and processing load. Configure those elements around the actual session—live recording, MIDI performance or playback-focused mixing—and confirm that the entire audio path is operating as intended before work begins.