verify_stream_format ignored ProcessLoopbackCapture::start()'s bool. A failed loopback activation then produced an empty ground-truth signal, so the result was ok=false -- indistinguishable from "captured fine but the two paths didn't correlate" -- after burning the whole measurement window capturing only the hook side for nothing. Now it checks start(): on failure it restores the ring tap, emits a clear OutputDebugString diagnostic, and returns immediately (ok=false) instead of wasting the window. The caller still falls back to the measured guess, but the cause is now visible. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
7.8 KiB
7.8 KiB