SSL Audio Interface article
Common Ssl Audio Interface Mistakes to Avoid
From skipping the Windows ASIO driver to misunderstanding the blend knob, the most common SSL audio interface mistakes are straightforward to prevent once identified.
Even straightforward home recording gear causes problems when set up or used incorrectly. Benjamin Wood covers the most common mistakes made with an SSL audio interface and how to avoid them before they cost time or damage recordings.
Not Installing the Windows ASIO Driver
On macOS, no driver is needed — the interface is plug-and-play via Core Audio. On Windows, the default audio driver (WDM) will technically work but produces unacceptable latency for live recording and monitoring. The ASIO driver from SSL's website is required for low-latency operation on Windows. Attempting to record through a DAW without ASIO on Windows results in a delay between speaking or playing and hearing the result in headphones — often several hundred milliseconds, which is too long to perform against. Download and install the ASIO driver before any first recording session on a Windows machine.
Forgetting Phantom Power for Condenser Microphones
Condenser microphones require 48V phantom power to operate. If phantom power is not engaged, a condenser microphone produces no signal — or a very faint signal — and the recording sounds quiet or absent. The 48V button on the front panel of the SSL 2 must be pressed before recording with a condenser microphone. The button illuminates when active. Note that phantom power should not be left engaged when connecting ribbon microphones, which can be damaged by 48V phantom current — check the microphone manufacturer's specifications before applying phantom power.
Setting Gain Too High or Too Low
Incorrect gain setting is the most common cause of poor recording quality. Too high: the signal clips digitally (harsh distortion that cannot be repaired in post). Too low: the recording is quiet and requires significant amplification in the DAW, which raises the noise floor and reveals hiss and hum. The correct approach is to set the gain so the loudest moments of the performance peak around -12dBFS to -6dBFS on the DAW input meter. This provides clean level with headroom for unexpected louder moments. Watch the SSL 2 input meters during a test performance and adjust the gain knob accordingly before pressing record.
Misunderstanding the Blend Knob
New users often find themselves unable to hear playback while recording, or confused by what they hear in headphones. The blend knob on the SSL audio interface controls the ratio of direct input monitoring to DAW software playback. Turning it fully toward "Input" means you hear yourself but not the backing track — fine for isolated practice but useless for tracking over a pre-recorded arrangement. Turning fully toward "Playback" means you hear only the DAW output, which introduces the software monitoring latency. The practical setting for most recording is midway — direct signal and DAW playback mixed together.
Using the Wrong Cable Type
Microphones require balanced XLR cables — three-pin connectors at each end. Guitars and basses connect via unbalanced 1/4" jack cables into the Hi-Z instrument input. Connecting a guitar into the XLR microphone input via an adaptor without a DI box will produce a weak, tonally incorrect signal. Connecting a dynamic microphone via a 1/4" adaptor into the Hi-Z instrument input will also not work correctly. Use the right cable and the right input for each source. When in doubt: microphone = XLR to XLR; guitar or bass = 1/4" jack to 1/4" jack into the front-panel Hi-Z input.
Enabling Software Monitoring Instead of Direct Monitoring
Many beginners enable software monitoring in their DAW — routing the input signal through the DAW and plug-ins before sending it to the headphone output — without understanding that this introduces latency. On any computer with a real-world processing load, software monitoring at typical buffer sizes (256 or 512 samples) produces a noticeable delay that makes vocal or instrumental performance uncomfortable. The solution is to use the SSL audio interface's direct monitoring (the blend knob) for zero-latency monitoring, and reserve software monitoring only for specific situations where hearing plug-in effects in real time is essential and the buffer size has been reduced to compensate.
Bottom Line
Most problems with an SSL audio interface are setup issues rather than hardware faults — ASIO drivers, phantom power, gain staging, and understanding the blend knob resolve the majority of first-use difficulties. For the full technical picture of the SSL range, the complete guide covers every model in detail.
Comments