Troubleshooting

Fixing the common problems every home studio hits

8 min read

Almost every home studio problem is one of a small number of recurring faults, and each has a known cause. This is a symptom-first guide: find what you are hearing, then work through the list.

Hum: a steady buzz at 50 or 60 Hz

What you hear: a steady tone, like a fridge or a fluorescent light, on every track.

Causes, in order of likelihood:

  1. Ground loops. Two pieces of equipment are connected to the mains through different paths, and the small voltage difference between them drives current through the audio cable. Classic sources: a laptop on its power adapter connected to a desktop interface, an amplifier and a computer on different circuits, or a cheap power strip.
  2. Poorly shielded or unbalanced cables. Long unbalanced runs, or a cable running next to a power cable.
  3. A dimmer switch or fluorescent light on the same circuit.
  4. An ungrounded outlet, or an outlet with a broken earth pin.

Fixes:

  • Test first. Unplug everything except the computer and the interface, and record silence. If the hum goes, add devices back one at a time until it returns — you have found the culprit.
  • Try a different outlet, ideally on a different circuit.
  • Use the same power strip for the computer and the interface, plugged into one outlet.
  • Check the cables. Replace any that are visibly damaged, and avoid running audio cables alongside mains cables.
  • Lift the ground pin on one end of the hum-carrying cable. This genuinely fixes ground loops, and it is a legitimate technique — but it is also a safety compromise. Do it on a short, known-good cable, never on a mains lead, and never as a permanent fix for a faulty installation. If you are unsure, ask an electrician.
  • A hum eliminator — a device that inserts a balanced isolation transformer in the offending path. Effective, and it costs money. Try the cheaper tests first.

A hum that is not present in the recording but appears on playback is a different problem: a USB ground loop in the monitoring path. Unplug the interface from USB and see if it disappears. If it does, a ground loop eliminator in the USB path fixes it.

Clicks and pops

What you hear: sharp clicks, either continuously or at the start of playback.

Causes and fixes:

  • A device is switching on or off. A click at the start of playback usually means something in the signal chain is powering up or switching impedance. Turn off automatic standby on interfaces, and try a different USB port.
  • A crackling gain knob. Turn the preamp gain down fully while the track is recording, then bring it up. If the crackle disappears, the pot is worn — a cheap fix is to spray it with contact cleaner, and a better fix is to not touch it during recording.
  • A bad cable. Intermittent clicks that come and go with movement are nearly always a cable fault. Move the cable while recording to test it.
  • Ground loops. See above.
  • Buffer underruns. The computer is struggling. Close other applications, lower the buffer size... actually, raise it slightly, or use a faster drive.

Clipping

What you hear: a harsh, flat, distorted sound, usually in the loudest moments.

There are two different clips, and they are not equally serious.

Clipping in the recording is fatal. The converter recorded a flattened waveform and the information is gone. You must re-record. Signs: waveform tops visibly flat, or a sudden change in texture on loud passages.

Clipping in the mix is a fader or master problem. The recorded audio is fine but the sum is too hot. Fix it by pulling the master fader down and rebalancing.

Prevention:

  • Record peaks around -12 dBFS. Six dB of headroom means a louder-than-expected performance cannot clip.
  • Watch the meter, not the gain knob.
  • Do not "fix" a quiet recording with gain. A quiet recording has a high signal-to-noise ratio problem, and raising the gain raises the noise with it.

Latency: you play, it comes back late

What you hear: you press a key or hit a drum and the sound arrives a fraction late. On an overdub, the timing drifts steadily further behind the original.

Causes:

  • The recording buffer size.
  • The interface's driver and conversion latency.
  • The latency of plugins in the monitoring path.
  • On USB interfaces, the round trip through the computer.

Fixes, in order:

  1. Lower the buffer size for tracking. 128 samples is a good default at 48 kHz; 64 if your setup handles it.
  2. Use direct monitoring for tracking. Zero latency, but you will not hear plugins or the recording.
  3. Use low-latency monitoring if your interface has it — a blend of direct and processed signal that lets you hear effects without the delay.
  4. Turn off plugins in the monitoring path during recording.
  5. Move the recording drive to a faster medium. A spinning disk or a busy system causes dropouts and clicks.
  6. Accept it and compensate. If the delay is consistent, you can nudge the recorded track to align it. This is a last resort, not a fix.

The delay should be the same every time. If it varies, you have a performance problem, not a settings problem.

The recording sounds thin or quiet

What you hear: the recording is there but it feels small, and there is noise underneath it.

Causes:

  • The signal-to-noise ratio is genuinely low. The source was too quiet, the preamp gain was too low, or the microphone was too far away.
  • The source is too quiet for the preamp. If you ran out of gain, the noise floor of the electronics is now part of every recording.
  • Wrong input. A line-level source plugged into a mic input, or a mic into a line input, sounds wrong in both directions.

Fixes:

  • Move the microphone closer. This is free and usually the biggest improvement.
  • Use a preamp with more gain, or a more sensitive microphone.
  • Do not fix this with volume. The noise comes up with the signal.
  • Check the input assignment on the interface and in the DAW.

The recording sounds muffled or dull

What you hear: no top end, no "air".

Causes:

  • The microphone is too far away. Distance also costs high frequencies.
  • The microphone is covered. A pop filter held flat against the capsule, a windscreen that is too thick, or a hand over the microphone.
  • The wrong side of a cardioid microphone. The back of a cardioid microphone does not just sound dull, it sounds wrong.
  • A dull plugin. A high-pass filter set too aggressively, or a plugin adding a lot of low-mid.
  • It is the room. A very live room loses clarity because reflections arrive before the direct sound.
  • A bad cable or a failing preamp — rare, but it happens.

Fixes: move the microphone closer and check the polar pattern; bypass every plugin on the track and listen to the raw recording; check the input on the interface.

Background noise in the recording

What you hear: traffic, a fridge, a computer fan, an electrical hum, a neighbour.

Fixes, in order of effectiveness:

  1. Fix the source. A fridge in the room cannot be edited out; unplug it or record at another time.
  2. Choose a better time. Most homes are quietest late at night and early in the morning.
  3. Change the microphone position. Distance and direction are the most powerful noise tools you have: a cardioid microphone pointed away from the noise rejects a lot of it.
  4. Treat the room. Absorbing the noise source's reflections reduces the direct sound reaching the microphone as well.
  5. Use a noise gate to silence the gaps between phrases. It does not improve the noise while you are speaking — it only stops it being printed between words.
  6. Use a noise reduction plugin as a last resort. Heavy settings produce the characteristic "underwater" artefact.

Playback is crackly or drops out

Causes: buffer underruns from a busy CPU, a slow drive, a weak USB connection, or a driver fault.

Fixes: close applications; use a faster drive for the audio; try a different USB port or a powered hub; move the interface off the CPU-bound USB bus; lower the buffer size only if the CPU can handle it.

The recording is fine but the mix is not

That is a different category of problem, and it is covered in your first mix — but one diagnostic is worth repeating here:

Play the raw recording on headphones, on a phone speaker and on your monitors. If it sounds wrong on all three, the problem is in the recording. If it sounds fine on headphones and wrong on the monitors, the problem is the monitoring or the room.

A troubleshooting order that works

  1. Bypass everything. Listen to the raw recorded audio. This tells you which half of the problem you have.
  2. Change one thing at a time. Two changes at once and you will not know which one worked.
  3. Trust the measurement. Levels, sample rates, buffer sizes, clipping. Most faults announce themselves in the numbers.
  4. Write down what you changed. Symptom-based debugging beats random fiddling.

Keep reading

All tutorials →