Your singer hears a tick in every rehearsal, yet the headphones sound fine when playing yesterday’s mix. Before changing drivers or cutting syllables out of a take, establish where the tick enters the path. This project produces a short test recording and a settings note you can reuse before a paid session.
Is the crackle captured?
Save a copy of the project. Loop the troublesome passage and mark the time of the first crackle. Replay three times. Does it happen on the same consonant each time, or does it move? Export that passage and play it on a second device. A click fixed to the same instant in the export points you toward a recorded noise, a clip boundary or processing in the session. Solo the source and listen across its edits. A clean export with intermittent crackles during playback puts the real-time path first on your list.
Make a fresh project with one unprocessed track at the original sample rate. Play a known-clean file through the same interface. Then record ten seconds of evenly sustained voice or instrument below clipping. If the old session crackles and this one stays clean, return to a copy of the old session and temporarily render a demanding software instrument to audio. Play the problem section again.
Test buffer size with the music held constant
The audio buffer gives the system time to process the next block of samples. A smaller block can feel more responsive but leaves less time to meet each deadline. Write down the current buffer, then try one step larger, such as 128 to 256 samples. Keep the sample rate and test passage unchanged. Record whether the crackle and the performer’s sense of delay changed. A clean run at the larger size points to a real-time load problem. Repeat the original setting once to check the change is repeatable. Ableton’s audio-latency explanation
If the clean test project still glitches, follow the interface maker’s USB guidance. As separate tests, connect directly to a compatible port and try a known-good data cable that meets the interface specification. Verify the software and driver match the model and operating system. Save system changes for a recording break. Focusrite’s USB troubleshooting guide
Prove the session is ready
Run a full chorus with all intended tracks armed. Listen to the recorded file away from the session and ask the performer whether the cue feels playable. Log the interface, port, driver, sample rate, buffer and result together. “256 samples, three clean choruses, voice monitored directly” is a setting another engineer can test.
Companion chapter · Build a bedroom studio around one clean take
Bedroom to Stage contents and glossary