3 Commits

Author	SHA1	Message	Date
Smittix	9463b36bb7	Fix WebSocket handler exiting immediately on receive timeout ... simple-websocket 1.1.0's receive(timeout=N) returns None on timeout instead of raising TimeoutError. The handler treated None as "connection closed" and broke out of the loop, causing Werkzeug to write its HTTP 200 response on the still-open WebSocket socket. The browser saw those HTTP bytes as an invalid WebSocket frame. Now checks ws.connected to distinguish timeout (None + connected) from actual close (None + not connected). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-08 13:21:25 +00:00
Smittix	30b9a97d99	Fix WebSocket waterfall "Invalid frame header" by serializing sends ... The fft_reader thread was calling ws.send() concurrently with ws.receive() in the main loop. simple-websocket is not thread-safe for simultaneous read/write, corrupting frame headers. Now the reader thread enqueues frames and only the main loop touches the WebSocket. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-08 12:52:42 +00:00
Smittix	a19f053abe	Add real-time WebSocket waterfall with I/Q capture and server-side FFT ... Replace the batch rtl_power SSE pipeline with continuous I/Q streaming via WebSocket for smooth ~25fps waterfall display. The server captures raw I/Q samples (rtl_sdr/rx_sdr), computes Hann-windowed FFT, and sends compact binary frames (1035 bytes vs ~15KB JSON, 93% reduction). Client falls back to existing SSE path if WebSocket is unavailable. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-08 12:37:50 +00:00