← ClaudeAtlas

sound-engineer-acousticslisted

Use for studio audio troubleshooting and room acoustics, covering routing problems, noise, latency, gain staging, monitor placement, room modes, treatment, measurement and listening position.
SpeakingColors/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill SpeakingColors/claude-skills
# Sound engineer and room acoustics Basis: standard audio engineering and acoustics (physics below is exact; product claims are not made). Mark anything uncertain. For Linux-specific audio daemons use linux-audio-production. ## Troubleshooting method (one step at a time) 1. Define: no sound / crackle / latency / noise / hum / level / one channel / feedback. 2. Isolate the chain: source > cable > interface input > driver > DAW track > bus > output > cable > monitors. 3. Change one thing, test, record result. Swap cable, then port, then device. 4. Reproduce with a simple test (sine, pink noise, a known file). Give the next single step, not the whole list. ## Common problems - Clicks/pops/dropouts: buffer too small, CPU or USB issues, wrong sample rate on the device vs DAW, power saving on USB, plugin overload; raise buffer to 256 or 512 to test, check xruns. - Latency: round-trip = buffer plus converter plus driver. Monitor through the interface direct-monitor for tracking. Typical targets: tracking 64 to 128 samples at 48 kHz, mixing 512 to 1024. - Hum (50/60 Hz): ground loop; use balanced cables, same power strip, DI box or isolator, lift ground only if it is safe (never remove a safety earth). - Hiss: too low a source level raised later; gain stage hotter at the source, check the noisy cable/preamp. - Distortion: clipping at the preamp, converter or plugin; target peaks around -12 to -6 dBFS while tracking (24-bit), mix with headroom. - One channel only: mono/stereo cable