From 8e68c5d9d0dd7216e6a9165a123e9c5e22fd2118 Mon Sep 17 00:00:00 2001 From: Smittix Date: Wed, 28 Jan 2026 23:00:50 +0000 Subject: [PATCH] fix: Initialize audio visualizer when listening starts The audio visualizer (Web Audio API analyzer) was not being initialized when direct listening or scanner signal detection started, so the synthesizer never received audio level data. Co-Authored-By: Claude Opus 4.5 --- static/js/modes/listening-post.js | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/static/js/modes/listening-post.js b/static/js/modes/listening-post.js index 46e64c4..1af1aef 100644 --- a/static/js/modes/listening-post.js +++ b/static/js/modes/listening-post.js @@ -659,6 +659,8 @@ function handleSignalFound(data) { scannerAudio.volume = knobValue / 100; } scannerAudio.play().catch(e => console.warn('[SCANNER] Audio autoplay blocked:', e)); + // Initialize audio visualizer to feed signal levels to synthesizer + initAudioVisualizer(); } } @@ -2089,6 +2091,9 @@ async function _startDirectListenInternal() { console.log('[LISTEN] Initial play blocked, waiting for canplay'); }); + // Initialize audio visualizer to feed signal levels to synthesizer + initAudioVisualizer(); + isDirectListening = true; updateDirectListenUI(true, freq); addScannerLogEntry(`${freq.toFixed(3)} MHz (${currentModulation.toUpperCase()})`, '', 'signal');