Audio Production Check
Verify microphone signal, clipping, monitoring output, and MIDI input before changing DAW routing or audio-interface settings.
Audio production problems are usually easiest to isolate as input signal → interface/OS device → DAW routing → monitoring output. Verify each boundary in order.
Run the browser-visible checks, then record the physical/native checks below. Progress stays in this browser unless you deliberately copy the fragment share link.
Browser-visible checks
Physical & native checks
These close the blind spots a website cannot inspect.
If an audio interface is used, compare its hardware input meter/direct-monitor path with DeviceOK and the DAW.
Why it matters: A hardware meter with no browser signal points differently from browser signal with no DAW signal.Confirm the OS/DAW is using a supported sample-rate/device mode for the interface.
Why it matters: Exclusive-mode or rate conflicts can stop an otherwise healthy interface.Use phantom power only when the microphone/interface documentation calls for it and cabling is appropriate.
Why it matters: Powering rules are hardware-specific and should not be guessed from a browser test.Conditions that deserve caution
- Damaged XLR/USB/power connectors, electrical noise or overheating.
- Phantom-power requirements are uncertain for connected equipment.
How to use the evidence
Follow the signal. The first stage where signal disappears is more useful than changing drivers, buffer sizes and cables all at once.